# Two 01:30 timestamps are not necessarily duplicates

Practical data checks · Mock walkthrough

Two 01:30 timestamps can represent different instants. Inspect mock CSV offsets, verify the UTC calculation and avoid confusing clock text with duplicate records.

Updated Nov 4, 2026 · [RowCove](https://rowcove.com/)

**Are two matching 01:30 timestamps necessarily duplicates?** No. With offsets -04:00 and -05:00, the two mock timestamps represent 05:30 and 06:30 UTC. Preserve the source offset and establish the timestamp contract before deduplicating.

**On this page** [Watch the example](https://rowcove.com/guides/csv-daylight-saving#watch) [All practical guides ↗](https://rowcove.com/guides)

## Watch the mock example

Your browser cannot play this video. Use the video download below. Illustrated mock data · English synthetic narration · RowCove team (commercial tool)

[Open or download the video](https://rowcove.com/media/csv-daylight-saving.mp4) · [English captions](https://rowcove.com/media/csv-daylight-saving.vtt)

The NIST 2026 schedule places the US fall-back transition on November 1 in
participating regions: [NIST daylight saving time rules](https://www.nist.gov/pml/time-and-frequency-division/popular-links/daylight-saving-time-dst) .
This does not describe every country or every US region.

Consider two completely synthetic CSV rows:

Synthetic (mock) examples

| Mock record | Original timestamp | UTC instant |
| --- | --- | --- |
| mock-001 | 2026-11-01T01:30:00-04:00 | 2026-11-01T05:30:00+00:00 |
| mock-002 | 2026-11-01T01:30:00-05:00 | 2026-11-01T06:30:00+00:00 |

If an export keeps only the clock text, both look like 01:30. With their explicit
offsets they describe instants an hour apart. That can matter when reviewing
logs, market-data exports or other time-series records. It does not prove that
any particular pair of records is unique: use the rest of the source contract.

The standard library can demonstrate the distinction:



```
from datetime import datetime, timezone

a = datetime.fromisoformat("2026-11-01T01:30:00-04:00")
b = datetime.fromisoformat("2026-11-01T01:30:00-05:00")
assert a.replace(tzinfo=None) == b.replace(tzinfo=None)
assert (b - a).total_seconds() == 3600
print(a.astimezone(timezone.utc).isoformat())
print(b.astimezone(timezone.utc).isoformat())

```



Keep the original timestamp, inspect complete values and establish whether
sorting compares text or instants. If the offset was never stored, simply
adding a timezone afterward does not establish the original instant. Named
zones, ambiguous local times and parsing policies need separate checks.

RowCove can help inspect the original fields in supported local files; this is
not a claim that every reader automatically reconstructs missing timezones or
normalizes all timestamp representations. The calculation above is independent
Python. Check the output before passing a transformed file to the next step.

Disclosure: RowCove team, commercial local data tool. AI-assisted draft, generated
mock rows only. No customer, trading strategy, real event feed or performance
measurement is included. Video assets illustrate these rows; they are not a
recording of the RowCove interface.

## Try the first page on your own data.

Start on Windows or macOS: source information and up to 100 records, read-only. Review reader capabilities before planning a full-file Pro workflow.

[Download for Windows ↓](https://rowcove.com/download/windows) [Download for macOS ↓](https://rowcove.com/download/macos)

Version 0.1.1 · Windows x64 · macOS Apple Silicon · [Install guide →](https://rowcove.com/download)

[Reader capabilities →](https://rowcove.com/formats)

---

Canonical page: https://rowcove.com/guides/csv-daylight-saving

Updated: 2026-11-04

[Related Agent reference](https://rowcove.com/agent/workflows.md)