1pm To 7pm Is How Many Hours

You're staring at a schedule. Maybe it's a shift roster. Maybe it's a meeting invite from a colleague three time zones over. The block says 1pm to 7pm and your brain does that quick thing — wait, is that six hours or seven?

It's six. But you'd be surprised how often people second-guess it.

What Is the Answer (and Why It Trips People Up)

1pm to 7pm is six hours. Count it on your fingers if you need to: 1 to 2, 2 to 3, 3 to 4, 4 to 5, 5 to 6, 6 to 7. In practice, six jumps. Full stop. Six hours.

So why does it feel tricky? " No. On the flip side, you don't. We see "1" and "7" and something in us wants to say "seven minus one equals six... but wait, don't I count the starting hour?Because human brains love inclusive counting. Here's the thing — the hour between* 6 and 7 is the sixth. The hour between* 1 and 2 is the first hour. You're measuring spans, not tick marks.

This trips up payroll. It trips up freelancers billing clients. It trips up parents calculating babysitter costs. And it absolutely trips up anyone trying to coordinate across time zones where the day boundary gets involved.

The midnight crossover trap

Here's where it gets spicy. In real terms, 1pm to 7pm is easy. But 10pm to 2am? On top of that, your brain sees 10 and 2 and wants to subtract. 2 minus 10 is negative eight. And wrong. You're crossing midnight. Also, the math becomes: hours left in the day (2) plus hours into the next day (2) equals four. Or just do 24 minus 10 plus 2. Sixteen? So naturally, no. Still, four. Because 10pm to midnight is two hours. Midnight to 2am is two hours. Total: four.

The 12-hour clock makes this weird. The 24-hour clock (13:00 to 19:00) makes it obvious: 19 minus 13 equals 6. Done.

Why This Simple Calculation Matters

Money. That's the short answer.

If you're hourly, six hours at $25 is $150. Over a year? Plus, seven hours is $175. That $25 difference adds up fast over a month. We're talking thousands.

But it's not just payroll. That said, a developer tells a client "this takes six hours" and the client schedules it 1pm to 7pm thinking they've got a buffer. No lunch. No "wait, where was I?They don't. No context switching. On top of that, they've got exactly the estimate. It's project estimates. " time.

It's also about boundaries. A shift listed as 1pm–7pm sounds like a standard six-hour block. But if the employer expects you there* at 12:45 for handover and you can't leave until 7:15 because the relief is late? That's not six hours anymore. Practically speaking, that's six and a half. Think about it: maybe seven. Worth adding: over a five-day week, that's 2. 5 to 5 hours of unpaid time. "Just fifteen minutes" is the most expensive phrase in shift work.

The lunch deduction nobody talks about

Here's a real-world wrinkle. Sometimes paid, sometimes not. In many jurisdictions, a six-hour shift requires* a meal break. 5 hours of actual work. If it's unpaid, your 1pm–7pm block just became 5.Or 5 hours if they give you a full hour.

But some employers schedule 1pm–7pm specifically* to skirt the break requirement — six hours is often the threshold. Maybe. Sneaky? Because of that, legal? Depends on local labor law. Worth knowing your rights.

How to Calculate Time Differences Like a Pro

Stop doing mental gymnastics. Use tools. But also understand the principles so you catch errors.

The subtraction method (same day, no midnight cross)

End hour minus start hour. In 12-hour terms: 7 - 1 = 6. 19 - 13 = 6. This works only* when both times are am or both are pm and you're not crossing noon/midnight.

The "add up to the boundary" method

Crossing noon? Hours past midnight: 2. That's why crossing midnight? Because of that, hours past noon: 2. Which means hours to noon: 2. Total: 4. That said, 10pm to 2am. 10am to 2pm. That said, hours to midnight: 2. Total: 4.

This scales. On the flip side, 8am to 10pm? Because of that, 4 hours to noon + 10 hours past noon = 14 hours. Check: 22 - 8 = 14. Works.

The 24-hour conversion (safest for mixed schedules)

Convert everything to 24-hour time first. 1pm = 13:00 7pm = 19:00 19 - 13 = 6.Practically speaking, 10pm = 22:00 2am = 02:00 (next day) (24 - 22) + 2 = 4. Or: 26 - 22 = 4 if you treat next-day 2am as 26:00.

This eliminates the "am/pm" confusion entirely. " Count the steps between any two numbers. On top of that, i keep a sticky note on my monitor: "13 14 15 16 17 18 19 20 21 22 23 0 1 2 3 4 5 6 7 8 9 10 11 12. That's your hours.

Spreadsheet formula for the win

In Excel or Google Sheets: =(End_Time - Start_Time) * 24 Format the result as Number, not Time. Done. Practically speaking, handles midnight crossover automatically if you include dates. =(B2-A2)*24 where A2 is "1/15/2024 13:00" and B2 is "1/15/2024 19:00" gives 6. Now, if B2 is "1/16/2024 02:00" it gives 13. Magic.

Common Mistakes People Get Wrong

Counting the start hour

"I work 1 to 7, that's 1, 2, 3, 4, 5, 6, 7 — seven hours!In real terms, the hour from 6:00 to 7:00 is hour six. " Nope. The hour from 1:00 to 2:00 is hour one. You're counting the hours displayed on the clock*, not the hours passed*. 7:00 is the end, not a duration.

Want to learn more? We recommend how many days until feb 24 and 1 3 1 4 as a fraction for further reading.

Forgetting the date change

A night shift worker texts me: "My shift is 10pm to 6am, that's 4 hours right? 10, 11, 12, 1,

The midnight trap – why “10 pm to 6 am” isn’t a simple subtraction

When the clock flips over, the arithmetic changes. Here's the thing — if you treat 6 am as “06” on the same day you’ll end up with a negative number (‑4), which obviously can’t be right. The correct approach is to recognize that the shift spans two calendar dates.

Step‑by‑step fix

1. Convert both times to 24‑hour format.

   • 10 pm → 22:00
   • 6 am → 06:00 (next day)

2. If the second value is smaller than the first, add 24 to it before subtracting.

   • 06 + 24 = 30

3. Subtract: 30 − 22 = 8.

So the shift actually covers eight hours, not four. The same rule works for any overnight block: just “wrap around” the smaller number by adding 24 hours until it exceeds the larger one, then subtract.

When “am” and “pm” get swapped

A frequent slip occurs when people read “1 am” as “01:00” but forget that 1 am is earlier than 1 pm. In a schedule that runs from 1 am to 9 am, the elapsed time is 8 hours. Which means if the same person mistakenly swaps the labels and thinks they’re working from 1 pm to 9 pm, they’ll calculate 8 hours again—but the actual shift might be only 8 hours or 20 hours depending on the context. Always double‑check whether the start time precedes or follows the end time on the same day.

The “whole‑hour” fallacy

Some employees mistakenly count whole‑hour increments only, ignoring the minutes that remain. Here's a good example: a shift from 1:15 pm to 6:45 pm looks like “five hours” if you simply look at the hour numbers (1 → 6). In reality, you have 5 hours 30 minutes. When payroll or overtime calculations are involved, those extra minutes can add up to a whole additional hour after rounding rules are applied. Always include the minute component or, better yet, let a spreadsheet handle the fractional result.

Rounding rules that bite back

Many companies round time to the nearest 5 or 15 minutes for payroll simplicity. Over a month, those lost minutes can translate into a noticeable dip in take‑home pay. On the flip side, if you clock out at 5:07 pm and the policy rounds down to the nearest 5‑minute block, you’ll be credited only 5:05 pm, effectively losing two minutes. Knowing the exact rounding policy—and whether it’s “up” or “down”—helps you anticipate how your clock‑in/clock‑out timestamps will be interpreted.

Managing multiple breaks

When a shift includes more than one unpaid break, the cumulative deduction can be surprising. Say you work 9 am to 5 pm (8 hours) but take a 30‑minute lunch and two 15‑minute coffee breaks. Still, the employer may subtract 1 hour total, leaving you with 7 hours of paid time. If you’re not tracking each break separately, you might think you’re being underpaid when, in fact, the deduction matches the policy. A quick spreadsheet that adds up all break lengths and subtracts them from the raw duration eliminates guesswork.

Automating the math

If you find yourself constantly converting, adding, and subtracting, a tiny script can save you hours. Here’s a simple Python snippet that takes a start and end timestamp (in 24‑hour format) and returns the exact elapsed time, automatically handling midnight crossovers:

from datetime import datetime, timedelta

def elapsed_hours(start_str, end_str, fmt="%H:%M"):
    start = datetime.strptime(start_str, fmt)
    end   = datetime.strptime(end_str, fmt)

    # If end is earlier than start, assume it’s the next day
    if end < start:
        end += timedelta(days=1)

    delta = end - start
    return delta.total_seconds() / 3600  # hours as float

Running elapsed_hours("22:00", "06:00") returns 8.Also, 0. You can adapt the format to include dates or seconds if needed, and integrate it into a larger time‑tracking tool.

Quick sanity‑check checklist

• Same‑day? If both times are on the same calendar day, subtraction works directly.
• Crosses midnight? Add 24 hours to the later

timestamp before calculating the difference.
Practically speaking, - **Minute precision? ** Double-check that timestamps include minutes (e.g., 3:07 vs. 3:00).

• **Rounding policy?In real terms, ** Confirm whether your workplace rounds up, down, or to the nearest interval. - Break deductions? Track all unpaid breaks separately to avoid miscalculations.

By combining these strategies, you’ll minimize errors and ensure your timekeeping aligns with both policy and reality. On top of that, whether you’re managing a payroll system, negotiating fair compensation, or simply optimizing your own schedule, precision in time tracking is non-negotiable. After all, in a world where seconds compound into minutes, and minutes into meaningful earnings, the clock is always ticking—and so should your attention to detail*.