How to calculate what time it was
A clear method for turning “X ago” into a clock time in your timezone, including midnight wrap and why a calculator is safer than counting on a calendar.
Method
Start from a trusted “now”
Every “what time was it” answer is only as good as the clock you subtract from. Use the time on the device in front of you, including its timezone. If that clock is wrong, the offset will be exact and the wall time will still be wrong.
Write down the offset you actually mean: 7 hours is not the same as “this morning”, and 1 day is not the same as 8 hours. Name the unit before you subtract.
Subtract in one unit, then convert
The reliable method is: convert the offset to seconds, subtract from the current Unix time, then format the result in the local timezone. Doing it in hours and then “fixing” the date by hand is where midnight errors come from.
Example: it is 01:10 on Wednesday. Three hours ago is 22:10 on Tuesday, not 01:10 minus 3 with the same date. A calendar app that only shows dates will not catch that. A clock that shows seconds will.
Watch the date line
Any offset larger than the time of day will cross yesterday. Any offset larger than 24 hours will cross more than one date. Keep the weekday in the result, not only HH:MM, so a log line can be sorted.
This site does that subtraction for you from the live clock at the top of the page. Enter 3, choose hours, choose ago, and you get both the time and the date.
When not to do it in your head
Do not count across daylight-saving changes, month ends, or timezones you do not live in. Those are the cases where “just subtract 8” produces a time that never existed locally, or existed twice.
If you need the same instant in another zone, convert the result to UTC first, then to the other zone. The UTC grid on each result page is there for that check.
Worked example: 01:10 minus three hours
Suppose the device clock shows 01:10:00 on Wednesday, 2 September 2026, in Asia/Singapore (UTC+08:00). Three hours ago is not 01:10 minus 3 with the same date. Convert three hours to 10,800 seconds, subtract from the Unix time of 01:10, then format again in the same zone.
The civil result is 22:10:00 on Tuesday, 1 September 2026. The weekday changed. Anyone who writes “01:10 − 3h = 22:10” and leaves Wednesday on the line has a wrong log. This is the whole reason the result pages print the date under the clock.
If you instead meant “yesterday at 01:10”, that is a one-day offset, not a three-hour offset. Open /1-day-ago. Mixing those two questions is the most common error on this site.
What the URL is doing
A path such as /3-hours-ago is a reusable question. It does not freeze 22:10. Reload it at 04:00 and the answer is 01:00. That is correct for a calculator and useless as an archive. When the number matters later, copy the displayed clock, date, and UTC offset into the ticket, then optionally keep the link as a way to repeat the method.
Same now, three different offsets
Device clock: Wednesday 01:10, Asia/Singapore. Each offset is a different civil time.
- 1 hour ago
- Tuesday 00:10 — still the previous calendar date
- 3 hours ago
- Tuesday 22:10 — previous evening, not “today minus 3”
- 1 day ago
- Tuesday 01:10 — yesterday at this time
Questions
Is “3 hours ago” always today minus three hours?
No. If the current time is before 03:00, three hours ago is yesterday. Always keep the date in the answer.
Should I use 24 hours ago or 1 day ago?
On this site they are calculated the same way: 24 × 60 minutes. Use 24 hours ago when you are thinking in hours; use 1 day ago / yesterday when you are thinking in calendar days.