About this tool
What does it compute?
Arrival times from distance and speed, task completion from remaining work and rate, and download ETAs from size and throughput — with unit handling so mixed inputs just work.
How to use it
- Enter what you know: distance+speed, work+rate, or size+bandwidth.
- Read the ETA plus the implied assumptions.
- Adjust for reality (traffic, overhead) on top.
Examples
- 240 km at 80 km/h → 3:00 arrival.
- 1.2 GB at 50 Mbps → ~3:12 (bits vs bytes handled).
- 40 tickets at 8/day → 5 working days.
Important limitations
- Linear math assumes constant rate — real trips and downloads vary.
- Bits vs bytes is the #1 download-ETA bug: 8× off if mixed.
- Working-day math needs calendars; raw division ignores weekends.
Privacy
Local arithmetic. Routes and plans stay on your device.
Frequently asked questions
Why is my download slower than math says?
Protocol overhead, congestion, server limits — divide advertised speed by ~0.8 for realism.
MB or MiB?
ISPs sell megabits (Mb); files measure megabytes (MB): 100 Mb/s ≈ 12.5 MB/s.
Time zones on arrival?
Set them explicitly for cross-zone trips — the math is zone-naive.