Schedule guide

How local fight times are calculated — and when a countdown should say TBA

A fight date and a real start time are different kinds of information. A trustworthy local countdown needs a timestamp with a timezone or UTC offset. When a publisher supplies only a calendar date or an unlabeled venue clock, Fights Now keeps the exact time and timed reminder unavailable while preserving the useful date.

By Fights Now editorial deskReviewed Source-led explainer

Key takeaways

  • A date-only announcement cannot support a precise countdown.
  • A qualified instant is formatted in the visitor's browser timezone using rules for the event date.
  • Without a qualified time, the timed reminder stays unavailable but calendar export remains an all-day date entry.
  • A published card or broadcast start is not a guaranteed main-event walkout time.

The minimum information for one real instant

A reliable start combines a date, clock time and timezone. An ISO timestamp ending in Z identifies UTC. An ending such as -04:00 supplies the offset at that instant. A venue-local clock with no zone can describe several possible instants, especially around daylight-saving transitions, so it is not silently treated as UTC.

KSW illustrates the safeguard: its event pages expose local-looking clock values without a reliable timezone offset. The collector validates the value but leaves the stored UTC fight instant empty. A less cautious conversion could shift the card by hours for readers elsewhere.

Worked conversion example

The following is an illustrative timestamp, not a real event listing. A source value of 2026-08-20T20:00:00-04:00 identifies the same instant as 2026-08-21T00:00:00Z. A browser whose event-date offset is +02:00 displays 02:00 on August 21. The local calendar date changes, but the underlying instant does not.

One illustrative instant in three representations
RepresentationDisplayed valueMeaning
Source offset2026-08-20 20:00 -04:00Publisher-qualified clock
UTC2026-08-21 00:00 ZNormalized instant
Browser at +02:002026-08-21 02:00Visitor-local display for that instant

Daylight saving belongs to the event date

Timezone rules can differ between the day a reader opens the page and the future event day. Formatting libraries apply the browser timezone's offset for the event instant. Reusing today's offset for a winter or summer card can produce a one-hour error even when the venue and reader have not changed.

An explicit numeric source offset already identifies the instant; the browser timezone is then used only for display. If a source later publishes a qualified correction, the stable event identity allows the accepted instant to change without inventing a second event.

What happens when only the date is known

Date-only information still supports a place in the event directory. It does not support an hour, countdown or notification scheduled relative to that hour. Fights Now's calendar download remains useful by creating an all-day entry, while the local browser reminder refuses to arm until a timezone-qualified start exists.

Public behavior for date-only source data
FeatureBehavior
Event dateShown as published
Exact timeTime TBA
CountdownUnavailable until a qualified instant exists
Timed browser reminderNot set; the interface explains what is missing
Calendar downloadAll-day entry on the published event date

Card time is not bout time

Promotions can publish separate windows for early prelims, prelims and the main card without guaranteeing a walkout time for every bout. A card start can be displayed under that label; it should not be relabelled as the exact start of the main event. Bout order, fight duration, breaks and production changes make that precision impossible without a dedicated source field.

The same distinction applies to a broadcast link. A stream becoming available does not establish that a particular fight has begun. Live status requires its own trusted status evidence rather than a clock passing or a link existing.

How readers can verify a displayed time

Open the linked event source and look for a timezone abbreviation, explicit UTC offset or fully qualified timestamp. Then compare the displayed source date with the local date, because crossing midnight is expected. If the source has changed, report the exact page and new qualified value through the corrections route instead of converting an unlabeled clock by hand.

Sources and further reading

Primary or directly relevant publications used to check this guide. External publishers control their own pages and update schedules.