How Many Days Since January 18

You're staring at a calendar. Maybe it's a spreadsheet. Maybe it's a legal document, a project deadline, or just a text message from three weeks ago that you're trying to place in time. The question is simple: how many days since January 18?

The answer changes every day. That's the whole point.

Today, as I write this, it's 147 days. By the time you read this, the number will be different again. In practice, tomorrow it'll be 148. But the method* for figuring it out? That stays the same. And surprisingly, a lot of people get it wrong — or at least make it harder than it needs to be.

What Is "Days Since" Actually Measuring

At its core, you're calculating the difference between two dates: a fixed anchor (January 18) and a moving target (today). Sounds trivial. But the devil lives in the details.

Are you counting January 18 itself as day zero or day one? Are you working in calendar days or business days? Are you including today? Does the year matter — meaning, are you asking about January 18 this year*, or January 18 of a specific past year?

Most people don't specify. They just want a number. But the number changes depending on those assumptions.

The inclusive vs. exclusive trap

Here's where almost everyone trips up. If today is January 19, how many days since January 18?

• Exclusive counting (most common in programming and date math): 1 day. You don't count the start date.
• Inclusive counting (common in human speech): 2 days. "It's been two days — the 18th and the 19th."

Neither is "wrong.So " But if you're calculating a deadline, a warranty period, or a legal statute of limitations, the difference matters. A lot.

Why the year changes everything

January 18, 2024 was a Thursday. In real terms, january 18, 2023 was a Wednesday. Also, january 18, 2025 falls on a Saturday. The day of the week shifts, obviously. But more importantly, leap years insert an extra day into the calendar every four years (mostly — century years not divisible by 400 skip it, but you knew that).

So "days since January 18" without a year attached is an incomplete question. On top of that, it's like asking "how far is it to Springfield? " without saying which Springfield.

Why People Actually Ask This

You'd be surprised how many scenarios hinge on this exact calculation.

Legal and compliance deadlines

Statutes of limitations. Contract notice periods. Even so, regulatory filing windows. Many of these are defined in calendar days from a specific triggering event — and that triggering event is often a date like January 18 (say, the date of an incident, a signing, or a notice delivery).

Miss the window by one day because you counted inclusively when the statute says exclusively? That's a malpractice suit waiting to happen.

Financial calculations

Accrued interest. Dividend ex-dates. So settlement periods (T+1, T+2). The financial world runs on precise day counts. And they don't all use the same convention — actual/actual, actual/360, 30/360, actual/365. Each gives a slightly different answer for the same date range.

Project management and sprint planning

"We're 47 days since the January 18 kickoff.Think about it: " That's a status update. But is it 47 calendar days or 33 business days? The team's velocity looks very different depending on which you use.

Personal milestones

Sobriety counters. Because of that, "Days since I quit smoking. " The psychology of round numbers is real — people hit 30 days, 90 days, 365 days and it means something. Relationship anniversaries. Getting the count right matters emotionally, not just mathematically.

How to Calculate It (Without Losing Your Mind)

You have options. Some are better than others.

The "just Google it" method

Type "days since January 18 2024" into Google. It'll give you the answer instantly. Which means works great for one-off questions. Fails if you need to do this repeatedly, programmatically, or for a range of years.

Spreadsheet formulas (Excel / Google Sheets)

This is where most professionals live. And it's easier than people think.

Basic calendar days:

=TODAY() - DATE(2024,1,18)

Format the result cell as a number, not a date. Done.

Business days only:

=NETWORKDAYS(DATE(2024,1,18), TODAY())

This excludes weekends. Add a holiday range as a third argument if you need to exclude federal holidays too.

Inclusive count (counting both start and end):

=TODAY() - DATE(2024,1,18) + 1

Pro tip: put the anchor date in a cell (say, A1) and reference it. Makes the formula readable and editable:

=TODAY() - A1

Programming approaches

Python (standard library):

For more on this topic, read our article on how many days until october 28 or check out how many concrete yards do i need.

For more on this topic, read our article on how many days until october 28 or check out how many concrete yards do i need.

from datetime import date
anchor = date(2024, 1, 18)
today = date.today()
delta = today - anchor
print(delta.days)  # exclusive count

JavaScript:

const anchor = new Date('2024-01-18');
const today = new Date();
const diffMs = today - anchor;
const diffDays = Math.floor(diffMs / (1000 * 60 * 60 * 24));
console.log(diffDays);

Watch out for time zones in JavaScript. new Date('2024-01-18') parses as UTC. The mismatch can shift your answer by a day. new Date() uses local time. Always specify time zones explicitly or use a library like date-fns or Luxon.

Command line (macOS / Linux)

# GNU date (Linux)
echo $(( ($(date +%s) - $(date -d '2024-01-18' +%s)) / 86400 ))

# macOS (BSD date)
echo $(( ($(date +%s) - $(date -j -f '%Y-%m-%d' '2024-01-18' +%s)) / 86400 ))

Quick, no dependencies, easy to alias.

Common Mistakes / What Most People Get Wrong

I've seen smart people make every one of these.

Forgetting leap years

Not in the "oh, 2024 is a leap year" sense — people know that. In real terms, the year 2100 is not a leap year (divisible by 100 but not 400). Some custom code doesn't. But in the "my spreadsheet formula breaks in 2100" sense. Most Excel formulas handle this correctly. If you're building something that needs to work decades out, test it against 2099-2101.

Time zone drift

You calculate "days since January 18" at 11:30 PM on March 15. Your server is in UTC. Your user is in Los Angeles. For the user, it's still March 15. For the server, it's March 16. You just gave them the wrong number.

Always anchor your "today" to a specific time zone — preferably the user's, or UTC with clear labeling

Inclusive vs Exclusive Counting

Most people assume "days since" means excluding the start date. But sometimes you want to include both January 18 and today. That's why the spreadsheet example adds 1:

=TODAY() - DATE(2024,1,18) + 1

This matters for things like warranty periods, project durations, or any scenario where the starting day counts as day one.

Weekend and Holiday Logic

The NETWORKDAYS function in spreadsheets is powerful but has quirks. It counts the start date if it's a weekday, and the end date if it's a weekday. So if your project starts on a Monday and ends on a Friday, you get 5 business days. But if it starts on a Saturday and ends on Monday, you might get 1 or 2 depending on your holiday settings.

For custom logic, you'll need to filter out specific dates from your calculation.

Platform-Specific Gotchas

Excel vs Google Sheets: Google Sheets sometimes handles dates differently based on your locale settings. A date entered as 1/18/2024 might be interpreted as January 18th or December 1st depending on regional settings.

Python's datetime vs date: Using datetime.now() instead of date.today() can introduce time components that mess up your calculations. Stick to date objects for pure day counting.

JavaScript Date Objects: The Date constructor treats string inputs inconsistently. new Date('2024-01-18') is UTC, but new Date('2024-01-18T00:00:00') is local time. This subtle difference causes real bugs.

Testing Your Implementation

Always test edge cases:

• Same day (should be 0 or 1 depending on inclusive/exclusive)
• One day apart
• Across month boundaries
• Across year boundaries, especially leap years
• Daylight saving time transitions

When to Use What

Quick one-off: Spreadsheet formula. Fastest to implement.

Repeated use by humans: Spreadsheet with named ranges. Others can understand and modify it.

Automated systems: Python or JavaScript. Better error handling, logging, and integration.

System scripts or pipelines: Command line. No GUI needed, easy to automate.

Web applications: JavaScript with a date library. Handles user-facing calculations.

Conclusion

Counting days seems trivial until you need to do it reliably across different contexts and timeframes. Because of that, the key is matching your tool to your use case: spreadsheets for human interaction, code for automation, and command line for system tasks. Always account for time zones, leap years, and whether you need inclusive or exclusive counting. Test your logic against edge cases before deploying it in production. The few minutes spent getting this right upfront save hours of debugging later.