10:30 PM to Military Time

10:30 PM becomes 2230 in two steps

Convert 10:30 PM with two moves and nothing else. Move one: the hour. The time sits in the evening half of the day, so the hour gains 12 and 10 becomes 22. Move two: the minutes. The 30 copies across with no arithmetic at all. Set the two pieces side by side as four digits and the result is 2230.

Going the other way is one subtraction: 22 minus 12 is 10, the number is above 12 so it is PM, and 2230 reads back as 10:30 PM. The round trip always works because the two clocks are one clock with the afternoon hours relabelled. The hour carries all of the arithmetic and the minutes carry none of it, which is why a 30 in the middle of the number never means half past anything else.

The step method for any evening time

The same two steps convert every evening hour, so it pays to learn the pattern once and reuse it all night. Pick the hour from the 12-hour clock. If the label is PM and the hour is 1 through 11, add 12. If the label is PM and the hour is 12, the hour stays 12 because noon is 1200. Copy the minute pair. Write four digits, padding the front with a zero whenever the result is a single-digit hour, which never happens on an evening conversion because the smallest evening result is 13.

Watch what the period label does to the tens digit. 10:30 PM and 10:30 AM share every digit except the leading one: the evening version is 2230 and the morning version is 1030. That is why the AM or PM on the source matters more than anything else on the clock face. The Astronomical Applications Department at the US Naval Observatory notes that Universal Time entries use the 24-hour clock for exactly this reason, so 1442 means 2:42 PM and 2117 means 9:17 PM with no label needed.

A quick sanity check keeps evening conversions honest. Any time from 1:00 PM to 11:59 PM lands between 1300 and 2359, so a converted evening result that starts with a 0, a 1 followed by a small second digit, or a 2 higher than 3 is a sign the 12 went on the wrong side. 2230 passes the check: it starts with 22 and sits inside the 1300 to 2359 evening band.

The whole ten o'clock hour at night

Once 10:30 PM is settled, every other minute of the ten o'clock hour follows the same path, and only the minute pair changes. The table below walks the hour in fifteen minute blocks, with the spoken form and the decimal a timesheet would record.

The decimal column divides the minutes by 60, so 15 minutes is 0.25 of an hour and 30 minutes is 0.5. The last row shows why many payroll systems round: 59 minutes is 0.9833 of an hour, a repeating decimal, and quarter hour rounding would call 10:59 PM the same as 11:00 PM. Minutes that land on 00, 15, 30 or 45 convert to clean decimals, which is one reason 10:30 PM is a friendly time to write on a record.

How 2230 is spoken and written

Say 2230 as one number plus a minute pair: twenty-two thirty. Hours from 1000 upward are spoken as a whole, and the minutes follow as their own pair, so the phrase is two words, not four. When the minutes are zero the word is hundred, which is why 2200 reads twenty-two hundred and stops. Radio procedure is stricter and reads every digit on its own, so over a channel 2230 becomes two two three zero.

Written forms vary by system. A duty log usually prints 2230 with no separator. An ISO style timestamp prints 22:30 with the colon, and a payroll field does not want either one: it wants 22.5, the decimal hour count. A common error is typing 22.30 into a decimal hours box, which the system reads as 22 hours and 18 minutes because 0.30 of an hour is 18 minutes, not 30. The number after the decimal point counts hundredths of an hour there, not minutes.

One more spoken form shows up in official contexts: appending hours, as in twenty-two thirty hours. It adds no information, but it signals that the number is on the 24-hour clock, and it is common in scripted announcements and recorded messages.

Reading 2230 back to 10:30 PM

The reverse conversion runs one subtraction. Look at the first two digits. If they form a number of 13 through 23, subtract 12 and mark the result PM. The 22 in 2230 gives 22 minus 12 = 10, so the time is 10:30 PM. If the first two digits are 12 exactly, the time is noon. If they are 00 through 09, the time is morning and the leading zero comes off: 0930 is 9:30 AM.

Context decides the date as well as the period. A ticket that says the lane closes at 2230 means 10:30 PM on the day printed on the ticket. A logbook entry stamped 2230 during an overnight event could belong to either of two calendar dates, so records that span midnight usually carry the date next to the four digits. The four digits pin the minute inside the day, and the date line pins which day.

2230 across common evening schedules

The same stamp shows up in many evening settings, and each one reads 2230 the same way. The table below pairs familiar ten thirty at night events with their 24-hour form so a log entry never has to be reworked.

Every row keeps the minute pair at 30 because only the hour block changes. If an event lands at 10:45 PM instead, the same row logic gives 2245, and 10:15 PM gives 2215.

Two worked examples with 10:30 PM

Example 1: a late shift clocks in at 10:30 PM and the timesheet runs on decimals. 2230 becomes 22 + 30/60 = 22.5 decimal hours. At a rate of $20.00 an hour, 22.5 x 20.00 = $450.00 of cumulative daily pay credit for the day up to clock in. The multiplication only works because the time was converted to a decimal first; 22:30 fed straight into the rate gives a wrong figure.

Example 2: a shift starts at 2230 and ends at 0630 the next morning. The end number is smaller than the start number, so the span crosses midnight and the end gains 24 hours: 0630 plus 2400 is 3030, and 3030 minus 2230 is 8 hours 00 minutes, or 8.00 decimal hours. At $21.00 an hour that is 8.00 x 21.00 = $168.00 of straight time. Both examples rest on the same base conversion, 10:30 PM to 2230, and both would break if the hour had stayed at 10.

Evening conversion mistakes to avoid

Four mistakes cover almost every wrong 10:30 PM conversion, and each has a one line fix.

• Skipping the 12: writing 1030 for 10:30 PM names the morning twin instead. Evening hours 1 through 11 all gain 12.
• Converting the minutes: 30 minutes is not 0.30 in the four digit form. The digits stay 30, and 0.5 belongs only in a decimal hours field.
• Rounding the hour down: 22 is not close to 10 in any useful sense here, yet a tired reader of 10 + 12 sometimes writes 20. The sum is 22, and the result must sit in the 1300 to 2359 band.
• Missing the colon form: 22:30 and 2230 are the same time in different notations, and a field that rejects one usually accepts the other.

A fifth trap hides in spoken orders. Twenty-two thirty and ten thirty sound nothing alike, which is a feature: on a noisy floor, the 24-hour form is harder to mishear across a twelve hour spread. The USNO page on Universal Time explains why the 24-hour clock is the standard for time entries, time.gov gives the official UTC and local readings from NIST and the Naval Observatory, and the OPM pay computation fact sheet covers how federal timekeeping turns hours into decimal pay.