The Excavator Productivity Calculator computes actual earthmoving yield using Ph=V/Th. Enter your total excavated volume and tracked operating time to instantly output hourly production rates.
Your Machine Specs Don’t Tell You What Your Excavator Actually Moved Today
Manufacturer datasheets give you rated output under ideal conditions — optimal swing angle, perfect fill factor, skilled operator, firm underfoot. Real sites don’t work that way. Rocky material, soft ground, a tight swing radius, or a less experienced operator can cut theoretical productivity by 30–50% before the morning is out. This calculator runs the math the other way: you enter what actually moved and how long it actually took, and it tells you your true measured productivity in real-time volume per hour.
That number — actual m³/hr or yd³/hr from your own field data — is the one worth tracking, comparing shift to shift, and using to project the rest of a dig.
Formula
All outputs trace back to one core division. Every other figure the calculator produces is derived from it.
Core productivity rate:
Productivity (m³/hr) = Volume ÷ Time (hrs)
If you enter time in minutes, the calculator converts it first before dividing:
Time (hrs) = Time (mins) ÷ 60
Pace and micro-yield (Card 1):
Rate per minute = Productivity (m³/hr) ÷ 60 Time for 100 m³ = 100 ÷ Productivity (m³/hr)
Trucking logistics (Card 2) — requires truck capacity input:
Trucks per hour = Productivity (m³/hr) ÷ Truck Capacity (m³) Minutes between trucks = 60 ÷ Trucks per hour
Project completion (Card 3) — requires project volume input:
Remaining volume (m³) = Project Total − Volume Already Moved Hours remaining = Remaining Volume ÷ Productivity (m³/hr)
If the volume already moved equals or exceeds the project total, remaining hours return as zero and the result displays as Goal Reached.
What Each Output Is Telling You
The hourly rate is the headline figure — use it to compare days, operators, or materials. The per-minute rate and “Time for 100 m³” are the same number expressed differently, useful for short spot-checks during a shift without waiting for a full hour of data.
The trucking card is where the calculator earns its place on mixed-fleet sites. Dividing your measured output by truck capacity gives you the exact load frequency your haulage needs to keep pace with the machine. If trucks are arriving slower than that interval, the excavator is idle. If they’re arriving faster, trucks are queuing. Either way, the gap between your calculated interval and your actual one is a direct measure of logistics efficiency.
The project completion estimate assumes your current rate holds for the remainder of the dig — same material, same conditions, same machine. Use it as a baseline for scheduling, not a hard deadline.
The Measurement Window Problem
Everything this calculator produces is only as clean as the window of time you feed it. If your “8 hours” includes a 45-minute lunch, two operator changeovers, a pre-shift inspection, and a rain delay, you’ve given the calculator 8 hours when the machine was cutting ground for maybe 5.5 of them. The result looks like a low productivity rate — but the excavator itself may be performing exactly as expected. You’re measuring site throughput, not machine output.
Shorter, cleanly timed working bursts entered in minutes will give a truer machine rate than a loosely tracked full-day figure. On the flip side, if your measured window excludes idle time that is unavoidable on that site — waiting for ground crew, waiting for trucks — then your rate is optimistic. Know which question you’re asking before you use the output to commit a completion date.
Worked Example: Cut-and-Fill on a Road Widening Job
A site supervisor is running a 20-tonne excavator on mixed clay and gravel. By mid-morning the machine has moved 480 m³ in 3 hours and 20 minutes. She enters 480 in the volume field, switches the time unit to minutes, and enters 200 — no mental conversion needed.
The calculator converts 200 minutes to 3.33 hours and returns 144 m³/hr. Per-minute rate: 2.4 m³/min. Time for 100 m³: 41.7 minutes — a useful benchmark against yesterday’s session on the same machine.
Her dump trucks carry 12 m³ each. At 144 m³/hr the formula gives 12 loads per hour — one truck every 5 minutes. Her actual fleet is cycling at one every 8 minutes because the haul road is longer than planned. That gap immediately flags a haulage bottleneck. The excavator is waiting between loads, and real daily throughput will sit below the measured digging rate unless haulage frequency is addressed.
Total project cut: 6,500 m³. With 480 m³ done, 6,020 m³ remains. At 144 m³/hr that is 41.8 hours of active cutting — useful input for a revised programme, though she pads it to account for the truck timing issue the logistics card just surfaced.
Frequently Asked Questions
Does it matter whether I enter time in hours or minutes?
The result is identical either way. Enter 1.5 hours or 90 minutes and you get the same productivity figure. The two options exist for convenience — short timed bursts are easier to record in minutes, full shift data is simpler in hours. Use whichever you wrote down without converting.
The truck scheduling card says “Needs Input” — what triggers it?
The trucking calculation only activates when you enter a truck capacity greater than zero. Leave it blank or enter 0 and the card stays inactive. Dividing hourly output by a zero truck size would produce a meaningless result, so the calculator holds off rather than displaying an error or an infinite value.
What happens if the project volume I enter is smaller than what I’ve already dug?
The project completion card shows “Goal Reached” with zero remaining rather than a negative number. This handles over-excavation scenarios or cases where you’re logging data after a phase is already complete.
Does this account for material swell, bucket fill factor, or operator efficiency ratings?
No — deliberately. This calculator works backward from what you measured on the ground. Those corrections belong in your volume survey before the data comes here, not inside the productivity calculation itself. Mixing a real measured volume with a theoretical adjustment factor makes the output harder to trust. What you enter is what gets calculated, in whatever measure your site survey used.