ETA Calculator
Estimate when work finishes or a trip arrives — amount and rate, or distance and speed, from any start moment.
Examples
Sprint remainder
120 issues at 8/h, starting 09:0015h 0m — finishes at 00:00 (+1d)A full day's pace at eight issues an hour runs into tomorrow's midnight — the badge makes the day crossing explicit.
Road trip arrival
300 km at 75 km/h, leaving 09:004h 0m — arrives at 13:00Distance and average speed reduce to the same pipeline; no timezone math, no daylight surprises.
Midnight task
2-hour task starting 23:302h 0m — finishes at 01:30 (+1d)Epoch math plus local calendar comparison makes the overflow unambiguous — tomorrow 01:30, not a bare 01:30.
About this tool
"When is this done?" is two different questions wearing one word. In sprint planning it is work divided by pace: 120 issues at 8 per hour is 15 hours, and 15 hours from a 09:00 start lands at midnight — technically tomorrow. On the road it is distance divided by speed: 300 kilometers at a 75 km/h average is 4 hours, so a 09:00 departure arrives at 13:00. The ETA Calculator answers both on one page — a work-and-rate mode and a distance-and-speed mode share the same pipeline: compute the duration, add it to the start instant, print the remaining time and the wall-clock finish.
The start moment is yours to choose. It defaults to now, but any datetime works — a sprint that starts Monday 10:00, a trip leaving at 23:30. Fractional rates are first-class (2.5 issues per hour, 12.5 km/h in city traffic), because real paces are rarely integers and rounding a pace before computing silently skews every estimate. When the projection crosses midnight into the next calendar day, a +1d badge appears next to the finish time, so a 00:00 finish reads as tomorrow's midnight, not an ambiguous zero hour.
Timezones are handled by refusing to be clever: every computation runs on epoch milliseconds, and the datetime input plus every printed clock label use the same local zone. A 23:30 start plus a 2-hour task genuinely finishes at 01:30 on the next calendar day, midnight overflow included, without any offset arithmetic that could disagree with the user's wall clock. A start stamped in the past is flagged with an explicit error instead of silently producing a stale answer — the one input the tool refuses to accept unexamined.
Everything is computed on the device with zero network calls; the calculator never sees your calendar or your trip data, and the input persists locally between visits. The result sentence — "15h 0m — finishes at 00:00 (+1d)" — copies in one click for standups, trip plans or status updates. When you need durations without a finish instant (how long between two dates), the Date Calculator handles the calendar side, and the Pomodoro Timer tracks the pace you feed into work mode.
What this tool does not do
- Constant-rate math: the model divides amount by one pace — no ramp-up, breaks or dependency waiting; layer those into the rate you enter.
- Distance mode assumes one average speed — no traffic segments, rest stops or border waits; split a trip into legs for realism.
- Pure arithmetic only: no calendar integration, no holiday awareness, and nothing is sent anywhere — inputs stay on the device.
How to use this tool
Pick a mode
Choose Work & rate for tasks (amount ÷ units-per-hour) or Distance & speed for travel (km ÷ km/h).
Enter the inputs
Type the amount and pace, or distance and average speed — fractional values like 2.5 units per hour work fine.
Set the start moment
The start defaults to now; edit the datetime for a planned start, or press Now to snap back to the current minute.
Read and copy the estimate
Get the remaining duration (d/h/m) and the clock finish time — with a +1d badge on midnight crossings — and copy the sentence.
Use cases
Sprint and backlog forecasting
Multiply your true throughput by the remaining backlog to give standup a defensible "done by" instead of a vibe.
Trip planning
Check what time a drive actually lands — average speed, not speed limit — before booking the dinner reservation.
Batch processing estimates
Convert render queues or upload batches (items per hour) into a wall-clock finish time you can put in a status update.
The two modes, one formula
| Input | Meaning |
|---|---|
| Amount of work | Tasks, issues, pages — any unit you can count |
| Rate (units/hour) | Sustainable pace; decimals allowed (2.5/h = one item every 24 minutes) |
| Distance (km) | Total distance to cover |
| Average speed (km/h) | Realistic average, not top speed; decimals allowed |
| Start at | Any datetime — defaults to now, past starts are flagged |
| Output | Remaining duration (d/h/m) + clock finish time, +1d badge on day crossings |
Both modes reduce to the same formula: duration = amount ÷ rate, finish = start + duration — computed on epoch milliseconds, timezone-safe.
Common mistakes
Mistake:Using top speed or best-case pace.
Fix:ETA is only as honest as its rate. Use a sustainable average — the last three sprints' throughput or the trip's moving average — not the ceiling.
Mistake:Starting from a stale timestamp.
Fix:A start left from yesterday silently shifts every result. The tool flags past starts; press Now to snap to the current minute.
Mistake:Ignoring the day crossing.
Fix:A bare "00:00" finish is ambiguous. The +1d badge exists so midnight crossings are stated, not implied.
Frequently asked questions
How does the ETA calculation work?
Both modes reduce to one formula: duration = amount ÷ rate, finish = start + duration. Work & rate mode divides tasks by your pace — 120 issues at 8 per hour is 15 hours. Distance & speed mode divides kilometers by average speed — 300 km at 75 km/h is 4 hours. The duration is added to your chosen start instant, and the tool prints the remaining time in d/h/m form plus the wall-clock finish time, computed on epoch milliseconds so the clock labels always match the datetime you entered.
Can I use decimal or fractional rates?
Yes — rates like 2.5 issues per hour or 12.5 km/h are first-class inputs, and they matter: rounding a pace to 3/h before computing would shift a 100-unit batch by hours. A 2.5/h pace means one item every 24 minutes, and the calculator converts that directly into the finish instant. Real-world paces — reviews per day, renders per hour, city-driving averages — are rarely integers, so the inputs accept any decimal.
What happens when the estimate crosses midnight?
The finish time gets a +1d badge whenever it lands on the next calendar day (or beyond): a 09:00 start with a 15-hour run shows "finishes at 00:00 (+1d)" instead of an ambiguous bare midnight. The comparison uses local calendar dates on both ends, so a 23:30 + 2 hours genuinely reads as tomorrow 01:30. There is no UTC conversion anywhere in the chain — what you see is your wall clock.
Why does the tool reject a past start time?
A past start silently shifts every result — an estimate computed from yesterday's timestamp looks valid and is wrong. The calculator flags the input with an explicit error instead of guessing your intent, and the Now button snaps the start to the current minute. If you genuinely want to project backward-looking work, set the start to the moment the work actually began — any explicit past datetime you choose yourself is accepted.
Which pace should I enter for sprint work?
Use a sustainable average, not your best day: the throughput from your last few sprints (issues completed ÷ working hours) or a measured items-per-hour from a timer. Top pace systematically produces optimistic ETAs that erode trust in estimates. If your pace varies by task type, run the calculator per task type and add the finish instants rather than averaging heterogeneous work into one rate.
Is my input sent anywhere?
No — everything is computed locally in your browser, with zero network calls. Your inputs persist only in local storage so a half-finished estimate survives a refresh, and nothing about your tasks, distances or schedules reaches a server. Copying the result sentence gives you a portable one-liner for standup notes or trip plans.
References & standards
Related tools
Date Calculator
Calculate the difference between two dates or add/subtract days, weeks, months and years
Time Calculator
Add or subtract hours:minutes durations and find intervals between times.
Pomodoro Focus Timer
Classic 25/5 Pomodoro cycles with configurable lengths, sound alerts and optional notifications — accurate even in background tabs.