Military Time and the 24-Hour Clock

What the 24-hour clock is

The 24-hour clock counts the full day in a single continuous sequence of hours, from 0 through 23. Midnight is the start of the day at hour 0, noon falls at hour 12, and the evening hours continue upward, so 6 in the evening becomes 18. Because every hour of the day has a unique number, there is never any doubt about whether a given time falls in the morning or the evening.

In written form, times are usually shown as four digits, such as 0830 or 1745, sometimes with a colon as 08:30 or 17:45. The first two digits are the hour and the last two are the minutes. Military usage often drops the colon and pronounces the digits in a distinctive way, for example saying 'zero eight thirty' or 'seventeen forty-five.'

It is worth stressing that 'military time' and 'the 24-hour clock' refer to the same underlying system. The only real differences are conventions of writing and speaking. Much of the world already uses the 24-hour clock for ordinary civil purposes, so for many people there is nothing exotic about it at all.

How to convert between 12-hour and 24-hour time

Converting from 12-hour to 24-hour time follows two short rules. For any AM time, keep the hour as is, except that 12 AM becomes 00. For any PM time, add 12 to the hour, except that 12 PM stays as 12. So 7:15 AM becomes 0715, 12:30 AM becomes 0030, 3:45 PM becomes 1545, and 12:30 PM stays 1230.

Converting back from 24-hour to 12-hour time reverses the process. If the hour is 00, it becomes 12 AM. If the hour is between 1 and 11, it stays the same and takes AM. If the hour is exactly 12, it takes PM. If the hour is between 13 and 23, subtract 12 and add PM, so 2000 becomes 8:00 PM.

The minutes never change in either direction, which keeps the arithmetic simple. The only part that ever needs adjustment is the hour, and the only tricky values are those around midnight and noon. Practicing a handful of examples in both directions is usually enough to make the conversion automatic.

Why the military, aviation, and medicine use it

The central reason these fields adopt the 24-hour clock is safety. The labels AM and PM are easy to misread, mishear, or omit, and a single dropped suffix can turn a morning dose or a morning departure into an evening one. Numbering the hours uniquely removes that failure mode entirely, because 0800 and 2000 can never be confused.

In aviation and the military, communications often happen over noisy radio channels where clarity is critical. A four-digit time spoken clearly leaves no room for the ambiguity that 'eight o'clock' would carry. Coordinating operations across time zones is also cleaner, which is why these fields frequently pair the 24-hour clock with a universal reference time.

In medicine, charts record doses, observations, and events around the clock, including overnight. A 24-hour notation makes the sequence of events unambiguous on the page, which reduces the risk of administering a medication twice or missing it entirely. The shared goal across all these fields is to make the time impossible to misinterpret.

Midnight and noon edge cases

Midnight and noon are where most confusion lives, even for experienced users. Noon is the simplest: it is 1200, exactly halfway through the day. There is no ambiguity, because 12 PM and 1200 line up directly.

Midnight is trickier because it sits at the boundary between two days. The start of a day is written 0000, pronounced 'zero hundred' or 'zero hundred hours.' Some conventions also allow 2400 to mean the very end of a day, so 2400 on one date is the same instant as 0000 on the next. To avoid confusion, many systems and standards prefer 0000 and discourage 2400 entirely.

A frequent misconception is that 12 AM is noon and 12 PM is midnight, when in fact it is the reverse: 12 AM is midnight and 12 PM is noon. This is one of the strongest arguments for the 24-hour clock, since 0000 and 1200 carry no such trap. When in doubt, writing the time in 24-hour form removes the guesswork.

How it relates to ISO 8601

ISO 8601, the international standard for representing dates and times, is built entirely on the 24-hour clock. A timestamp such as 2026-06-20T18:45:00 uses hour 18 rather than 6 PM, precisely because the standard avoids AM and PM. This makes machine-readable times unambiguous and easy to sort, since later times always have larger numbers.

The standard also has clear rules for the day boundary, treating 00:00 as the start of a day. It can attach a time zone offset, such as a trailing Z for UTC or a value like +02:00, so the same notation works for local and universal time. Anyone comfortable with military time already understands the core of how ISO 8601 expresses the time of day.

Because so many programming languages, databases, and data formats default to ISO 8601, familiarity with the 24-hour clock pays off well beyond the military context. Reading a log file, an API response, or a calendar export becomes far easier when 18:45 is instantly recognizable as a quarter to seven in the evening.

A quick reference and common mistakes

As a quick reference, the morning hours map directly: 1 AM is 0100, 6 AM is 0600, and 11 AM is 1100. After noon, add twelve: 1 PM is 1300, 6 PM is 1800, and 11 PM is 2300. The two anchors to memorize are 0000 for midnight and 1200 for noon, and the rest follows automatically.

The most common mistake is mishandling the noon and midnight hours, for instance writing 1 PM as 1200 instead of 1300, or treating midnight as 1200. Another frequent error is adding 12 to morning times, which produces nonsense like 1900 for 7 AM. Remember that AM hours generally stay as they are, and only PM hours from 1 through 11 get the extra twelve.

A final pitfall is reading a four-digit time as a single number, such as hearing 'fourteen hundred' and writing 14:100. Each time has exactly two digits for the hour and two for the minutes, with minutes never exceeding 59. Keeping that structure in mind makes both writing and converting 24-hour times reliable.