1730 Military Time

1730 is 5:30 PM, half past five

1730 is 5:30 PM. Split the code into 17 and 30. The hour pair sits past noon, so subtract 12 and 17 becomes 5. The minute pair is 30 and it does not change, because minutes mean the same thing on both clocks. Put the pieces back and the reading is half past five in the evening, or 17:30 with a colon.

The half hour is the part doing the work. At 1700 the minute pair is empty and the code only says which hour it is. At 1730 the pair carries real information, and that is why a decimal hours column needs care: 30 minutes is half of an hour, so the decimal is .50 and not .30. The difference is twelve minutes of pay on every shift, and it gets its own section below.

In minutes, 1730 falls 1050 after midnight. A full day holds 1440 minutes, so 390 remain, which is six and a half hours. Both counts come straight from 17 x 60 + 30.

Seventeen thirty, and where the word hundred goes

Say 1730 as "seventeen thirty". The word hundred belongs to the top of the hour only, so it disappears the moment a minute pair shows up. A listener who hears "seventeen hundred thirty" will still follow you, but the phrasing marks you as a visitor rather than a regular.

Minutes below ten take an "oh" to keep the pairs even: 1705 is "seventeen oh five". Minutes from ten to fifty nine are read as a two digit number: 1735 is "seventeen thirty five". On a channel with background noise the fallback is one digit at a time, "one seven three zero", which cannot be mistaken for thirteen or thirty.

In ordinary speech 1730 is "five thirty", and context supplies the PM. That works in a text to a friend and fails in a log that spans a full day, which is the reason the four digit form exists at all.

17.50 is the decimal, and 17.30 is the trap

A timecard does not store a clock reading. It stores hours, and hours come from minutes divided by 60. The hour holds 60 minutes by definition, and NIST's conversion tables list the minute as 60 seconds, which is where that divisor comes from. Thirty divided by 60 is 0.5, so 1730 becomes 17.50. The digits 30 in the code are not the digits 30 in the decimal, and treating the two as the same thing is the most common error in this hour.

Write 17.30 by mistake and the payroll math reads seventeen hours and eighteen minutes, because 0.30 x 60 is 18. The record is then twelve minutes short of the truth. On a 6.5 hour shift at 22.40 an hour, the correct figure is 145.60 and the mistaken one pays 141.12, a gap of 4.48 for a single evening.

The error compounds without looking like one. A closer who works three of these shifts a week loses just over thirteen dollars, and the line still looks like a typo rather than a policy, so nobody reports it. Check the decimal column against the minute column before a week gets approved.

Read the table one row at a time and the pattern holds: every correct form points to 1050 minutes, and only the 17.30 row lands somewhere else.

A half hour schedule that closes at 1730

Half hour start times are the default in retail, food service and clinics because they line up with a 30 minute lunch and with a register that opens on the half hour. A store that closes at 1730 usually schedules the closing crew from 1200 or 1300 rather than 1215, because a quarter hour start forces a quarter hour break somewhere later in the shift.

The block lengths are easy to check in your head. From 1200 to 1730 is five and a half hours. From 1300 to 1730 is four and a half. From 1500 to 1730 is two and a half. Each one lands on a .50 decimal, which is why a half hour schedule and a decimal timecard fit together with no rounding at all.

At 22.40 an hour the 1100 to 1730 block pays 145.60, which matches the decimal example in the section above. If your own rate is different, the widget on this page will run the multiplication with your number.

The half hour before the overtime line

Federal law sets the overtime threshold at 40 hours in a workweek, and the Department of Labor's fact sheet on hours worked spells out that hours past that line are paid at one and a half times the regular rate. A shift that ends at 1730 sits right against that line for anyone who has already logged 33.5 hours by the start of the day.

Suppose a worker reaches Thursday morning with 33.5 hours on the books and clocks in at 0900. The 40th hour arrives six and a half hours later, at 1730. Every minute after that is overtime. At 22.40 an hour the regular rate is 22.40 and the overtime rate is 33.60, so the split happens at the same clock reading the schedule already uses as a closing time.

That coincidence matters when you build a schedule. A 1730 close on the fifth day of a 34 hour week creates no overtime at all. The same close on the sixth day of a 40 hour week creates a half hour of premium pay, and a supervisor who did not plan for it sees the number on Friday's report. Some states add their own daily overtime rules, so check the state labor office if you work somewhere with a separate statute.

One 1730Z call, four local clocks

A meeting notice that says 1730Z is not a local time, and that is the point of the Z. Subtract the offset to get the local clock. In January, New York is five hours behind UTC and reads 12:30 PM. Chicago is six behind and reads 11:30 AM. Denver is seven behind and reads 10:30 AM. Los Angeles is eight behind and reads 9:30 AM.

July moves all four cities, because each one observes daylight saving and subtracts one hour less than in winter. Phoenix is the exception nearby, since Arizona keeps standard time all year and stays at 10:30 AM in both rows.

NIST lists the 2026 changeover as March 8 at 2 a.m. local time and November 1 at 2 a.m. local time. A recurring 1730Z call crosses both dates, so the invite should carry the UTC reading and let each calendar convert it, rather than a typed local time that is wrong for half the year.

Adding and subtracting around 1730

Durations are where the half hour earns its keep. From 0900 to 1730 is 510 minutes, or 8.5 hours, which is a full day with a half hour lunch already taken out. From 1200 to 1730 is 330 minutes, or 5.5 hours. From 1730 to 0000 is 390 minutes, the same count as the minutes left in the day.

When a block crosses midnight, add 1440 to the end before subtracting. From 1730 to 0130: 90 plus 1440 is 1530, 1530 minus 1050 is 480, and that is eight hours. From 1730 to 0030 the same steps give 1470 minus 1050, or 420 minutes, which is seven hours and 7.00 decimal.

Adding time runs the same steps in reverse. Two hours after 1730 is 1930. Ninety minutes after 1730 is 1900, because 30 plus 90 crosses the hour boundary by 60. The rule to keep in mind is that minutes roll over at 60 and hours roll over at 24, and never the other way around.

What to check before you book or punch 1730

Start with the minute pair. If the code ends in 30, the decimal should end in .50. A timecard that shows 17.30 next to 1730 holds two different numbers in one row, and the pair should be fixed before payroll runs.

Next, confirm the zone. 1730 on its own is a wall clock reading with no location attached. A remote team spread over four zones needs the Z form or an explicit offset, and a calendar invite should display the time in the viewer's own zone rather than the sender's.

Then check the day boundary. An end time of 0000 is midnight at the end of the shift, not the start of it, and a system that reads it as zero will produce a negative duration. Most systems handle this correctly. The ones that do not are worth catching in the first pay period rather than the fourth.

Last, check the rounding policy in writing. Rounding to the nearest quarter hour is allowed under 29 CFR 785.48 when it averages out over time. If the rounding only ever moves one direction, that is the pattern to raise with a manager or a state labor office.