SECOND in Excel: Extract Seconds and Preserve Duration Meaning

• Introduced: first introduction version is not established by the official history reviewed; the current product list is not a launch record.
• Availability: official help lists Excel for Microsoft 365, Excel for Microsoft 365 for Mac, Excel 2024, Excel 2024 for Mac, Excel 2021, Excel 2021 for Mac, Excel 2019, Excel 2016.
• Checked: October 14, 2026; official SECOND reference. Documentation and independently modeled examples; no native Excel execution or broader platform certification.

=SECOND(serial_number)

The required input supplies a time as a numeric serial, recognized text or another formula result. Format the answer as General or Number so the extracted component remains visible as a number.

Microsoft’s dedicated reference describes an integer seconds field but does not specify every fractional-second rounding boundary. The primary examples therefore use whole-second inputs. Behavior from another spreadsheet that rounds seconds must not be assumed to prove Excel’s rule.

=SECOND(TIME(8,15,0))
=SECOND(TIME(8,15,30))
=SECOND(TIME(8,15,59))
=SECOND(TIME(8,16,0))

Expected results are 0, 30, 59 and 0. Advancing to the next minute resets the seconds field to zero. A result of zero can describe any exact minute, not only midnight.

The numeric fraction 0.5 is exactly noon, so =SECOND(0.5) has expected result 0. It is half a day, not half a second.

=SECOND(DATE(2026,10,14)+TIME(8,15,30))
=SECOND(DATE(2026,10,15)+TIME(19,45,30))

Both expected outputs are 30. SECOND discards the other fields from its result; the timestamps are not equal simply because their seconds components match.

Use the complete numeric timestamps for chronological ordering or elapsed-time comparisons. The component can support a within-minute diagnostic but cannot identify a unique event.

Create A2:A5 with numeric times 08:15:00, 08:15:30, 08:16:00 and 08:16:59. In B2 enter and fill down:

=SECOND(A2)=0

Under this whole-second fixture, expected results are TRUE, FALSE, TRUE and FALSE. Two inputs lie on an exact whole-minute mark.

If the real source can contain subsecond values, the integer component alone is insufficient to certify exact minute alignment without verifying its fractional behavior. The worked Boolean controls deliberately do not make that broader promise.

For whole-second inputs, combine the minute and second conditions:

=AND(MOD(MINUTE(A2),15)=0,SECOND(A2)=0)

For 08:15:00, 08:15:30, 08:30:00 and 08:31:00, expected results are TRUE, FALSE, TRUE and FALSE. Testing only the minute field would incorrectly accept the second row as an exact quarter-hour boundary.

These labels implement a particular scheduling rule. They do not prove that the date is a working day, that the time is in a required zone, or that a scheduled event actually occurred.

=SECOND(TIME(1,2,3))
=TIME(1,2,3)*86400

Expected results are 3 and 3723. The second calculation retains the hour and minute contributions: 3600+120+3. The same distinction applies when an interval is calculated by subtracting two complete timestamps.

For a multi-day duration of 90061 seconds, its day quantity is 90061/86400. SECOND extracts expected component 1, while multiplying the complete quantity by 86400 recovers 90061. The duration includes one day, one hour, one minute and one second.

A clock-style display can wrap after a day; the stored numeric duration and a suitable numeric unit conversion preserve the total. Do not label a wrapped component as elapsed seconds.

With =DATE(2026,10,14)+TIME(8,15,30) in A2:

=TIME(HOUR(A2),MINUTE(A2),SECOND(A2))

Expected time: 08:15:30, or 29730/86400 of a day. The returned time excludes the date. Adding the positive modern timestamp’s INT(A2) date portion reconstructs the complete date and whole-second time for this fixture.

This composition is not a lossless normalization for every input. It does not establish preservation of subsecond precision, historic negative serials or original text formatting.

The dedicated source does not provide a complete invalid-text, blank, Boolean or negative-serial error table. Those results remain separate native test cases. TIME constructs numeric times; TIMEVALUE parses recognized text; MINUTE and HOUR extract other components.

Keep whole-second examples separate from millisecond measurements. Rounding, measurement precision and time-zone conversion need explicit rules rather than assumptions inferred from a small integer result.

• Microsoft SECOND reference.
• Editorial testing standards.

Expected results are independent calendar/arithmetic models or explicitly documented rules, not captured native output. Examples use English function names and comma separators. Input dates and schedules are fictional.