How Many Hours In 15 Days

You’re staring at a project plan. Or maybe a vacation request form. Which means a freelance contract says "15 business days. " A shipping estimate promises delivery in "15 days." Your brain immediately asks the same question: Okay, but how many hours is that actually?

It sounds like a trick question. Think about it: it isn't. But the answer changes depending on why you’re asking.

What Is 15 Days in Hours

The mathematical answer is boring. 15 days × 24 hours = 360 hours. That’s the raw, physics-based number. Earth rotates fifteen times. Done.

But nobody lives in raw physics. We live in shifts, time zones, sleep cycles, and "business hours." If you’re calculating server uptime, 360 is your number. If you’re calculating how long you have to finish a client deliverable, 360 is a dangerous fantasy.

Let’s break down the versions of this number that actually matter.

The raw number

360 hours. 21,600 minutes. 1,296,000 seconds. This is the "wall clock" total. Use it for: battery life estimates, continuous integration pipelines, how long a 3D print takes, or the runtime of a very long Twitch stream.

The "business hours" version

Standard US work week: 8 hours a day, 5 days a week. 15 calendar* days usually spans three weeks. That’s roughly 11 to 12 business days depending on where the weekends fall. At 8 hours a day, you’re looking at 88 to 96 working hours. Not 360. Big difference.

The "awake hours" version

Average adult sleeps 7–8 hours. That leaves 16–17 waking hours per day. Over 15 days: 240 to 255 conscious hours. Subtract meals, commutes, scrolling, and you’re down to maybe 180 "productive" hours. That’s the real budget for a side project.

The shift-work version

Three 8-hour shifts cover 24 hours. 15 days = 45 shifts. Two 12-hour shifts? 30 shifts. Four 10-hour shifts with overlap? You do the math — but the point is, "15 days" on a schedule is a totally different beast than "15 days" on a calendar.

Why It Matters / Why People Care

You might think this is trivial. Day to day, multiply by 24. Move on. But people mess this up constantly, and it costs money, sleep, and credibility.

Project estimates that implode

A freelancer quotes "15 days" for a build. The client hears "15 days × 8 hours = 120 hours of work." The freelancer means "I’ll fit it in over 15 calendar days while doing other stuff." The client gets mad on day 10 when the thing isn’t done. The freelancer burns the weekend. Nobody wins.

Shipping and logistics

"Delivers in 15 days." Is that business days? Calendar days? Does the day of pickup count? Day 15 at 5 PM or midnight? If you’re promising a customer a refund if it’s late, you need the exact hour cutoff. 360 hours from when*?

Shift scheduling and payroll

A nurse works 3-day weeks, 12-hour shifts. 15 days is five shifts. 60 hours. But if they pick up overtime on their "off" days, 15 calendar days could mean 84 hours. Payroll breaks if you assume a flat conversion.

Travel and jet lag

You have 15 days in Japan. That’s 360 hours. But the first two days are zombified by jet lag. The last day is packing and transit. You really have ~300 usable* hours. Plan for 360, you’ll overcommit. Plan for 300, you might actually see Kyoto.

Server SLAs and uptime

"99.9% uptime over 15 days." That allows 43.2 minutes of downtime total. Not per day. Total. If you’re the on-call engineer, you know that number by heart. 360 hours. 43 minutes of red alert budget. Sleep with your phone loud.

How It Works (or How to Calculate It)

The math is simple. The context is where people trip. Here’s how to derive the number you actually need.

Step 1: Define your "day"

• Calendar day: Midnight to midnight. 24 hours. ×15 = 360.
• Business day: Usually 8 hours, Mon–Fri. Count the weekdays in your 15-day window. Multiply by 8 (or your shift length).
• Working day (your actual capacity): Be honest. 6 focused hours? 4? Multiply that by the number of days you’ll actually* work.

Step 2: Count the weekdays in the window

Don’t guess. Open a calendar. Count Mon–Fri.

• 15 days starting Monday: 11 weekdays (Mon–Fri ×2, plus Mon–Wed of week 3). 88 hours @ 8h/day.
• 15 days starting Saturday: 10 weekdays. 80 hours.
• 15 days starting Thursday: 11 weekdays. 88 hours.
• Holidays? Subtract them.

Step 3: Adjust for partial days

Day 1: You start at 2 PM. Day 15: You finish at noon. Those aren't full days.

• Start day: hours remaining in your work window.
• End day: hours worked before deadline.
• Middle days: full count.

Step 4: Convert to minutes or seconds if precision matters

• 360 hours × 60 = 21,600 minutes.
• 21,600 × 60 = 1,296,000 seconds.
• Milliseconds? 1,296,000,000 ms.
• Unix timestamp math: 15 × 86,400 = 1,296,000 seconds. Add to start epoch.

Step 5: Spreadsheet it

Don't do mental math for anything that bills money.

For more on this topic, read our article on how many months is 118 days or check out how many weeks is 16 days.

• Excel/Sheets: =NETWORKDAYS(start_date, end_date, holidays) * hours_per_day
• For raw hours: =(end_datetime - start_datetime) * 24
• Format the cell as [h]:mm to see total hours past 24.

Step 6: Time zones and DST

If your 15-day window crosses a daylight saving shift, you lose or gain an hour.

• Spring

A nurse works 3-day weeks, 12-hour shifts. 15 days is five shifts. Day to day, 60 hours. But if they pick up overtime on their "off" days, 15 calendar days could mean 84 hours. Payroll breaks if you assume a flat conversion.

Travel and jet lag

You have 15 days in Japan. That's 360 hours. But the first two days are zombified by jet lag. The last day is packing and transit. You really have ~300 usable* hours. Plan for 360, you'll overcommit. Plan for 300, you might actually see Kyoto.

Server SLAs and uptime

"99.9% uptime over 15 days." That allows 43.2 minutes of downtime total. Not per day. Total. If you're the on-call engineer, you know that number by heart. 360 hours. 43 minutes of red alert budget. Sleep with your phone loud.

How It Works (or How to Calculate It)

The math is simple. The context is where people trip. Here's how to derive the number you actually need.

Step 1: Define your "day"

• Calendar day: Midnight to midnight. 24 hours. ×15 = 360.
• Business day: Usually 8 hours, Mon–Fri. Count the weekdays in your 15-day window. Multiply by 8 (or your shift length).
• Working day (your actual capacity): Be honest. 6 focused hours? 4? Multiply that by the number of days you'll actually* work.

Step 2: Count the weekdays in the window

Don't guess. Open a calendar. Count Mon–Fri.

• 15 days starting Monday: 11 weekdays (Mon–Fri ×2, plus Mon–Wed of week 3). 88 hours @ 8h/day.
• 15 days starting Saturday: 10 weekdays. 80 hours.
• 15 days starting Thursday: 11 weekdays. 88 hours.
• Holidays? Subtract them.

Step 3: Adjust for partial days

Day 1: You start at 2 PM. Day 15: You finish at noon. Those aren't full days.

• Start day: hours remaining in your work window.
• End day: hours worked before deadline.
• Middle days: full count.

Step 4: Convert to minutes or seconds if precision matters

• 360 hours × 60 = 21,600 minutes.
• 21,600 × 60 = 1,296,000 seconds.
• Milliseconds? 1,296,000,000 ms.
• Unix timestamp math: 15 × 86,400 = 1,296,000 seconds. Add to start epoch.

Step 5: Spreadsheet it

Don't do mental math for anything that bills money.

• Excel/Sheets: =NETWORKDAYS(start_date, end_date, holidays) * hours_per_day
• For raw hours: =(end_datetime - start_datetime) * 24
• Format the cell as [h]:mm to see total hours past 24.

Step 6: Time zones and DST

If your 15-day window crosses a daylight saving shift, you lose or gain an hour.

• Spring forward: lose one hour. Your 360-hour deadline becomes 359 hours of actual work time.
• Fall back: gain one hour. You get 361 hours. Build that into your buffer.
• Multiple time zones? Convert everything to UTC first. Then apply local business rules.

Step 7: Factor in human friction

This is where most calculations fail.

• Meetings scheduled across time zones that nobody remembers to reschedule after DST changes.
• Email replies that take 24 hours because someone's "out of office" includes a weekend.
• The three-hour delay when your teammate in Tokyo wakes up and reads your 8 AM request at 11 AM their time.

Step 8: The reality check

After all that, ask yourself: what's the minimum viable number that still gets the job done? Often it's not 360 hours. It's 240. Or 180. The difference between 360 and 180 is the difference between surviving and thriving.

Final thought: Every 360-hour project has a hidden 720-hour version that includes all the retries, the rework, the context switching, and the inevitable "let's just start over." Plan for 360. Budget for 720. That's how you ship.