1 PM to Military Time

1 PM becomes 1300: add 12 to the hour, write 00 for the minutes

The conversion takes two moves. The hour is 1 and the time falls in the afternoon, so the hour gains 12: 1 + 12 = 13. The time falls exactly on the hour, so the minute digits take 00. Set the two pairs side by side and the answer is 1300.

Whole hours trip people up because the double zero looks like decoration. It is not decoration: four digits are mandatory, the last pair always carries the minutes, and an on-the-hour reading puts 00 there. That pair is also what makes the spoken form work, since 1300 reads as thirteen hundred the way a round number takes the word hundred in speech.

Running it backward is one subtraction: 13 - 12 = 1, attach PM, and 1300 is 1 PM again. The round trip never loses a minute because the two clocks name the same hours with different digits.

The noon boundary: 12 PM stays 1200 and 1 PM turns into 1300

Noon is the hinge of the whole system. The 12 hour keeps its number across the boundary, so 12:00 PM is 1200, and 1 PM is the first afternoon hour that gains 12. Hold onto that one fact and the entire afternoon follows: every hour from 1 through 11 in the PM takes the +12, while noon itself does not.

The same boundary explains why 1 PM and 12 PM sit so close together on paper but an hour apart on the clock. A lunch meeting set for 1230 starts at half past noon; set it for 1300 and it starts at 1 PM sharp. The digits 12 and 13 are neighbors, the times they name are not.

Saying 1300: thirteen hundred, or one three zero zero

Exact hours are spoken with the word hundred. 1300 is thirteen hundred, sometimes thirteen hundred hours on a formal log, and 0100 is zero one hundred. The hundred belongs to whole hours only: the moment minutes appear, the reading switches to the hour plus the minute pair, so 1305 is thirteen oh five and 1330 is thirteen thirty.

Radio procedure reads every digit on its own, trading speed for clarity on a noisy channel. Under that style 1300 becomes one three zero zero and 0100 becomes zero one three zero. Both styles describe the same instant; the digit-by-digit one just survives static better.

Ordering lunch at thirteen hundred would sound strange; ordering it at one PM would not. The 24-hour forms live in writing, in timetables and on radios, where a dropped AM or PM costs more than an extra syllable.

The one o'clock hour, minute by minute

1 PM owns the minute ladder from 1300 to 1359, and every rung converts the same way: the hour is fixed at 13 and the minutes copy across unchanged. The morning versions drop to 01 and gain the leading zero instead.

Only two shapes in that ladder need special handling in speech. A zero minute pair gets the word hundred, as in 1300, and a single zero in the minutes column is voiced oh, as in 1307. Everything else reads the minutes the way you already say them out loud.

Reading 1300 back to 1 PM

The reverse rule needs one test and maybe one subtraction. Look at the first two digits. If they read 13 through 23, subtract 12 and mark the time PM: 13 - 12 = 1, so 1300 reads back as 1:00 PM. If the first two digits are 01 through 11, the time is already in the morning with nothing to subtract. The special pair is 12, which means noon, and 00, which means midnight.

Written with a colon the same time is 13:00, the shape printed by European train timetables, clinic charts and most software. The official US clock at time.gov keeps civil time, and none of these notations changes it: 1300, 13:00 and 1 PM are one instant wearing three outfits.

Most misreadings come from splitting the digits in the wrong place. The hour owns the first pair and the minutes own the second, with no exceptions: read 1300 as 3:00 and the subtraction hit the wrong pair, since 13 minus 12 is 1 and the trailing 00 was never part of the hour.

1 PM on a timesheet

Payroll systems store time as decimals, so 1 PM arrives as 13.0: the thirteenth hour of the day with nothing trailing behind it. Counted in minutes, the same point sits at 13 x 60 = 780 from midnight, which is how time clocks and spreadsheets total a day.

Shift math falls out of the same table. A morning shift that runs 0900 to 1300 covers 780 - 540 = 240 minutes, and 240 / 60 = 4.0 hours. At an hourly rate of $18 that stretch pays 4 x 18 = $72 before taxes and deductions.

The trap is reading 1300 as 13.00 and treating the 00 as a decimal fraction. Here the two agree because the minutes are zero, but the habit breaks on any other time: 1330 is 13.5, not 13.30. Keeping four digits for display and decimals for arithmetic avoids the whole problem.

Where 1 PM conversions go wrong

Four mistakes account for nearly every wrong answer around this hour, and each has a one line fix.

• Writing 100 for 1 PM. On this clock 100 is a padded 1 AM; the afternoon hour gains 12, so the answer is 1300.
• Dropping the trailing zeros. 13 is not a time on this clock. The minutes pair must show, so an exact 1 PM is 1300, four digits.
• Adding 12 to noon. 12:00 PM is 1200, not 2400. Only hours 1 through 11 in the afternoon gain 12.
• Ignoring a zone suffix. 1300Z is a UTC reading, not a local one. Convert the zone first, then the notation.

Where the forms turn up in daily life: airline gate boards and itinerary emails print four digit times, hospital charts and pharmacy pickups print 13:00, and calendar apps show whichever the region setting asks for. The NIST Time and Frequency Division maintains the underlying time standard, and every written form above points at the same second of the day.

One habit prevents most of the mix-ups: pick one notation per document. A schedule that bounces between 1 PM, 13:00 and 1300 on the same page invites guesses, and the guesses fail most often right around the noon boundary, where the numbers sit closest together.

1 PM in one zone is another number in the next

1300 is a clock reading, not a moment in the world. The same instant reads 1300 in New York, 1200 in Chicago, 1100 in Denver and 1000 in Los Angeles, because each zone west of the last sits one hour earlier. Changing the notation does not move the meeting; changing the zone does.

Read the table backward and the rule appears: the four digit form tracks local time, so a 1300Z stamp in UTC becomes 8:00 AM in New York under standard time and 9:00 AM under daylight time. That is why a flight listed as 1300Z keeps its number when clocks change, while the local departure time printed beside it moves by an hour.

In practice: when someone in another zone sends a meeting at 1300 their time, convert the zone first, then write the result in whatever notation your calendar uses. A 1300 Eastern meeting lands at 1000 Pacific, which is 10 AM on a Pacific clock, not 1 PM.