How Long Will a Zero-Turn Mower Run on One Tank?
Tank capacity is only half the runtime calculation. Use measured consumption and a realistic refuelling allowance to plan a mowing session.
A bigger fuel tank can mean fewer refuelling stops, but the number printed on a specification sheet is not a runtime guarantee. To plan a mowing session, you need both the fuel you intend to use before stopping and a consumption rate that represents the same work.
Use two numbers with matching units
The basic calculation is planned runtime = fuel budget before refuelling / fuel consumption per hour. Divide US gallons by US gallons per hour, or litres by litres per hour. Do not combine a US-gallon capacity with an imperial-gallon consumption figure.
Your fuel budget should leave an appropriate allowance before the tank runs empty. It is not automatically the full advertised tank capacity. Follow the machine's filling instructions and decide when to stop using the fuel indication and operating experience. A larger arithmetic budget is never permission to overfill the tank.
Work through a clearly labelled example
Suppose a hypothetical mower has a nominal 10-US-gallon tank. For planning only, assume you budget 8 gallons before the next stop and have measured average consumption of 1.2 US gallons per engine hour under similar work.
- Planned runtime: 8 / 1.2 = about 6.7 engine hours.
- If consumption rises to 1.6 gallons per hour, the same budget gives 5 hours.
- A six-engine-hour work session would require 7.2 gallons at the first rate and 9.6 gallons at the second.
These are arithmetic examples, not tested mower results. The two-gallon allowance is an illustrative assumption, not a universal reserve recommendation. The useful result is the sensitivity: a route that fits the first estimate may need a planned stop under the second.
Measure consumption without emptying the tank
Start and finish at the same manufacturer-approved fill level, on level ground and with the engine stopped and cooled as instructed. Record the fuel added after the session and the engine-hour difference. Divide the refill quantity by those hours. Do not run the engine out of fuel just to measure capacity.
For example, replacing 3.6 US gallons after three engine hours gives an observed average of 1.2 gallons per hour. Label the work: deck setup, growth conditions, approximate mowing time and time spent with the engine running between cutting areas. Repeat across representative sessions rather than treating one unusually easy visit as normal.
Follow the exact manual for refuelling. Walker's B23 operator manual, for example, requires a stopped engine, cooling before refuelling a hot engine, outdoor filling and room below the top of the tank. Use your mower's instructions rather than copying another model's fill height.
Keep engine hours separate from elapsed job time
A consumption rate measured per engine hour includes whatever the engine did during the measured period. Apply it to a comparable engine-running schedule. Do not add engine-off loading time to the fuel calculation, or multiply a cutting-only rate by a mixed operating day without explaining that assumption.
Fuel planning and work-rate planning answer different questions. Our mowing-time calculation estimates time from area and effective cutting rate. Combine the two only after making the time basis consistent.
Compare capacity without ranking efficiency
The Walker B23 M48 has a published 4.7-US-gallon tank; the John Deere Z955M 60 EFI lists 11.5 US gallons. Those figures describe storage capacity, not a head-to-head fuel economy result. The machines also differ in engine, deck and intended work.
Likewise, EFI or diesel branding alone does not supply a measured consumption rate. The EFI comparison explains what evidence to request for a savings claim.
Before choosing a mower for longer sessions, write down the actual work interval, a conservative fuel budget, measured consumption and a convenient safe stopping point. If consumption has not been measured, keep runtime as an unknown in the buying comparison. Research checked October 21, 2026; no model-specific runtime testing is claimed.