You ran late on Sunday evening, yet the log places the workout on Monday. Or its start differs by exactly one hour from your recollection while distance and duration look right. Such an error does not necessarily arise during recording. The file may store the correct instant while the viewer displays it in another time zone.
Clock changes can make this particularly apparent: in autumn, the same wall-clock reading can represent two different instants. To understand this, we separate an absolute instant, UTC offset, local time-zone rules and running duration. Our examples show when checking display is enough and why randomly shifting every timestamp in a file by one hour could be harmful.
One instant can have several local labels
The RFC 3339 internet timestamp standard uses an unambiguous relationship to UTC, Coordinated Universal Time. The suffix Z denotes zero UTC offset; +01:00 denotes a positive one-hour difference. Local clock time identifies an instant together with its offset. “10:00” alone, without date and time-zone context, cannot establish which ten o’clock in the world is meant.
In our simple winter example, 09:00Z and 10:00+01:00 represent the same instant. If a programme displays the first and a watch the second, their numbers differ while the recording may remain entirely consistent. Do not automatically add an hour to the file. First establish whether the interfaces display data within the same local frame.
A time-zone name and current offset are different too. “Europe/Budapest” may identify a location-based rule set, while +01:00 only describes a particular offset. The official IANA time-zone database description handles historical offsets and daylight-saving rules separately. A fixed +01:00 does not automatically replace a local time zone valid throughout the year.
In autumn, half past two can happen twice
The European Commission’s published 2022–2026 schedule states that the 2026 summer-time period ended on 25 October at 01:00 UTC. The following example uses Budapest’s summer +02:00 and winter +01:00 offsets. We state the date because interpreting an instant always depends on the rules for that place and day.
In our example on 25 October 2026, 02:30+02:00 corresponds to 00:30Z. The same day’s 02:30+01:00 corresponds to 01:30Z. The wall-clock label matches, yet one hour passes between the instants. A table retaining only the local date and 02:30 cannot reliably distinguish those possibilities without the offset.
Ambiguity can also confuse event order. A list sorted by local clock numbers around the change can produce the wrong sequence if offsets are ignored. The runner’s time did not reverse; the label repeated. Correct chronological ordering requires unambiguous instants and separate handling of display rules.
Local date and UTC date may differ
In our November example, a short run starts at 00:20+01:00 on 20 November. In UTC, this is 23:20Z on 19 November. A raw export showing UTC days may place the start on Thursday while the local log places it on Friday. Even a one-hour offset can therefore change the date. Proximity to midnight makes the shift visible.
This can affect weekly summaries too. In our example, an eighteen-kilometre run beginning at 00:30 on Monday belongs to the new week in local winter time but starts at 23:30 on Sunday in UTC. If one system uses local calendar weeks and another UTC weeks, weekly distance can differ without any workout being lost. Compare grouping boundaries.
Month and year boundaries reveal the same problem in larger summaries. A local start shortly after 1 January may still belong to the previous year in UTC. Before correcting a date, inspect the full timestamp rather than only the day on a log tile. Correct data can look misplaced in an unsuitable calendar view.
Enlarge imageA FIT timestamp and its local supplement are separate data
The Garmin FIT decoding guide explains that FIT timestamps almost always use seconds from Garmin’s UTC epoch of 31 December 1989. A separate Local Timestamp field in the Activity message can provide a local-time supplement. Not every manufacturer fills it, and validity must be checked. The difference between the fields can help determine the offset.
The guide also explains that, without the local supplement, a processor may find a time zone from the first location. This raises a practical question: is a usable position available, and which location does the receiver assign to the recording? Indoor runs or exports without location can follow another path. Not every file provides the same clues for local display.
A number in a binary field must therefore not be treated as an everyday date or a value relative to another format’s epoch. The number alone does not fully describe time; the format definition makes it interpretable. An incorrect epoch can cause a vastly larger date error than a summer–winter shift. One-hour and decades-long discrepancies suggest different troubleshooting directions.
GPX and CSV may show different labels
The official GPX 1.1 schema allows times to be associated with track points. Inspect the full date, clock time and time-zone notation in a text timestamp. Do not assume a locally displayed time and a Z-suffixed file time should already be identical text. Different descriptions can represent the same instant.
CSV is a simple tabular container; the exporter determines its time column’s meaning. One programme may write UTC, another local time, perhaps with a separate offset column. A header saying only “time” offers little context. In your working table, retain both the original time string and the unambiguously interpreted instant so conversion remains checkable.
A spreadsheet’s automatic date detection can also conceal information. If it reformats a cell for display, the original offset may no longer be visible. For checking, compare raw text and documentation in a working copy. An attractively formatted date does not prove import applied the right time zone.
Without GPS, profile settings may decide
The official Strava troubleshooting guidance dated 17 September 2026 says to check the profile time zone for activities without GPS. If a device supplies no appropriate time-zone information, the service may use the profile’s zone. This illustrates how a recorded instant and its later local display can depend on settings in several systems.
In our example, a runner returns home with profile settings used in another country and uploads an indoor run. The file’s start is correct, but the receiver displays it outside the intended local zone. Changing the date on the watch would intervene in the wrong place. Check the source instant separately from display applied through the profile.
Different behaviour in outdoor and indoor runs is therefore a useful clue. If only activities without location appear on the wrong day, first investigate the source of time-zone information. If every recording from every device shifts alike, another shared setting may be involved. This is not a finished diagnosis, but a narrower investigation: the pattern suggests where to seek a documented explanation.
Duration is not the difference between wall-clock numbers
In our autumn example, a run begins at 02:50+02:00 and ends at 02:20+01:00. The absolute instants are 00:50Z and 01:20Z, so thirty minutes passed. Subtracting wall-clock labels alone would give minus thirty minutes. Actual duration is not negative; the clocks went back. Use the difference between unambiguous instants.
In a sports file, elapsed time, timer-running time and time classified as moving can also differ. Stopping at lights or pausing manually is a different question from time zones. If total time is right but the start’s clock label wrong, do not immediately alter every duration. Start-time display and internal workout timing are separate checking levels.
Shifting every timestamp uniformly can preserve differences while creating the wrong absolute history. Duration stays the same while the run becomes linked to different weather data, group departures or race times. Plausible pace does not prove the correction is right. Change timestamps only with a known reason and a retained original.
Enlarge imageA checking sequence for a workout shifted by one hour
First note when and where you started by the local clock and what date the receiver shows. Save the original activity file. Then identify a full file timestamp with its offset. Decide whether the instant itself is wrong or the same moment is being viewed in another zone. Do not build an assumed cause of the one-hour difference into the correction.
Next check profile, phone, watch and exporter time-zone settings. Note where zone selection is automatic or fixed. Correct local time needs the rule for the particular date, rather than only today’s offset. Checking in November does not justify rewriting July’s recording with November’s offset.
Third, compare several nearby activities: one before the clock change and one after, preferably with outdoor and indoor examples. If a strange date jump occurs only at one file’s beginning or end, uniformly shifting the entire file is probably not the best first step. First identify where the difference starts. Your checking notes can then give manufacturer support more precise information too.
Consider social data before re-uploading
Strava also warns that deleting and re-uploading an activity can lose its original comments, likes and photographs. A new profile setting’s effect on future uploads therefore differs from fully replacing an existing post. The cost of correction is not measured only in clock accuracy.
In our decision example, an old group-run log is shifted by an hour but contains many personal pictures and conversations. First document the correct start and check future recordings. If replacing the old recording is necessary, save everything that can be preserved and understand the service’s current behaviour beforehand. A technical time correction should not accidentally destroy social data.
A correct running file appearing on the wrong day can often be understood through different interpretations of the instant and local calendar. UTC, offset, date-specific zone rules and duration are separate concepts. Checking them separately avoids unnecessary one-hour rewrites while preserving the run’s actual timing. Start from the original recording and make any correction traceable and checkable.
Sources
- RFC 3339: UTC offsets and unambiguous internet timestamps.
- IANA: time zones, historical offsets and daylight saving.
- Garmin FIT: timestamps and conversion to local time.
- Topografix: GPX 1.1 time data.
- Strava: official troubleshooting for incorrect dates and start times.
- European Commission: 2022–2026 summer-time dates.
How Futószív articles are prepared: our editorial guidelines.


