How Many Days Ago Was February 20

You stare at the screen. Because of that, maybe it’s a birthday you forgot. Maybe it’s a contract deadline. Maybe you’re just trying to figure out how long it’s been since that thing happened on February 20.

You type the question into Google. How many days ago was February 20?*

The answer pops up instantly. A number. Clean. Definitive.

But here’s the thing — that number is already wrong. Or it will be in a few hours. Or it was wrong the moment you read it because the calculator assumed midnight UTC and you’re in Denver.

Time math looks simple. It’s not. And if you’re making decisions based on a raw day count — legal filings, medical windows, project milestones — the difference between “342 days” and “343 days” isn’t academic. It’s the difference between on time and late.

What Is “Days Ago” Anyway

It sounds like a subtraction problem. Today minus February 20. Done.

But “days ago” is slippery. Are we counting calendar days? Business days? Because of that, do we include the start date, the end date, or neither? Does February 20 at 11:59 PM count as the same day as February 20 at 12:01 AM?

Most online calculators default to calendar days elapsed* — meaning they count the number of midnights between the two dates. If today is March 1 and you ask about February 20, you’ll get 9 days (in a non-leap year). But if you’re a human thinking “it’s been a week and a half,” you might feel like the answer should be 10.

Neither is wrong. They’re just different definitions.

The Inclusive vs. Exclusive Trap

This is where people trip up.

Exclusive counting* (standard in programming and most date libraries):
Feb 20 → Feb 21 = 1 day elapsed.

Inclusive counting* (common in legal contracts, hospital stays, hotel nights):
Feb 20 → Feb 21 = 2 days (you count the night of the 20th and the night of the 21st).

Excel’s DAYS function uses exclusive. NETWORKDAYS uses inclusive. Practically speaking, google Sheets does the same. Your HR portal might do something else entirely.

If you’re calculating “how many days since Feb 20” for a refund window that says “within 30 days of purchase,” you need to know which convention the policy uses. Guessing gets you denied claims.

Why It Matters More Than You Think

You might wonder why anyone writes a whole article about a date calculation. Fair question.

But date math shows up in the quiet infrastructure of adult life:

• Statutes of limitations. A claim filed on day 366 instead of 365 gets dismissed. Courts don’t care that your calculator said 365.
• Medical protocols. “Return in 14 days” after surgery. Day 14 or day 15? The clinic’s scheduling software might count differently than you do.
• Visa and immigration. “90 days within any 180-day period” in the Schengen zone. Mess up the count by one day and you’re facing a ban.
• Subscription renewals. “Cancel 7 days before renewal.” Is that 7 full 24-hour periods? Or 7 calendar midnights?
• Project management. “T-minus 30 days to launch.” If the team counts business days and the client counts calendar days, the launch meeting gets awkward.

The February 20 example isn’t special. Any fixed date becomes a moving target the moment you try to measure distance from today. And today never sits still.

How to Calculate It — Without Guessing

You have options. The right one depends on stakes, tools, and how allergic you are to spreadsheets.

1. The “Good Enough” Way: Online Calculators

Type “days between dates calculator” into any search engine. You’ll get a dozen sites. Practically speaking, timeanddate. com, Calculator.net, Omni Calculator — they all work roughly the same way.

Put in February 20 as the start date. Put in today as the end date. Hit calculate.

Watch for these settings:

• Include end date?* Toggle this based on your definition (see the inclusive/exclusive trap above).
• Time zone?* Most default to UTC. If you’re in Los Angeles and it’s 10 PM on March 1, UTC is already March 2. The calculator might say “10 days” when you feel like it’s 9.
• Leap year handling?* Good calculators handle this automatically. Bad ones don’t. February 20 to March 20 is 28 days in 2023, 29 days in 2024. A hardcoded “28 days” answer is wrong half the time.

2. The Spreadsheet Way: Excel / Google Sheets

If you do this more than once a month, learn the formulas. They’re transparent, auditable, and you can build a template once and reuse it forever.

Continue exploring with our guides on what is 1 4 of 2 3 and how many days until 9th june.

Basic calendar days (exclusive):

=DAYS(end_date, start_date)

Example: =DAYS(TODAY(), DATE(2024,2,20))
Returns the number of midnights between Feb 20 and today. Updates automatically every time you open the sheet.

Basic calendar days (inclusive):

=DAYS(end_date, start_date) + 1

Or use DATEDIF with the "d" unit — but DATEDIF is a legacy function with quirks. DAYS is cleaner.

Business days only:

=NETWORKDAYS(start_date, end_date, [holidays])

This counts Monday–Friday. Add a holiday range if you need to exclude federal holidays, company shutdowns, or your cousin’s wedding.

Pro tip: Put the start date in cell A1, the end date in B1 (or TODAY()), and the formula in C1. Label everything. Future you will thank present you.

3. The Developer Way: Code

If you’re building this into an app, script, or automation — don’t write your own date math. Use a library.

JavaScript: date-fns or luxon (avoid Moment.js — it’s legacy and huge).

import { differenceInCalendarDays } from 'date-fns';
const days = differenceInCalendarDays(new Date(), new Date(2024, 1, 20)); // month is 0-indexed

Python: datetime in the standard library is fine for

3. The Developer Way: Code

If you’re building this into an app, script, or automation — don’t write your own date math. Use a library.

JavaScript: date-fns or luxon (avoid Moment.js — it’s legacy and huge).

import { differenceInCalendarDays } from 'date-fns';
const days = differenceInCalendarDays(new Date(), new Date(2024, 1, 20)); // month is 0-indexed

Python: datetime in the standard library is fine for basic cases.

from datetime import date
start = date(2024, 2, 20)
today = date.today()
delta = (today - start).days  # exclusive count

Go: The time package handles this cleanly.

days := int(time.Since(time.Date(2024, 2, 20, 0, 0, 0, 0, time.UTC)).Hours() / 24)

Key gotchas across languages:

• Months are zero-indexed in JavaScript and Go (February = month 1, not 2).
• Time zones matter when comparing timestamps. Normalize to UTC if you’re unsure.
• Daylight saving time can shift your count by an hour — and if you’re dividing by 24, that matters.

The Human Factor: When Precision Isn’t the Point

Sometimes you don’t need an exact count. Sometimes you need a rough sense of how long something has been going on.

For personal milestones — “It’s been three months since I started running” — approximate is fine. But people understand that “three months” means somewhere between 89 and 92 days. The emotional truth outweighs the mathematical one.

But for contracts, deadlines, billing cycles, or compliance reporting, precision is non-negotiable. A single day’s discrepancy can mean a late fee, a missed SLA, or a legal dispute. That's why in those cases, document your method. Note whether you’re counting inclusive or exclusive. Specify the time zone. Write it down so the next person doesn’t have to reverse-engineer your logic.

Final Recommendation

Pick your method based on frequency and consequence:

• Once in a blue moon? Use an online calculator. Just check the settings.
• Monthly or recurring? Build a spreadsheet template. It pays for itself in five uses.
• Built into software? Use a proper date library. Never roll your own.
• High-stakes or auditable? Document your assumptions. Write them on the spreadsheet, in the code comment, in the email. Make it impossible for someone else to misinterpret.

And remember: the date you’re measuring from doesn’t change. The date you’re measuring to does — every single day. That’s not a bug in your calculation. It’s the point.