Runtime converts a chosen amount; it does not choose that amount
Dosing-pump runtime equals a separately chosen liquid volume divided by measured delivery rate. The result tells you how long delivery would take under the measurement assumptions. It does not determine an aquarium's chemical demand, a livestock-safe dose or how often an additive should be used. Establish those decisions from the applicable product instructions, measurements and suitable aquarium guidance before using runtime arithmetic.
The dedicated calibration guide covers obtaining a measured delivery observation. This article focuses on interpreting rate units and translating them into seconds without a factor-of-sixty error. NumUtility's Aquarium Dosing Pump Calibration Calculator displays that conversion, but it does not program a controller, send a command to equipment or generate a chemical dosing schedule.
Convert the measured collection into a rate
Suppose a hypothetical primed pump collects 24 mL over a measured 60-second test under its manufacturer's procedure. Its average rate is 24/60 = 0.4 mL/second, or 24 mL/minute. The collection volume and elapsed time belong to the same test. A nominal speed from a different head, tubing arrangement or liquid is not an equivalent measurement.
For a second illustration, collecting 12 mL in 30 seconds gives the same average rate of 0.4 mL/second. Collecting 12 mL in 60 seconds instead gives 0.2 mL/second. Keep the duration attached to every collected amount so that a change in test length is not mistaken for a change in pump performance.
Use compatible units before dividing
If rate is expressed in mL/minute and desired volume in mL, dividing volume by rate gives minutes. Multiply that answer by 60 to obtain seconds. Equivalently, runtime_seconds = desired_mL × 60 / rate_mL_per_minute. For 10 mL at 24 mL/minute, the result is 10 × 60/24 = 25 seconds, not 0.4167 seconds.
If rate is already 0.4 mL/second, divide 10 mL directly by 0.4 mL/second to obtain the same 25 seconds. Applying another factor of 60 would be wrong. A dimensional check is useful: the mL terms cancel and the remaining time unit must match the result's label. Do this check before rounding or copying a number into another interface.
Keep liters per hour distinct from milliliters per minute
The same 24 mL/minute rate is 1,440 mL/hour, or 1.44 L/hour. The conversion uses both 60 minutes per hour and 1,000 mL per liter. A specification written as 1.44 L/hour is not 1.44 mL/minute. Copying only the displayed numeric value while changing the unit can produce a large error even when the number looks plausible.
If a separately established desired amount is 0.010 L, convert it to 10 mL before using a rate in mL/second. Avoid using an unlabeled field as though it accepts any familiar unit. NumUtility's collection and desired-dose fields are in milliliters, and the test duration is in seconds; it does not infer unit choices from a product label or controller screen.
Check short-run delivery rather than assuming perfect linearity
At the hypothetical measured rate of 0.4 mL/second, 3 mL corresponds to 7.5 seconds. That is a theoretical proportional estimate from an average collection test. Very short pulses can be more sensitive to startup behavior, tubing condition, trapped air and controller timing limits than a longer test. Follow the equipment's calibration and verification procedures for the intended operating conditions.
As a purely illustrative controller constraint, rounding a 7.5-second estimate to 8 seconds at the assumed constant rate predicts 3.2 mL, which is 0.2 mL above 3 mL. This does not claim that any particular controller uses whole-second steps. Check the actual device's supported settings and measured delivery instead of assuming the displayed decimal can be programmed or delivered exactly.
Separate a runtime estimate from a calibration correction
The calculator can optionally compare collected liquid with the amount commanded for that same collection test. If 24 mL was collected when 20 mL was commanded, signed relative error is (24 − 20)/20 × 100 = +20 percent. This describes that test's volume discrepancy; it is not a manufacturer's calibration-factor instruction.
The desired 10 mL used for a future runtime example is a separate quantity and must not replace the 20 mL commanded during the test. Different controllers define calibration entries differently, so do not enter a reciprocal factor or signed percentage into firmware without its instructions. The runtime result and the optional commanded-versus-collected error answer different questions.
Treat multiple events as a scheduling question outside the calculator
At a constant 0.4 mL/second, one theoretical 30 mL delivery takes 75 seconds. Three theoretical 10 mL deliveries total the same 75 seconds of pumping, but their start times, pulse behavior and suitability are not determined by that equality. The arithmetic does not recommend combining events or changing the timing of an aquarium additive.
Likewise, it does not approve mixing different chemicals, sharing tubing or delivering incompatible products together. Keep each pump head, liquid and measured arrangement identified in the record. If operating conditions or tubing change, verify delivery according to the equipment instructions rather than assuming an old average remains accurate because the nominal pump model is unchanged.
Record measured rate, desired amount and verification separately
A reproducible runtime note includes the pump head, relevant setup, collection volume, test seconds, calculated mL/minute, independently chosen desired mL and calculated runtime seconds. Record the actual supported controller setting and any verification collection separately. That distinction preserves the difference between a mathematical estimate, a programmed value and observed physical delivery.
Use suitable measurement tools and the manufacturer's procedure; do not assume a generic number of drops per milliliter or a universal liquid density. The calculator does not average a test history, compensate for wear automatically or guarantee dosing accuracy. Its value is a transparent unit conversion that you can compare with the device's instructions and an appropriate delivery check.