11 PM to Military Time

11 PM is 2300: the last full hour of the day

The conversion needs one move. The hour is 11 and the time falls in the evening, so the hour gains 12: 11 + 12 = 23. On the hour the minute digits are 00, so the four digit answer is 2300, the reading a 24-hour clock shows as 23:00. It is the highest hour reading the day can carry before midnight.

The zeros carry the minute field, not the hour. A 24-hour reading always holds four digits, an hour pair then a minute pair. Within the eleven o'clock hour every reading starts with 23: 2300 on the hour, 2330 at half past, 2359 one minute before the day closes. Drop the leading pair and a reading like 300 is not a short form, it pads to 0300, which is 3 in the morning.

Why 12 and not some other number? The 24-hour clock counts straight from 0 at midnight to 23 at 11 PM, so every evening hour equals its 12-hour number plus 12. The 11 at night is the 23rd hour of the day, sitting 12 hours after the morning 11.

The whole eleven o'clock hour in four digits

Only the minutes change inside the hour, and they copy over untouched. The table walks the hour from its first reading to its last.

The last row is the boundary this hour lives against. 11:59 PM converts to 2359, and 60 minutes later the reading drops from the top of the scale to the bottom: 0000 on the next date. Nothing else in the system behaves that way, which is why scheduling software keeps the date attached to every 24-hour timestamp.

Read the hour against its morning twin. 11 AM is 1100 and 11 PM is 2300, and the two readings sit 12 hours apart, which is 720 minutes. In the 12-hour system the AM and PM tags do the separating; in the 24-hour system the number does it on its own.

2300 on a timesheet

Decimal hours divide the minutes by 60 and add them to the hour. At 2300 the minutes are 00, so the decimal value is 23.00 with nothing left over, and the minutes elapsed since midnight run 23 x 60 = 1,380. One hour remains before the day ends: 60 minutes, or 1.00 decimal hour.

Overnight pay math follows the wrap. A shift from 2300 to 0700 runs 8 hours 00 minutes, or 8.00 decimal hours, because the end time belongs to the next date. At $19.25 an hour that shift earns 8 x 19.25 = $154.00. A 2300 to 0715 shift with a 30 minute unpaid break logs 7.75 paid hours, which is $149.19 at the same rate once the quarter hours are priced.

Two readings name the same midnight. The Times of Day FAQs from NIST draw the line this way: 0000 refers to midnight at the start of a date and 2400 to the end of one. A timesheet that logs a 2300 start and a 2400 end on the same date records 1.00 hour, while 2300 to 0000 next date records the same hour across the boundary.

Saying and writing 2300

Whole hours take the word hundred: 2300 is twenty-three hundred, or twenty-three hundred hours on a formal log. Radio procedure reads every digit on its own, so the same time becomes two three zero zero, a style that survives noise better than the compressed form. The moment minutes appear the speech changes shape: 2305 is twenty-three oh five and 2345 is twenty-three forty-five.

In writing, the four digit form without a colon is the military and log convention, while 23:00 with a colon is the international form carried by ISO 8601 and most of the world's digital clocks. Both mean eleven at night. A 12-hour rendering, 11:00 p.m., describes the same instant with the period carried by the tag instead of the number.

2300 in Zulu time

Convert 2300 to UTC by adding the zone's offset, and this is the one evening hour where the date almost always rolls over. Eastern Standard Time runs 5 hours behind UTC, so 2300 EST is 23 + 5 = 28, and 28 - 24 = 4, giving 0400Z on the next date.

Daylight time shortens every offset by one: 2300 EDT is 0300Z, 2300 PDT is 0600Z, and so on. The local reading stays 2300 either way. What moves is the UTC value, which is why flight plans, medical logs and server timestamps record Zulu rather than local time when the entry could be read from another zone.

Reading Zulu back follows the mirror rule. 0400Z in Eastern Standard Time is 23:00 the previous evening, because you subtract the 5 hour offset instead of adding it and the date steps back one.

11 PM against the hours around it

The mix-ups at this hour have a pattern. One comes from reading 1100 as the evening hour, and the other from guessing whether midnight is 2400 or 0000. The table places 2300 next to the readings it gets confused with.

Notice that neither noon nor midnight follows the add-12 rule. Noon keeps 1200 because the 24-hour count has reached only 12 hours, and midnight opens the day at 0000. The rule applies only to the PM hours from 1 through 11, which is exactly the band 2300 sits at the top of.

For schedules, the practical value of 2300 is that it removes the tag problem entirely. A posted 11:00 PM can be misread as morning on a faded sign or a misheard call; 2300 cannot, because no morning hour carries that reading.

Where a 2300 start shows up

2300 marks the late part of the day, and the places that use it cluster around the same pattern. Third shift and graveyard shifts commonly run 2300 to 0700, an 8.00 hour block that ends when the morning shift arrives. Bars and venues in cities with late licenses close at 2300 or later. Hospital night intakes, hotel night audits and overnight stock crews all anchor their logs on the 2300 hour.

Media and transport use it differently. Some rail and ferry timetables print 23:00 departures to avoid the AM and PM ambiguity entirely. Broadcast logs schedule programming in 24-hour form so a 2300 slot can never be confused with the 1100 rerun. In each case the reader is someone who needs the hour without a second look.

The 24-hour clock guide at timeanddate.com collects the countries and industries that run on this form full time. The United States keeps it to these niche uses, which is why the conversion question comes up at all for an American reader.

One habit is worth building if you read logs often: when you see a 24-hour reading above 1200, subtract 12 from the hour pair and attach PM. 2300 becomes 11:00 PM in one step. Any reading at or below 1200 either keeps its number as an AM hour or, at 1200, is noon. That single rule covers the whole dial.

Converting 2300 back to 11 PM

The reverse move subtracts 12 from any hour pair above 12. Subtract 12 from 23 and the hour reads 11 again, the minutes copy over untouched, and the PM tag comes back, giving 11:00 PM. The calculator above runs the reverse conversion too: type any four digit reading and it returns the 12-hour form.

A hand check with three readings covers the edge cases. 1100 is at or below 1200, so it keeps its number and reads 11:00 AM. 1200 is noon, so it keeps 12 and reads 12:00 PM. 0000 sits at the bottom of the scale, and converting it wraps to 12:00 AM, the start of the date the log is written on.

The date boundary deserves a second look on real logs. An entry stamped 2300 on the 3rd describes the same instant as 11:00 PM on the 3rd, but an entry stamped 0400Z describes 2300 EST on the 3rd from a UTC calendar that has already moved to the 4th. When you convert a Zulu reading back to local time, step the date back one whenever the subtraction crosses midnight, or the log will appear to describe an hour that has not happened yet.

None of these conversions involve time zones in the local sense: 2300 means the same wall clock hour everywhere, and only the UTC math brings offsets in. Keep the two operations separate and the errors stay out.