The duration calculator measures between two known moments; it cannot find an unknown date. Counting back gives it: 180 days before October 27, 2026 is April 30, 2026; 45 business days after October 26, 2026 is December 28, 2026; and months have no row because a month is not a fixed length.

What the tool does, and what it does not

The time duration calculator measures between two moments you already know. Give it a start date and an end date and it returns the exact elapsed time. What it cannot do is find a moment you do not know: “180 days ago” is not a duration question, it is a date question, because the answer is a date, not a length of time. The distinction matters, because the two jobs need different inputs. A duration needs two known moments. A days-ago question gives you one known moment — today — and a length, and asks for the other moment. This article shows how to find that moment by hand, and where the calculator fits once you have it.

The honest workflow is two steps. First, count back (or forward) across the calendar to find the unknown date, using the method below. Second, if you need the duration in hours or minutes as well, enter both dates into the calculator and read the exact span. The counting method is the skill; the calculator is the check. And the same two-step workflow covers business days, except the counting step skips weekends — a difference that changes every answer, as the business-days section shows.

Counting back: days ago, by hand

Counting back across month boundaries is the whole skill, and it has one rule: subtract within the current month first, then step back a whole month at a time. To find 180 days before October 27, 2026: October 27 minus 27 days lands on September 30 (27 days used, 153 to go); minus 30 days lands on August 31 (57 used, 123 to go); minus 31 lands on July 31 (88 used, 92 to go); minus 31 lands on June 30 (119 used, 61 to go); minus 30 lands on May 31 (149 used, 31 to go); minus 31 lands on April 30 (180 used). So 180 days before October 27, 2026 is April 30, 2026. The check is the forward trip: April 30 plus 180 days is October 27, because May contributes 31, June 30, July 31, August 31, September 30, and October 27 — and 31 + 30 + 31 + 31 + 30 + 27 = 180.

A shorter example confirms the method. One hundred days before October 27, 2026: October 27 minus 27 days is September 30 (27 used, 73 to go); minus 30 is August 31 (57 used, 43 to go); minus 31 is July 31 (88 used, 12 to go); minus 12 is July 19. So 100 days before October 27, 2026 is July 19, 2026, and the forward check — July 19 plus 100 days — lands back on October 27. The method works forward identically: 90 days after January 1, 2026 is April 1, 2026, because January contributes 30 more days (to January 31), February 28 (to February 28), March 31 (to March 31), and 1 more day reaches April 1 — 30 + 28 + 31 + 1 = 90.

Business days are not calendar days

A business day is a Monday-to-Friday day, and a span counted in business days is always longer in calendar days than its number suggests — roughly 7 calendar days for every 5 business days, plus edge effects from where the count starts. The counting convention used here, stated so it can be checked: count Monday-to-Friday days after the start date, skipping Saturdays and Sundays, and do not exclude public holidays, because holidays vary by place and the count here is a weekday count, not a holiday calendar. Under that convention, 10 business days after Friday, October 23, 2026 is Friday, November 6, 2026: the count skips two weekends and lands two calendar weeks later. And 45 business days after Monday, October 26, 2026 is Monday, December 28, 2026 — 63 calendar days later, because 45 business days are exactly 9 working weeks.

The two traps in business-day counting are the start day and the holidays. Counting the start day itself as day 1 shifts every answer one business day earlier than the convention above — always confirm whether a deadline means “10 business days after” (start excluded, as here) or “within 10 business days” (which some readers count inclusively). And a span crossing a public holiday overstates the working days if holidays are not removed: a 10-business-day span crossing one holiday contains only 9 working days. For legal or contractual deadlines, count against the applicable holiday calendar, not this weekday-only method; for planning estimates, the weekday method is the right first approximation, and the calculator’s calendar-day span is the wrong tool for the job entirely — it counts every day, weekends included.

Why there is no months row — and no years row

The calculator’s breakdown stops at weeks for a reason: months and years are not fixed lengths. A “month” can be 28, 29, 30, or 31 days, so a span of 60 days is 2 months from January 1 (January 31 days plus February 28 in a common year, with a day to spare) but not 2 months from any other starting point in the same way — and a span described as “11 years, 8 months, 24 days” is a calendar description tied to specific start and end dates, not a duration that can be converted without them. Weeks, days, hours, minutes, and seconds are fixed; months and years are calendar constructs, and mixing the two kinds in one breakdown would produce numbers that do not add back up.

The related edge case is January 31 plus one calendar month, which has no single answer: February has 28 days in 2026 and 29 in a leap year, so “one month after January 31” is claimed as both February 28 and March 1 by different conventions, and neither is wrong — the question itself is underspecified. The safe practice is to state durations in days for anything contractual (“within 90 days”), and to reserve months and years for calendar descriptions tied to named dates (“from January 2026 to March 2026”). When a duration must be expressed in months, name the start and end dates alongside it, so the reader can verify the count instead of trusting a conversion.

Leap years change nothing — except the count

Deadlines: inclusive, exclusive, and why documents differ

Deadline counting adds one more convention to the business-day problem: whether the start day itself counts. A notice served on January 1 with a “30 days” deadline lands on January 31 if the count starts the day after service (January 2 as day 1, through January 31 as day 30), but on January 30 if the service day itself counts as day 1 (January 1 through January 30). Both counts are “30 days” under their own convention, and the one-day difference is exactly the kind of gap that decides a filing. The only safe move is to read the document’s own counting rule — most legal and contractual texts state whether the trigger day is included or excluded — and to state your convention in writing when you set a deadline yourself.

The same inclusive-exclusive question hides inside “days ago” phrasing. “Three days ago” from a Friday usually means Tuesday, counting Friday as today and stepping back three days — but a system that counts “3 × 24 hours ago” from Friday at 3:00 PM lands on Tuesday at 3:00 PM, the same date, so the two readings agree on the date and differ only on the hour. Where they disagree is at boundaries: “1 day ago” from just after midnight can mean yesterday’s date under calendar counting, but only a few hours back under elapsed counting. For dates, calendar counting is the usual reading; for spans, elapsed time is. Say which one you mean, and the ambiguity disappears.

Leap years need no special rule in duration arithmetic, because the counting never assumes month lengths: it counts actual days. February 28 to March 1 is 2 days in the leap year 2024, because February 29 sits between them, and 1 day in the common year 2025. The counting-back method above already handles this automatically, because it steps through real month lengths: counting back across February 2024 subtracts 29 days for the month, while counting back across February 2025 subtracts 28. The only leap-year error is assuming February always has 28 days, which undercounts any span crossing a February 29 by exactly one day — the same one-day error that breaks date arithmetic in spreadsheets every fourth year.

Frequently asked questions

How do I find the date 180 days ago?

Count back across real month lengths. From October 27, 2026: 27 days back reaches September 30, then 30 to August 31, 31 to July 31, 31 to June 30, 30 to May 31, and 31 to April 30, 2026 — 180 days in total. Check by counting forward: April 30 plus 180 days is October 27.

What is the difference between business days and calendar days?

Business days skip Saturdays and Sundays. Forty-five business days after Monday, October 26, 2026 is Monday, December 28, 2026 — 63 calendar days later, because 45 business days are exactly 9 working weeks. The calculator counts calendar days, so it cannot count business days.

Does the calculator count business days?

No. It counts every calendar day, weekends included. Business-day counting needs a weekday count, and for legal deadlines a holiday calendar as well, since a span crossing a public holiday contains fewer working days than its weekday count suggests.

Why does the calculator show weeks but not months or years?

Because weeks are fixed (7 days) while months and years are not: a month is 28, 29, 30, or 31 days, so a span in months cannot be converted without its start and end dates. The breakdown stops at weeks so its rows always add back up to the same total.

How do leap years affect a duration?

Only by adding one real day. February 28 to March 1 is 2 days in the leap year 2024, because February 29 sits between them, and 1 day in the common year 2025. Counting actual days handles leap years automatically; assuming February always has 28 days undercounts by one.

How do I find a date 90 days from now?

Count forward across real month lengths. Ninety days after January 1, 2026 is April 1, 2026: 30 days to January 31, 28 to February 28, 31 to March 31, and 1 more day to April 1. Then, if you need the span in hours, enter both dates into the calculator.