Enter days, hours, minutes, and seconds to find the target date and time. Start from now or choose a custom baseline.
Start from
Start Date & Time
Base time
Tuesday, September 29, 2026 at 11:31:30 (11:31:30 AM)
Projected time
Tuesday, September 29, 2026 at 11:31:30 (11:31:30 AM)
An offset of 0 seconds ago before the base time occurred on Tuesday, September 29, 2026 at 11:31:30 AM.
Total Days
0.0000
Total Hours
0.000
Total Minutes
0.00
Total Seconds
0
Timestamp (Seconds)
1790652690
Timestamp (Milliseconds)
1790652690870
ISO 8601 (Local Time)
2026-09-29T11:31:30+08:00
ISO 8601 (UTC)
2026-09-29T03:31:30Z
Time Ago Calculator
This calculator subtracts a time offset from a base time to find an exact past date and time. Enter days, hours, minutes, and seconds, then use the current time or set a custom baseline. Results include local time, time zone, ISO 8601, and Unix timestamps.
Common Uses
Incident and ticket timelines
Use it to answer questions like “what time was it 45 minutes ago?” when you have an elapsed time but need a timestamp.
Time tracking and notes
Use a custom baseline when your reference point is a logged time. Copy ISO or Unix timestamps into a spreadsheet or report.
Common time-ago questions
Use this to keep everyone referencing the same timestamp in chat, tickets, or calendars.
The human-readable result follows the browser’s local timezone. Include the displayed zone or an ISO value when another person may be in a different timezone.
The local ISO output includes the current UTC offset, while the UTC ISO output ends in Z. Those two strings can describe the same instant with different clock times.
Notes
- Share a timezone or ISO value with the clock time.
- Do not assume another device uses the same local timezone.
Using a custom baseline
Use this for incident timelines, logs, and “when did this happen?” questions.
Hours, days, and weeks are applied as elapsed seconds. Across a daylight-saving transition, a 24-hour offset can display a different local clock hour.
The result depends on the device clock and timezone database. For incident or system logs, compare the UTC ISO and Unix timestamp with the source record.
Notes
- Review daylight-saving transitions in the relevant local timezone.
- Verify the device clock before using the result in an incident timeline.
Copying results into logs
Use this when you need a human-readable time plus a machine-readable timestamp.
Unix seconds and milliseconds identify the projected instant relative to the Unix epoch. Check which unit a destination API or spreadsheet expects before pasting the number.
ISO 8601 is useful for exchanging a timestamp, while the total-days, total-hours, total-minutes, and total-seconds cards describe the elapsed magnitude of the offset.
Notes
- Confirm whether a destination expects Unix seconds or milliseconds.
- Use UTC ISO when a timezone-neutral exchange format is needed.
Time zone and formatting notes
Use this for checklists and training examples where consistent offsets matter.
The combined calculator accepts non-negative whole days, hours, minutes, and seconds, converts them to one elapsed offset, and applies it once. Use a custom baseline to reproduce an example instead of relying on a live clock that changes every second.
For a worked check, compare the displayed base and result, then reverse the direction with the same offset. Calendar month-end and daylight-saving transitions can make the clock fields look asymmetric.
Notes
- Set a fixed example date before documenting a training result.
- Test zero and a date-rollover case when checking the workflow.
Visualizing the Past
If you prefer a quick lookup table, the unit chart pages show common offsets based on your local time when the chart loads. Examples include what time it was 11 hours ago, plus charts for days, weeks, and months ago.
Frequently Asked Questions
Related Lookback Tools
Last updated: September 16, 2026