1700 Military Time

1700 is 5:00 PM with an empty minute pair

1700 is 5:00 PM. The first two digits hold the hour, 17, and the last two hold the minutes, 00. Because 17 sits past noon, take 12 off it: 17 minus 12 leaves 5, and the minute pair stays as it is. Written with a colon the same moment is 17:00, and on a kitchen clock it is five in the evening.

No AM or PM tag appears anywhere in the code, and none is needed. The hour number does that job by itself. A 24 hour clock counts straight through the afternoon, so 17 can only be the seventeenth hour of the day measured from midnight. A reader who sees 1700 never has to work out whether the sun is up.

The trailing zeros matter more than they look. Drop them and 1700 turns into 17, a number someone could take for seventeen minutes, seventeen dollars, or a line on an order form. Keep both pairs and the code stays a clock reading. Put a decimal point in it and 17.00 becomes a different thing again: a count of hours since midnight, built for a payroll column. Same digits, different job.

Run those counts and they agree with each other, which is the fastest way to catch a typo. If the minutes after midnight do not match the hour you converted, one of the two numbers is wrong.

Saying seventeen hundred, and when the word hours appears

Out loud, 1700 is "seventeen hundred". The word hundred stands in for the empty minute pair, and it is the reason the code sounds like a quantity rather than a time. On formal radio traffic people add one more word and say "seventeen hundred hours". In a hallway, nobody bothers.

Two habits separate someone who reads the clock from someone who guesses. The first is that the leading pair is never read as a thousand. 1700 is seventeen hundred, not one thousand seven hundred, even though the digits would say exactly that in a bank balance. The second is that minutes, when they exist, replace the word hundred instead of following it. 1705 is "seventeen oh five" and 1745 is "seventeen forty five", with no hundred in either.

When a radio channel is noisy, crews fall back to single digits: "one seven zero zero". That form survives static better than any word, and it is common in aviation and on the water. For a text message or a calendar invite to a friend, plain "5 PM" is the right choice. The code is a tool for logs and schedules, not a personality.

Three counts that pin 1700 to the day

Multiply 17 by 60 and you get 1020. That is how many minutes have passed since midnight when the clock reads 1700. Subtract 1020 from 1440, the number of minutes in a full day, and 420 remain. Seven hours sit between 5 PM and the next midnight, which is why a shift that ends at 1700 and a bedtime near midnight feel close together.

Divide 1020 by 60 and the answer is 17.00. The division comes out exact because the minute pair is zero, so the decimal column shows two zeros and no fraction. That is a small convenience on a timecard: a punch on the hour never needs a rounding decision. Fifteen minutes late would change the decimal to 17.25, while five minutes late would give 17.0833, which is where the arithmetic gets awkward and most payroll systems switch to counting minutes instead.

The UTC value depends on the season, not on the code. In January, Eastern Standard Time runs five hours behind UTC, so 1700 EST is 2200Z. In July, Eastern Daylight Time runs four hours behind, so the same wall clock reading is 2100Z. The local digits stay put all year. Only the offset moves. The official US clock, time.gov, shows every zone offset side by side, which makes the comparison easy to see in real time.

1700Z in January and again in July

The Z at the end of 1700Z means the reading is already on UTC, the clock that ignores the seasons. To turn it into a local time, subtract the zone offset. In winter that means subtracting 5 for the East Coast, 6 for Chicago, 7 for Denver, 8 for Los Angeles, 9 for Alaska and 10 for Hawaii. In summer, every zone that observes daylight saving moves one hour closer to UTC, so each subtraction drops by one.

Those changes follow the federal rules that NIST publishes on its daylight saving time page. In 2026 daylight saving runs from 2 a.m. on March 8 to 2 a.m. on November 1. Arizona (apart from the Navajo Nation) and Hawaii stay on standard time all year, so a Phoenix reader sees 10:00 in both columns and a Honolulu reader sees 7:00 in both.

A 1700Z meeting is therefore a moving target for anyone outside UTC. A team that books 1700Z every Thursday for a year will meet at noon in New York in winter and at one in the afternoon in summer, and the people who forget the shift will arrive an hour late twice a year.

The end of the day shift and the 5 PM rush

On a standard day shift, 1700 is the moment the building empties. A shift that starts at 0800 and ends at 1700 covers nine hours on the clock, and after an unpaid lunch it usually pays eight. The punch itself takes seconds, but the line at the time clock does not, and a crew of thirty can spend ten minutes waiting to badge out.

That queue is one reason employers round punches. The rule that governs the practice, 29 CFR 785.48 from the U.S. Department of Labor, accepts rounding to the nearest five minutes, the nearest tenth of an hour, or the nearest quarter hour, as long as it does not systematically short the worker over time. A policy that pulls a 1703 punch back to 1700 and pushes a 1658 punch forward to 1700 is fine on paper. A policy that rounds every punch in the employer's favor is not.

If you are the one punching, the advice is dull and effective: badge out at the clock, not on the way to the parking lot. Minutes spent walking to the car are not minutes on the record unless the employer's system captures them.

The same 5 PM on a receipt, a roster, and a timecard

A point of sale receipt almost always prints the colon form, 17:00, because the receipt is read by a customer who may not know the four digit convention. A shift roster prints 1700, because four digits line up in a column and leave no room for an AM or PM tag to be misread. A payroll export prints 17.00, because the software needs a number it can multiply by a rate.

None of those three is more correct than the others. They are one instant written for three different readers. The mistake to avoid is mixing them inside one column, such as a roster that says 1700 in one row and 5:00 in the next. Sorting that column will put the 5:00 entries in the wrong place for the rest of the year.

The pay column uses 19.75 an hour, a rate that keeps the arithmetic easy to check by hand. Eight hours at that rate is 158 dollars, which is what a 0900 to 1700 day pays before tax. A six hour evening block from 1700 to 2300 pays 118.50. When the block runs past midnight the hours still add up the same way, as the last row shows.

From 1700 to 0100, and other blocks that cross midnight

An end time smaller than the start time has rolled into a new day. The fix is to add 1440 to the end before subtracting. From 1700 to 0100: 60 plus 1440 is 1500, 1500 minus 1020 is 480, and 480 minutes is eight hours. From 1700 to 0030 the same steps give 1470 minus 1020, or 450 minutes, which is seven and a half hours and 7.50 in the decimal column.

Two shortcuts are worth knowing. A block that ends at 2400 or 0000 can be measured by subtracting the start from 1440, because midnight closes the day being counted. A block that runs to the same clock time on the following day is 24 hours, which is rare on a timecard but common in security work and in hospital scheduling.

If the shift crosses a daylight saving change, the arithmetic needs one more adjustment. Spring forward removes an hour at 2 a.m., so a night shift that spans the change and reads eight hours on the wall clock is seven hours of paid time. Fall back adds an hour, so the same span pays nine. Payroll systems handle this with timestamps rather than typed digits, which is one reason they prefer 1700 EST to a bare 1700.

Four mistakes to catch before you send 1700

The first is a missing pair. A roster that says 17 instead of 1700 will be read by half the crew as five in the afternoon and by the other half as an error. Write all four digits every time, zeros included.

The second is the wrong field. Typing 17.00 into a box that expects a clock reading earns a validation error at best. Typing 1700 into a decimal hours box pays seventeen hours at worst. Read the label above the box before you type.

The third is a lost PM. Convert 1700 to 5:00 and the number is right but the meaning is gone, since 5:00 with no tag could be dawn. Carry the PM across whenever you switch formats.

The fourth is treating 1700Z as local. The Z is not decoration. If a dispatcher says 1700Z and you live in Denver, your clock should read 10:00 in winter and 11:00 in summer. Converting the code is easy. Remembering which clock you started from is the part that goes wrong.