Calligra Sheets SECOND Function: Extract the Second from a Time

SECOND extracts the second-of-minute component of a time. For a real typed time 14:35:42, =SECOND(TIME(14;35;42)) has expected result 42. This is useful when building a scheduling, reporting or time-quality-check worksheet. It does not return a full time or elapsed duration. The source also registers SECONDS with the same implementation callback; SECONDS is covered here as a synonym rather than a separate calculation.

Version, scope and validation: This guide is based on KDE’s handbook and Calligra 26.08.2 source (KDE release dated October 8, 2026; sources checked October 12, 2026). The pinned source comes from commit 72123cc643f6625351139e7df294544255a1056f. The source and handbook establish registrations and intended behavior for that code snapshot, not a guarantee for every binary, platform, installation or imported file. Calligra Sheets was not run in this research. Every worksheet number labeled expected is independently calculated or drawn from a documented KDE example; none is a screenshot or result observed in a native build.

=SECOND(time)
=SECOND()
=SECONDS(time)

• time — optional, first and only argument. KDE’s English-language handbook describes the time argument as Text; the compiled function registration permits zero or one argument (setParamCount(0, 1)), and the callback passes a supplied value through Calligra’s asTime() converter. That allows a typed time value as well as documented accepted time expressions, but does not prove that every user-entered string will parse in every locale.
• Omitted argument: =SECOND() takes the current local time, then returns its second component. It has no fixed default time. Its output changes with the clock and evaluation; do not hardcode an expected number for an unrecorded test run.
• Return type: KDE calls this a whole number; the pinned callback returns an integer Value. The conceptual second component is 0–59, subject to the SECOND fractional-rounding source caveat explained below where applicable.
• Argument order: with one argument, supply a single time expression or cell reference. It does not take separate hours, minutes, seconds. If you have separate components, construct a time first using TIME(hours;minutes;seconds).

Regional settings: Formulas in the KDE English handbook use ; between multiple parameters (as in TIME(14;35;42)). An installed spreadsheet might show a different separator, different 12/24-hour display, localized time literals or comma decimal separators. Check your local formula editor. For reusable examples, use TIME() with numeric arguments rather than assuming that the literal text "02:03:04" parses identically everywhere. Do not mistake a visually formatted date/time string for a typed spreadsheet time.

Open a new Calligra Sheets worksheet. In A1, type Typed time; in B1, type SECOND result. Enter each formula below into column A; enter the corresponding =SECOND(A2)-style formula into column B. Copy B2 down to B7. Format A2:A7 as time (hh:mm:ss) if needed, while leaving B as ordinary numbers.

How these were checked: TIME(h;m;s) in the examined KDE code creates an internal Time from three numeric components. The SECOND callback extracts its second property. I independently parsed the six entered h:m:s triplets to obtain the listed expected integers. Native execution: unavailable. The cell’s displayed time could differ with regional formatting, but the canonical 24-hour components are unambiguous for these controlled inputs.

To verify a result yourself, check that A3 represents 14:35:42, select B3 and inspect the formula bar. If B3 disagrees with the independently computed 42, confirm that A3 is a time value, not a string that merely looks like one, and that the installed Calligra version has the same semantics.

The direct nested formula =SECOND(TIME(14;35;42)) → 42. This removes any dependencies on cell formatting or copy/fill operations and is the safest initial calculation to compare across installations.

KDE documents =SECOND("22:10:12") → 12 and =SECOND(0.1234) → 42. These are documentation-supplied values, not results observed in a Calligra build.

The documented fractional-day examples should not be confused with an unconditional promise that arbitrary text timestamps, invalid dates or nonstandard input serials have identical behavior in Excel and Calligra. The native parsing and representation of fractional times were not tested.

For timestamp quality checks, compare second components from two captured time cells, but do not calculate elapsed seconds by subtracting two SECOND values. A time of 14:36:02 follows 14:35:58 by four seconds; SECOND(end)-SECOND(start) produces −56, not four. Use full time/datetime subtraction with an appropriate duration format, especially around midnight.

Second independent calculation: =HOUR(A3)*3600+MINUTE(A3)*60+SECOND(A3) is expected to yield 52,542 seconds since midnight for 14:35:42 (50,400 + 2,100 + 42). This is clock-time decomposition, not elapsed seconds between dates. This calculation is based on the same typed times used above, without asserting that the formula ran in a native Calligra installation. If time is imported as text, explicitly parse or enter it as time before applying the extraction function, and verify the result in the target locale.

For complete duration arithmetic, work with full timestamps and appropriate formatting rather than extracting the second component and assuming it reflects elapsed time. Time zones and daylight-saving adjustments belong in timestamp handling, not in these component functions.

Source-level precision caveat: func_second computes time.second() + qRound(time.msec() * 0.001) rather than simply returning time.second(). Fractional milliseconds can therefore increment the second result; near 59 seconds, a source-inferred value of 60 may be possible. Whether the engine normalizes such inputs, and which releases show it, are not established without native execution. Avoid claiming all outputs always stay within 0–59.

• Missing value versus omitted argument: =SECOND() has intentional current-clock semantics; =SECOND(A8) when A8 is blank presents an explicit reference, and its conversion behavior is a separate question. Do not infer the latter from the former. The actual blank-cell result requires native validation.
• Invalid or non-localized text: Conversion failures from asTime() are passed back as error values by the callback; the exact displayed error message for an invalid timestamp is native-unverified. The return code and text displayed in the user interface are not verified here.
• Stored number versus visible time: A cell can look like 14:35:42 while containing a text label. Inspect the formula bar and use TIME() to distinguish display formatting from conversion. Values outside ordinary clock ranges may be normalized by the input-conversion routines or rejected; avoid unverified assumptions.
• Alias and file interchange: The source registers SECONDS to the same callback. When exporting to another spreadsheet application, the plural name may not be supported as a function there. The canonical singular name is preferable for portability.
• Platform/edition scope: This evidence is pinned to one KDE source release; native Windows/macOS packaging, downstream patches, locales and spreadsheet file conversions have not been separately exercised.

Whole-second TIME() values avoid fractional-millisecond ambiguity. If input has fractions of seconds, investigate the exact version and source conversion rather than assuming Excel’s rounding/truncation rules.

Calligra 26.08.2: SECOND accepts 0–1 arguments, and SECONDS maps to the same implementation (per KDE registration). The callback converts an explicit argument to Time and reads its second component (per source). Microsoft Excel: Excel documents SECOND(serial_number) with a required argument and says the result is in 0–59. Calligra accepts zero or one argument and has the source-level subsecond rounding caveat described here. These two differences mean imported formulas merit testing. Microsoft documentation is used only to describe Excel, not as proof of Calligra behavior.

What is likely portable: =SECOND(A2) where A2 contains a conventional, properly typed 24-hour time. What is not automatically portable: the no-argument form, the alternate plural name, localized textual inputs, unusual duration values, and in SECOND’s case the source’s subsecond handling. Check the destination application’s formula separator and time interpretation before trusting a migrated workbook.

1. Unexpected value: Compare against a nested typed-time formula, =SECOND(TIME(14;35;42)) → 42. If this works but a referenced cell does not, inspect its underlying value or text format.
2. Formula name not recognized: Check exact spelling SECOND and the target version. SECONDS is source-registered in Calligra 26.08.2 but does not mean all spreadsheet products recognize it.
3. Wrong hour or minute after import: Confirm whether the source uses a 24-hour time, has AM/PM suffixes, and includes a date or time zone. Convert consistently before extracting components.
4. Error on a typed string: Compare a literal documented example with TIME(h;m;s). If only the string fails, suspect locale-aware text parsing. Record the exact application version and observed error.
5. Unexpected change when revisiting sheet: Avoid the no-argument invocation for fixed historical records: it reads the current clock, not a saved event timestamp.
6. Duration exceeds 24 hours: Use an actual duration/timestamp calculation, not a component value. A formatted 26-hour duration is not guaranteed to return a total of 26 hours from HOUR.
7. Native source inconsistency: Use a known TIME input and compare with this evidence; report the installed platform, locale, exact formula and observed result to the editor. The native check is pending, not silently presumed successful.

• KDE’s official SECOND handbook section — documents the purpose, text-labeled parameter, examples and no-argument behavior. Accessed 2026-10-12.
• KDE’s TIME handbook section — supplies reproducible numeric time construction. Accessed 2026-10-12.
• KDE’s SECONDS handbook entry — distinct heading; same implementation in the pinned release. Accessed 2026-10-12.
• Pinned KDE function registrations and pinned time-extraction callback — review source-specific arity, aliases, conversion and error behavior. Verified against pinned commit 72123cc643f6625351139e7df294544255a1056f on 2026-10-12.
• Official KDE Calligra release history — lists 26.08.2 dated 2026-10-08. Accessed 2026-10-12.
• Microsoft’s Excel SECOND reference — comparative Excel-specific required argument and range. Accessed 2026-10-12.