How the date difference is counted
Most elapsed-time calculations use a half-open interval: the start is included and the end is excluded. A booking from July 1 to July 2 lasts one night, even though two date labels appear. This calculator follows that convention by default. Selecting “include end date” adds one calendar day and adds the end day to the business-day count when it falls Monday through Friday.
calendar days = |UTC end date − UTC start date| ÷ 86,400,000 ms
inclusive calendar days = calendar days + 1
business days = weekdays in [earlier date, later date)
inclusive business days also test the later dateThe implementation converts each date-only value to midnight UTC before subtraction. That is deliberate: local daylight-saving changes can create 23-hour or 25-hour civil days, but March 7 to March 9 is still two calendar dates apart. UTC date-only arithmetic also handles leap day directly. If the dates are entered in reverse, the tool shows the absolute interval and labels that choice rather than returning a confusing negative count.
Worked examples and the off-by-one rule
In leap year 2024, February 28 to March 1 is two elapsed days: February 28 to February 29, then February 29 to March 1. Including the end date counts February 28, February 29, and March 1, so the result becomes three. For a same-day interval, the default elapsed difference is zero; including the end counts that one named day.
For business days, Friday July 10 to Monday July 13 contains one weekday in the default half-open interval: Friday. Turning on inclusive mode also counts Monday, producing two. Saturday and Sunday are always excluded. This definition is useful for rough schedules but is not a settlement calendar, payroll calendar, or legal deadline engine.
What “business days” means here
| Day | Counted? | Important limitation |
|---|---|---|
| Monday–Friday | Yes | Unless it is the excluded end boundary |
| Saturday–Sunday | No | Always treated as weekend |
| Public holiday | Yes | No country or market calendar is assumed |
| Observed holiday | Yes | Rules vary by jurisdiction and employer |
Public holidays vary by country, region, exchange, bank, and employer. A static worldwide tool cannot claim a holiday count without asking for a jurisdiction and maintaining official calendars. Add or subtract relevant holidays manually, and confirm any contractual or regulatory deadline with the governing source.
Useful planning connections
A date count can define a measurement window, but it does not make the underlying assumption accurate. The TDEE calculator, for example, recommends calibrating an estimate across a consistent multiweek trend. The drawdown recovery calculator can pair an underwater duration with the gain still required. Traders can set risk before entry with the position size calculator, and travelers can combine trip length with usage in the eSIM data calculator.
Frequently asked questions
Should I include the end date when counting days?
Include it when you mean named calendar dates touched, such as every day of an event. Exclude it when you mean elapsed time, nights, or the interval before a deadline. State the convention whenever the answer affects money, work, travel, or a legal obligation.
Why is the same start and end date zero days?
The default measures elapsed distance between date boundaries, and no time separates a date from itself. Turning on “include end date” changes the question to how many named dates are included, so the same start and end becomes one calendar day.
Does the business-day result remove public holidays?
No. It counts Monday through Friday only. Public and observed holidays differ by country, state, market, bank, and employer, so silently choosing one calendar would create false precision. Check the relevant official calendar and subtract applicable holidays manually.
Does daylight saving time change the answer?
Not for calendar-day results. The calculator uses UTC date-only values, so a 23-hour or 25-hour local day still counts as one calendar day. If you need exact elapsed hours across time zones, use timestamps with explicit zones rather than date-only fields.