Calculating the gap between today and June 23
It's a straightforward subtraction problem, but people keep making it harder than it needs to be. I see the same mistakes repeated in thread after thread, usually because someone is trying to do it by hand or using a tool that doesn't account for leap years properly. The quick answer depends entirely on what today's date is. If you're reading this and today is say, May 1st, then June 23rd is 53 days away. If it's January 15th, it's roughly 159 days. The exact number shifts every single day, which is why a static answer won't help you here. I used to build custom scripts to handle these calculations for scheduling software back when I was doing dev work. One thing that always caught people off guard: June 23rd falls on different weekdays depending on the year, and if you're working with event planning or payroll systems, the weekday matters way more than the raw day count. A 53-day gap in a leap year isn't the same as a 53-day gap in a non-leap year when you're mapping out business days.
Here's how to actually calculate it yourself without overcomplicating things.
Do it in your head or use a simple formula
Break it down month by month. June 23 is the 174th day of a non-leap year (23 + 31 + 28 + 31 + 30 + 23). In a leap year, it's the 175th day. Subtract the day-of-year number of today from that, and you've got your answer for the current year. If June 23 has already passed this year, add 365 (or 366 for a leap year) to 174 before subtracting. That gives you the days until next year's June 23. Simple. For something more reliable than mental math, here's a compact script that handles leap years correctly and spits out the exact count:
Get the Full Details
from datetime import date This ran in production for a client of mine for about three years without a single bug. The only time it ever threw a wrench in things was when their server clock drifted by a few hours during a daylight saving transition, and the date comparison flipped by one day. We fixed it by forcing the comparison to UTC.
today = date.today()
target = date(today.year, 6, 23)
if target < today:
target = date(today.year + 1, 6, 23)
print((target - today).days)
Online tools and spreadsheets
If you don't want to write code, Google itself will calculate this for you. Type "days between today and June 23" into the search bar and it shows the answer immediately. Excel and Google Sheets handle it just as easily with a formula like =DATE(2026,6,23)-TODAY(). Put that in a cell and it updates every day without you touching it. I recommend the spreadsheet approach if you need to track this repeatedly. One cell for the target date, one for today, and one that auto-calculates the difference. Set it up once and walk away.
Common mistakes to avoid
People often forget that the day count is exclusive of the start date but inclusive of the end date, depending on which convention their system uses. Some calendars count from zero, others from one. If you're integrating this into a booking system, shipping window, or subscription cycle, get clear on whether day zero counts as day one before you ship anything. Another issue I run into constantly: time zones. If your target date is June 23 at midnight local time and your user is in a different timezone, the day count can be off by one. Always normalize to UTC before comparing dates if your users span multiple regions. The raw number of days until June 23 isn't useful on its own if you're planning around it. Business days, weekends, and holidays matter far more in practice. A 30-day stretch might only contain 21 working days depending on where it lands. I learned that the hard way when a client complained that our "30-day delivery window" took 42 calendar days because we'd silently dropped weekends from the calculation without telling anyone.
Use the tools that are already built into your OS or browser. They're accurate, they're free, and they handle leap years for you. There's almost never a reason to calculate this by hand unless you're doing it for fun or for a test that forbids calculators.
