ETA Calculator
MathCompute estimated time of arrival from rate and remaining work with custom units for sprint planning and long-running batch task progress projections.
5.000 / min300.0 / hour850170.0Sep 26, 2026, 5:59 AMRelated Tools
About ETA Calculator
When running a huge data import, training a model, or downloading massive files, the question you most want answered is "how much longer, and when will it finish?" This tool uses the simplest reliable approach: linear extrapolation. From the amount done and the time elapsed it derives the current rate, then divides the remaining amount by that rate to estimate the time left, showing the projected finish time and a progress bar too. Just enter total, done, and elapsed minutes, and the result updates anytime. All estimation runs locally in your browser with no backend, ideal for a quick check between batch runs. For example, total 1000, done 400, elapsed 20 minutes estimates about 30 minutes left, with a projected finish time.
How to Use
- Open the ETA Calculator tool
- Enter the values to calculate
- Adjust the output options as needed
- Click the Calculate button; results appear in real time
- Copy or export the result
Use Cases
- Data migration — When importing millions of rows, estimate total finish time from rows migrated so far.
- Model training — Use completed steps and elapsed time to predict hours left in training.
- Bulk downloads — Estimate remaining time from files downloaded to plan when to step away.
- Render jobs — Project a video or image render finish time from frames already rendered.
- Progress reports — Share the current percentage and projected finish with the team for scheduling.
- Database restore — Estimate restore completion time from the MB processed so far versus the total backup size.
- File transfer — Project remaining time for a large rsync or S3 sync from the bytes transferred so far.
FAQ
How does it compute the time left?
Rate equals done divided by elapsed, and time left equals remaining divided by rate. This is linear extrapolation assuming future speed matches the current average.
Why does the real finish come earlier or later?
The linear model ignores rate swings. If the later stage slows (large files last) or speeds up (cache hits), actual time will drift, so re-estimate as progress advances.
Does the time-left unit change?
Yes, it adapts: under a minute shows seconds, tens of minutes show minutes, over an hour shows hours, and over a day shows days, for easier reading.
Must elapsed time be in minutes?
Yes, the field is in minutes and accepts decimals. For 90 seconds enter 1.5, and the tool converts to a suitably scaled time left.
Why is there no result when done is 0?
The rate cannot be computed (division by zero), so some progress is required to extrapolate. Come back after the job has made some headway.