isValidFixUtcTimestamp
Signature
Section titled “Signature”isValidFixUtcTimestamp(value: string): booleanisValidFixUtcTimestamp(value: void | {} | null | undefined): booleanisValidFixUtcTimestamp(value: unknown): value is stringReturn true when value is a FIX UTCTimestamp that states a real UTC second.
- True exactly when
parseFixUtcTimestampreturns a value for the same argument: the validator calls the parser, so the two cannot disagree. - Checks the calendar and the leap-second table as well as the shape: 30 February, hour 24 and a
60on a day with no inserted leap second are false. For the shape of an ISO second 60 alone,hasSecond60; for an ISO leap second,isLeapSecond. - A fraction of 3, 6, 9 or 12 digits, or none; any other width is false (FIX Latest: other widths are “with bilateral agreement”, which a value does not carry).
- A value that is not a string, a
Stringobject included, returns false. A true result narrows anunknownvalue tostring.
Parameters
Section titled “Parameters”| Parameter | Type | Description |
|---|---|---|
value | string | any value; a string is checked as a FIX UTCTimestamp (e.g. “20240615-14:30:00.123”) |
Returns
Section titled “Returns”boolean indicating validity
Examples
Section titled “Examples”import { isValidFixUtcTimestamp } from "@northguild/gmt/finance/validate";
isValidFixUtcTimestamp("20240615-14:30:00.123") // trueSource
Section titled “Source”© 2026 NorthGuild · Licences
Code examples: MIT-0. Packages: MIT. Third-party data and components: their own licences, credited where they appear. Everything else: © 2026 NorthGuild, all rights reserved.