🆕 Newly Added Calculators:

✅ Hours Calculator

Muhammad Yasir Yasin
By Muhammad Yasir Yasin · Updated 12 Nov 2026 Founder · 20 Year+ Telecom + IT Expert
Muhammad Yasir Yasin

Muhammad Yasir Yasin

Founder, metacalculator.org

Muhammad Yasir Yasin is a Telecom + IT expert from Pakistan with 20+ years of proven experience — the career documented on his LinkedIn. He has been in pure IT since 1998, and works as a crypto consultant & trader since 2016. He is the founder of metacalculator.org, seotools.metacalculator.org (SEO Tools) and metatrendonline.com (Digital Products Market Place): free tools built to give clear, checked answers, with no sign-ups and no paywalls.

Every calculator here is built from the published formula, tested by hand, and explained in plain words.

Hours Calculator

Result

Timesheets are just seven small subtractions plus one addition — but across a week of split shifts the arithmetic gets tedious. Enter each day's start and end time; empty days are skipped automatically.

The total is shown in decimal hours (e.g. 37.5), the format payroll systems expect. Overnight shifts crossing midnight are handled too.

A week of start and finish times, totalled

The Hours Calculator turns a week of clock-in and clock-out times into the number payroll actually wants: a total in decimal hours. There is a start and an end field for every day, Monday to Sunday. Fill in the days you worked, press Calculate, and you get a row per day — Monday 8.5 h, Tuesday 8.5 h — and the week's total as the headline: 42.5 hours for a Monday-to-Friday week of 09:00 to 17:30. Days you leave blank are simply not part of the week; there is nothing to delete and no zero to type.

How each day is counted

A day's hours are the minutes from its start time to its end time, divided by 60. If the end time is earlier than the start — the signature of a night shift — the end is read as falling on the next day, so 22:00 to 06:00 counts as 8 hours, exactly as worked. A day only counts when both its fields are filled: a start with no end (or the reverse) is skipped without a message, so after calculating, glance at which day rows appeared — the rows listed are the days that were counted, and a missing row means a missing field, not a missing day of work. The total is built from the exact minutes of every counted day and rounded once, to two decimals, at the very end.

Worked example — the standard week

Monday to Friday, 09:00 in, 17:30 out, weekend left blank:

DayTimesHours
Monday09:00 – 17:308.5 h
Tuesday09:00 – 17:308.5 h
Wednesday09:00 – 17:308.5 h
Thursday09:00 – 17:308.5 h
Friday09:00 – 17:308.5 h
Total for the week42.5 hours

Other patterns fall out the same way. A four-day week of 10-hour shifts (say 07:00–17:00, Monday to Thursday) totals exactly 40 hours. A part-time pattern of 09:00–13:00 on Monday, Wednesday and Friday totals 12 hours. Weekend-only work — Saturday 10:00–16:00 and Sunday 10:00–14:00 — totals 10 hours, with the five blank weekdays correctly contributing nothing. And a single night shift, Monday 22:00 to 06:00, counts 8 hours on Monday's row: the day a shift starts is the day it is counted on, which matches how rosters are written.

Breaks — the honest method

Be clear about what this calculator does with breaks: nothing — because it cannot see them. Each day has exactly one start and one end, so a break inside the day is inside the span it measures. If your break is unpaid and must come out, take it out of the end time: a 09:00–18:00 day with a one-hour unpaid lunch is 8 hours worked, and entering 09:00–17:00 produces exactly that — the end pulled earlier by the length of the break. A 30-minute break inside 09:00–17:30 (an 8.5-hour span) means entering 09:00–17:00 for a clean 8 h. What you should not do is enter the raw span and plan to "remember to knock an hour off the total" — the total is the figure that travels onward to pay calculations, and the remembering step is where hours quietly vanish. Paid breaks, of course, stay in: enter the true start and end and let the span stand.

Why the total can differ by a cent from the rows

Each day row is rounded to two decimals for display; the total is not the sum of those rounded rows but the rounded sum of the exact minutes. Two short days of 20 minutes each (09:00–09:20) display as 0.33 h apiece — yet the week totals 0.67 hours, not 0.66, because 40 minutes is 0.6667 of an hour. The total is the correct figure; the rows are rounded views of it. On ordinary full days the two agree to the cent, and the difference only ever reaches a hundredth of an hour — 36 seconds — but payroll people reconcile to the cent, and this is the page that explains why their reconciliation is right.

Decimal hours, and what happens next

The total arrives already in the form payroll systems store: decimal hours, where 42.5 means 42 hours 30 minutes. Keep the two apart in your head — 42.5 is not 42:50, and 8.5 h is 8 h 30 min, not 8 h 50. If your week is kept as daily hours rather than start/end times (a card that says "Mon 8, Tue 8.5…"), the Time Card Calculator is the matching tool: it totals the week and splits out overtime over 40 hours, which this page deliberately does not — the Hours Calculator reports the whole week at one rate and leaves thresholds, overtime and pay to the tools and contracts that own them. To price the week, multiply the decimal total by the hourly rate; to convert a single day's clock span into decimals by hand, the Time to Decimal Calculator shows the working.

Common mistakes

  • Leaving a day half-filled and trusting the total. One field of a day filled means that day is skipped silently. If a row is missing from the result, a field is missing on the form.
  • Entering the raw span and forgetting the break. An unpaid lunch inside the span stays in the total unless you pull the end time earlier by the break's length (see the breaks section).
  • Reading 8.5 h as 8 hours 50 minutes. It is 8 hours 30. Decimal hours are fractions of an hour, not minutes wearing a dot.
  • Counting a night shift on the wrong day. A shift starting Monday 22:00 is counted on Monday, all 8 hours of it, including the part after midnight. Do not split it across Monday and Tuesday rows.
  • Rounding each day before totalling. Employers who round per day (some round to the nearest quarter hour per shift) will land a few minutes away from this page's exact-minutes total. Know which convention your payslip uses before disputing either figure.

Split shifts, second jobs and the overtime preview

Real weeks are messier than one block a day, and the calculator absorbs the mess in three standard ways. A split shift — 06:00–10:00 and 16:00–20:00, say — has no single start and end, but its span total is what this page adds up, so entering one block with the same length (06:00–14:00) gives the identical 8.0 hours for that day; only the total is carried forward, so the placeholder block costs nothing. Two jobs are the same trick at week level: add both jobs' hours into the days and the total is your true worked week — with one caution, that an overtime threshold normally applies per employer, so a combined 45-hour week across two workplaces is a fact about your time, not about either payslip. Finally, the overtime preview: this page deliberately stops at the total, but reading it against 40 takes one subtraction — a 47.5-hour total is 40 regular + 7.5 over, in the weekly-rule sense — and the Time Card Calculator exists to make exactly that split its headline. One more freedom the labels hide: the rows say Monday to Friday, but the arithmetic does not know the calendar. A Sunday-to-Thursday workweek, or any five days in a row, enters exactly the same way; the labels are the common case, not a constraint.

Auditing a payslip week — a full worked example

Here is the page doing the job it is most often opened for: checking a week that does not match the payslip. The week as worked: Monday 09:00–17:30, Tuesday 09:00–17:30, Wednesday 09:00–13:00 (a half day), Thursday 09:00–17:30, and Friday an overnight 22:00–06:00. Entered exactly so, the rows read 8.5, 8.5, 4, 8.5 and 8 hours — Wednesday's short day in plain sight, Friday's overnight span correctly crossing midnight — and the hero total is 37.5 hours, decimal 37.5, total minutes 2,250. If the payslip says 36.5, the missing hour is findable: it is almost never the addition, it is a day entered differently — Friday recorded as a same-day 22:00–23:00 by a system that could not hold the overnight span, or Wednesday's unpaid lunch deducted a second time. The audit method is the point: compare row by row, not total by total, because the rows are where the disagreement lives, and this page shows its rows precisely so that comparison takes a minute.

Key terms

  • Decimal hours — hours written as a decimal (8.5), the format payroll systems store; the week's total is given this way.
  • Span — the time from a day's start to its end; breaks inside it are included unless removed by the end-time method above.
  • Overnight shift — a shift whose end falls after midnight; counted in full on the day it starts.
  • Quarter-hour rounding — a common payroll convention (rounding each shift to the nearest 0.25 h); not applied here — this page totals exact minutes.

Related tools

The Time Card Calculator totals a week entered as daily hours and splits overtime over 40; the Time Duration Calculator measures a single start-to-end span; the Time to Decimal Calculator converts hours-and-minutes into decimal hours.

A closing word on keeping the record

The audit above only works if your side of the paper exists. The habit that makes it effortless: fill the week in as you go — thirty seconds each evening, while the day's start and finish are still facts rather than reconstructions — and keep the five row figures somewhere of your own, because the row figures are the audit trail. A total remembered on Friday is an opinion; five start–end pairs written down daily are evidence, and in every payslip dispute the side holding the daily record is the side that gets believed.

Frequently asked questions

What does the Hours Calculator compute?

It takes the start and end times for each day from Monday through Sunday and totals your weekly work hours. You get a row per day plus the week's total in decimal hours — 37.5, say, or 42.5 — the format payroll systems expect.

Can you give a worked example?

Yes — enter 09:00 to 17:30 for Monday through Friday and leave the weekend blank. Each weekday row shows 8.5 h and the weekly total comes to 42.5 hours. A single overnight shift works too: Monday 22:00 to 06:00 counts as 8 hours on Monday's row.

How does it handle a shift that crosses midnight?

The end time is read as falling on the next day, so the shift is counted in full and credited to the day it started. A 22:00 start with a 06:00 finish is 8 hours — no negative numbers, no splitting the shift across two days.

Does it deduct lunch or other breaks?

No. Each day has one start and one end, so a break inside the day is inside the measured span. If your lunch is unpaid, pull the day's end time earlier by the break's length: 09:00 to 18:00 with a one-hour lunch is entered as 09:00 to 17:00, giving exactly the 8 hours you worked.

What happens if I fill in only some days, or only one field of a day?

Blank days are ignored, which is how part-time and weekend-only weeks are meant to be entered. But a day needs both its start and its end: a day with only one field filled is skipped without a warning, so check the result rows — the days listed are the days that were counted.

Why can the total differ by 0.01 from adding up the day rows?

Because the rows are rounded for display while the total is rounded once from the exact minutes. Two 20-minute days show as 0.33 h each, yet the total is 0.67 hours — 40 minutes is 0.6667 of an hour. The total is the exact figure; the rows are rounded views of it.

What should I know about accuracy?

The arithmetic is exact to the minute: no rounding is applied per day before totalling, and the total is shown to two decimals. Any difference from a payslip almost always comes from a rounding convention — many employers round each shift to the nearest quarter hour — or from an unpaid break that was inside a span you entered.