ETA Calculator

How to use this ETA calculator

1. Enter how many items you've completed and the total.
2. Enter how many minutes have elapsed so far.
3. See your rate, remaining time, and estimated finish clock time.

How is the estimate calculated?

The tool calculates your current rate (items per minute) from your progress so far, then projects that same rate forward to estimate how long the remaining items will take — assuming a steady pace.

The actual math behind a linear ETA projection

This calculator's underlying math is genuinely simple, but it's worth spelling out exactly what it computes. First, it derives your current rate by dividing items completed by minutes elapsed. Then, it multiplies that rate by however many items remain to get an estimated remaining time, and finally adds that remaining time to the current clock time to project a finish time. This entire calculation rests on one specific, explicit assumption: that whatever rate you've maintained so far will continue completely unchanged for the rest of the task. This is called linear extrapolation, and it's the same fundamental approach nearly every simple ETA indicator you encounter — file downloads, installation progress bars, batch job trackers — actually uses under the hood, even when it isn't stated explicitly to the user.

Why real-world progress is so often not actually linear

A linear projection assumes a constant rate, but real tasks very often don't proceed at a constant rate at all, and it's worth understanding the common reasons why. Some tasks front-load their easier work — early items are quick, straightforward cases, while items encountered later turn out to be edge cases needing extra handling, causing the actual rate to slow down over time compared to the earlier pace the estimate was built on. Other tasks do the reverse — an initial ramp-up period (a cache warming up, a batch process finding its stride) makes the beginning artificially slow compared to a faster steady-state rate reached later. This general pattern — where the last portion of a task takes disproportionately longer than a simple linear projection from earlier progress would suggest — is common enough in software development specifically that it has its own well-known name: the "90% done" phenomenon, where a task's final stretch reliably takes far longer than the previous 90% combined.

How more sophisticated tools smooth out a noisy rate estimate

More advanced ETA implementations — the kind found in mature download managers, CI/CD pipeline dashboards, and professional data processing tools — often use an exponential moving average rather than this tool's simple total-items-over-total-time calculation, specifically to react more usefully to a rate that changes over the course of the task. Rather than treating the entire elapsed history as equally representative of the current pace, an exponential moving average weights more recent progress more heavily than older progress, letting the estimate adapt relatively quickly if the actual rate genuinely shifts partway through — speeding up or slowing down — rather than being permanently anchored to a stale, outdated average rate calculated back at the very start of the task.

Why an ETA is a genuinely useful heuristic despite never being perfectly accurate

Given everything above about real-world rate variability, it's worth being explicit about why a simple linear ETA remains genuinely useful anyway, rather than dismissing it as inherently unreliable. For tasks with a reasonably steady, predictable rate — most straightforward batch file processing, most bulk API calls, many kinds of automated data transformation — a linear projection is often accurate enough in practice to be a genuinely trustworthy planning signal, even without more sophisticated smoothing. Its real value lies less in being perfectly precise down to the exact minute, and more in giving a reasonable, actionable order-of-magnitude sense of whether a task will finish in minutes, hours, or days — which is exactly the level of precision most people actually need when deciding whether to wait around, step away, or plan something else around a running task's completion.

Limitations of this tool

This tool computes a simple linear projection from your current overall progress and elapsed time — as explained above, it assumes a perfectly constant rate throughout, and doesn't implement the exponential moving average or other rate-smoothing techniques more sophisticated tools use to adapt to a rate that changes partway through a task. It's best treated as a rough, general planning estimate for tasks with a reasonably steady pace, not a guaranteed, precise completion time for tasks where the actual rate is likely to vary significantly over the course of the work.