ETA calculator

Estimate total duration and end time

All computation runs locally in your browser

Last updated: February 8, 2026

CreatorFrank Zhao

Amount of element to consume

The consumption started at

Amount of unit consumed by time span

I have 186 dishes to wash. It takes me 5 minutes to wash 3 dishes.

Total duration

5 hours 10 minutes

It will end

today at 07:43

An ETA (estimated time of arrival) is a simple rate question: “Given my pace, how long until I’m done — and what time will that be?” Below you’ll find a quick-start walkthrough, practical examples with real numbers, and a plain-English explanation of the formulas.

→Introduction / overview
→How to use / quick start
→Real-world examples
→Common scenarios
→Tips & best practices
→Calculation method
→Related concepts
→Frequently asked questions
→Limitations / disclaimers
→External references

Introduction / overview

This ETA calculator estimates how long it takes to finish a total amount of work when you have a steady rate. You’ll get two outputs: the total duration and the estimated end time.

Who is this for?

Anyone tracking a queue: tickets, tasks, records, items, pages, kilometers.
People planning a work block (“If I keep this pace, when do I stop?”).
Teams estimating completion windows for batch jobs and service throughput.

Best results come from a reasonably steady pace. If your speed changes a lot, treat the ETA as a rough guide and recompute when conditions change.

Need to share a schedule-friendly timestamp? Pair the result with our Date time converter to copy, format, or convert date-time values.

How to use / quick start

1Enter the total amount you want to finish. Think “units of work” (tickets, pages, items, km).
2Choose the start time (when the work began).
3Enter your pace as “consumed per time span”, for example3 items per 5 minutes.
4Read the outputs: total duration and the friendly end time label.

Quick sanity check: doubling the total should double the duration; doubling the pace should roughly halve the duration.

Worked example 1 (queue / throughput)

Background: you have $A = 30000$ records to process. Your system handles $c = 120$ records per $s = 1\ \mathrm{min}$ .

T = \frac{A\cdot s}{c}

=

\frac{30000\cdot 1\ \mathrm{min}}{120}

=

250\ \mathrm{min}

=

4\ \mathrm{h}\ 10\ \mathrm{min}

If you started at 09:20, the end time is:

t_{\mathrm{end}} = 09{:}20 + 4{:}10 = 13{:}30

How to use it: if 13:30 is too late, you can increase throughput (bigger batch size, more workers, faster instance) and re-run the ETA.

Worked example 2 (personal work block)

You want to draft $A = 3000$ words. Your pace is $c = 500$ words per $s = 1\ \mathrm{h}$ .

T = \frac{A\cdot s}{c}

=

\frac{3000\cdot 1\ \mathrm{h}}{500}

=

6\ \mathrm{h}

How to interpret it: if you only have 3 hours today, you’re looking at roughly half the draft — or you’ll need a higher pace.

Real-world examples / use cases

Each example below follows the same pattern: define the total $A$ , define the pace $c$ per span $s$ , then compute the duration. If you keep the “unit of work” consistent, the calculator works for almost anything.

Manufacturing batch

Background: you need to produce 480 parts.

Inputs: $A=480$ , pace $c=32$ parts per $s=20\ \mathrm{min}$ .

Result: $T=\frac{480\cdot 20}{32}=300\ \mathrm{min}=5\ \mathrm{h}$ .

How to apply: plan shift coverage and setup time around a 5-hour run.

Studying / reading session

Background: you have 120 pages to read.

Inputs: $A=120$ pages, pace $c=18$ pages per $s=45\ \mathrm{min}$ .

Result: $T=\frac{120\cdot 45}{18}=300\ \mathrm{min}=5\ \mathrm{h}$ .

How to apply: split into two blocks (e.g., 2 hours + 3 hours) if you want a break.

Support backlog

Background: your team has 210 tickets waiting.

Inputs: $A=210$ tickets, pace $c=7$ tickets per $s=30\ \mathrm{min}$ .

Result: $T=\frac{210\cdot 30}{7}=900\ \mathrm{min}=15\ \mathrm{h}$ .

How to apply: convert 15 hours into shifts, then re-run the ETA each day with the remaining amount.

Travel time (steady speed)

Background: you have 120 km remaining at roughly constant speed.

Inputs: $A=120$ km, pace $c=60$ km per $s=1\ \mathrm{h}$ .

Result: $T=\frac{120\cdot 1}{60}=2\ \mathrm{h}$ .

How to apply: add buffer if traffic is uncertain and re-check after the next checkpoint.

Common scenarios

Queue finishes

Useful when you know “items per minute” and the queue size.

Not ideal if throughput swings wildly (autoscaling, retries, failures).

Deep work session

Useful for writing, studying, and personal tasks with a stable pace.

Not ideal if interruptions are frequent and unpredictable.

Travel time at steady speed

Useful for a simple “distance / speed” style ETA.

Not ideal for heavy traffic, stops, or mixed road conditions.

Production / fulfillment

Useful when “units per hour” is fairly stable.

Not ideal when setup changes or downtime dominate the timeline.

Countdown to a deadline

Useful for “If I started at X, I’ll finish at Y.”

Not ideal if you must account for calendars, time zones, or hard business hours.

Break planning

Useful to sanity-check how breaks change an ETA (compute in segments).

Not ideal if the pace after the break is unknown — measure again and update.

Tips & best practices

Use consistent “units of work” (items, pages, km, MB). The calculator treats the amount as a pure count.
Prefer measuring a representative window (e.g. 10–15 minutes) to reduce randomness in the rate.
For variable-rate processes, break work into segments and sum durations.
Use the Share button to generate a link that restores the same inputs.
If the ETA is business-critical, add a buffer. Real processes have variance even when the average rate looks stable.

Calculation method / formula explanation

The calculator uses a constant-rate model. Let $A$ be the total amount of work. Let $c$ be the amount you complete in one time span, and $s$ be that time span. Then your average rate is $c/s$ .

T = \frac{A}{c/s}

=

\frac{A\cdot s}{c}

Internally, the chosen time unit is converted to milliseconds. If one time unit equals $u$ milliseconds, then:

T_{ms} = \frac{A \cdot (s \cdot u)}{c}

Finally, the end time is computed by adding the duration to the start time:

t_{end} = t_{start} + T_{ms}

Related concepts

Dimensional analysis: a quick unit check. If you do $\text{items} / (\text{items}/\text{min})$ , you should end up with minutes.
Throughput: items/time, commonly used in queues, manufacturing, and data pipelines.
Piecewise rates: if the rate changes, compute each segment and add them.
Local time: the displayed end time follows your device’s locale/timezone settings.
Rounding: durations are formatted for readability (hours/minutes/seconds), not for legal or contractual timing.

Frequently asked questions

Why does my ETA look wrong?

The most common cause is a unit mismatch (e.g. you measured “per hour” but selected “minutes”). Double-check the time unit and ensure your rate is “units consumed per time span”.

Can I use decimals?

Yes—decimals work for amount, consumed-per-span, and time span. Extremely small spans may make the duration harder to interpret.

Does the calculator account for breaks or changing speed?

No. It assumes a constant rate. If your process changes, compute ETAs for each phase and sum them.

Is my data uploaded?

No—computation runs locally in your browser.

What does “It will end: tomorrow at 14:05” mean?

It’s a friendly, relative label based on your local date/time. If you need an exact timestamp to paste elsewhere, use the Date time converter to format it.

How do I model a two-phase pace?

Compute each segment separately and add durations. In symbols: $T = T_1 + T_2$ . For example, work 2 hours at one rate, then 3 hours at a slower rate.

What if my “consumed” number is larger than the total?

That just means the work fits within one span. The math still works: $T = \frac{A\cdot s}{c}$ will be less than $s$ .

Limitations / disclaimers

What this calculator does not do

It assumes a constant average rate; it does not model variability, breaks, or bottlenecks.
The “end time” label is optimized for readability; use exact timestamps for strict scheduling.
This is not professional advice for contracts, staffing commitments, or safety-critical planning.

External references / sources

These are general references that explain the underlying ideas (rates, units, and queue-style thinking):

Related Calculators

Chronometer

Use a simple chronometer (stopwatch) to track elapsed time down to milliseconds. Runs locally in your browser.

Try Now

Email normalizer

Normalize email addresses to a standard format for easier comparison. Useful for deduplication and data cleaning. Runs locally in your browser.

Try Now

JWT parser

Parse and decode your JSON Web Token (JWT) and display its content. All computation runs locally in your browser.

Try Now

MIME types

Know which file extensions are associated to a MIME type, and which MIME type is associated to a file extension. Includes a full MIME types table.

Try Now

Lorem ipsum generator

Generate random Lorem Ipsum placeholder text with customizable paragraphs, sentences, and word counts. Runs locally in your browser.

Try Now

HTTP status codes

Browse and search HTTP status codes (1xx–5xx). Includes WebDAV codes. Runs locally in your browser.

Try Now