Contact

SECOND in WPS Spreadsheet: Extract Whole Seconds Without Losing Minutes or Days

Date & Time Intermediate WPS Spreadsheet

Use WPS SECOND to inspect a time’s 0–59 second field, compare it with total elapsed seconds, and keep fractional-boundary behavior explicit.

Verification status: See the evidence and test scope described in this guide. How formula examples are checked

Quick answer: SECOND(serial_number) extracts the integer second component from 0 through 59. It does not return total seconds in a duration. Keep full time or date-time values when calculating elapsed totals.

Availability and version history

  • Introduced: documented by 2019-06-12 in the official WPS lesson; original introduction is not established.
  • Availability: WPS Office for Windows Personal; the lesson metadata gives no numeric release.
  • Scope: exact current supported builds remain unverified; the historical Windows lesson does not establish all WPS clients.
  • Checked: October 14, 2026 against complete function-specific documentation. Examples are independent expectations; no native WPS test was performed.

Syntax and input scope

=SECOND(serial_number)

The WPS reference describes time inputs as recognized text, numeric day fractions or formula results. The main examples below use integer-second TIME constructions. Outputs are independent documentation-based expectations, not native results.

Use General or Number format for the extracted component. A time format applied to the integer 25 does not mean 25 seconds; numeric spreadsheet time units are days. The expected component should remain visibly 25.

Example 1: extract a complete second field

=SECOND(TIME(4,30,25))
=SECOND(TIME(18,45,0))
=SECOND(0.78125)

Expected outputs are 25, 0 and 0. The first reproduces the calendar-independent time described by the WPS walkthrough. The decimal input is its documented 18:45 control, with no seconds component.

The input 04:30:25 contains 16225 seconds since midnight. SECOND returns only 25. A display that omits seconds can conceal that field without removing it from the stored value.

Example 2: compare a component with 90 elapsed seconds

Put =TIME(12,0,10) in A2 and =TIME(12,1,40) in B2:

=SECOND(B2-A2)
=(B2-A2)*86400

Expected outputs are 30 and 90. The interval is 00:01:30, so its second field is 30. The day-to-second conversion uses 24×60×60 = 86400.

Useful exact-second controls are intervals of 59, 60, 61 and 120 seconds. Their second components are 59, 0, 1 and 0, while the elapsed totals remain 59, 60, 61 and 120.

Advanced example: retain an entire day

Create A5 with =DATE(2026,10,14)+TIME(0,0,0) and B5 with =DATE(2026,10,15)+TIME(1,1,1):

=SECOND(B5-A5)
=(B5-A5)*86400

Expected outputs are 1 and 90061. The full interval is 25 hours, 1 minute and 1 second. The extracted second alone cannot recover its elapsed length.

Small floating representation differences can affect a displayed arithmetic total. Compare a sensible numeric tolerance for a unit conversion rather than asserting exact binary equality, and keep native boundary behavior unverified.

Advanced example: check a minute-aligned schedule

For exact integer-second values in D2:D5, enter 08:00:00, 08:00:30, 08:01:00 and 08:01:59 with TIME. Fill:

=SECOND(D2)=0

Expected flags are TRUE, FALSE, TRUE and FALSE. This checks the second component of the controlled inputs; it is useful when a schedule is supposed to start on whole-minute boundaries.

It is not a universal proof that an arbitrary imported timestamp has no fractional seconds. The captured WPS source does not specify how SECOND rounds, truncates or carries subsecond values near a boundary. Those cases must be tested separately in the intended build.

Use MINUTE and HOUR to inspect the other clock fields. Use TIME to construct exact-component controls and TIMEVALUE for recognized text.

Negative values, text-number/Boolean/blank coercion, malformed input error codes and fractional-second ties remain unverified. The distinction between a whole-second component and total elapsed seconds is independent of those unresolved input boundaries.

References and verification

The complete function definition and walkthrough were reviewed. Worked outputs are independent calendar and time models; source ambiguities and native boundaries remain explicit.