UTC clock · DST · executable quality · state gates
Best Times to Trade 6Z: Measure Market Quality by State
The same clock label can describe a different 6Z market. Chicago and New York shift daylight saving on dates that do not follow South Africa; a SARB announcement can transform an otherwise ordinary bin; U.S. data can arrive inside it; and liquidity can migrate between contracts. The “best” time is the interval that meets measured quality gates for the intended order today.
- Clock
- UTC + IANA zones
- Book
- Spread + depth
- Order
- Size + urgency
- Fixed best hour
- Not claimed
Civil time is versioned data
Store UTC and Reconstruct Local Time
Preserve the exchange timestamp and stated timezone, then derive UTC and historical local labels with a timezone database. Store Chicago, New York and Johannesburg labels separately. South Africa does not follow U.S. daylight-saving transitions, so hard-coded offsets silently shift comparisons during parts of the year.
Preserve
Keep raw timestamp, precision, sequence and source timezone.
Resolve
Use historical IANA timezone rules, not a fixed UTC offset.
Normalize
Store UTC while retaining Chicago, New York and Johannesburg labels.
Tag
Add exchange date, holiday, event, pause, roll and expiry states.
Bin
Assign fixed UTC intervals only after earlier fields are frozen.
Worked bin decision
Score one interval for two different orders
Assume a UTC bin has an acceptable median spread in the historical sample. First score a patient one-contract limit order, then a larger urgent order. Use the same eligible dates but compute capacity and realized outcomes for each policy separately. The small order may pass because ordinary depth covers its quantity and its historical fill-rate and delay stay inside registered bounds. The urgent order may fail because modeled book sweep, lower-tail depth and conservative slippage exceed its budget. Calling the bin universally “best” would erase this difference.
Now apply the live state gates. Confirm the dated contract is active, no excluded SARB or U.S. release overlaps the order lifecycle, current spread and quote age are within validated ranges, and recent depth is not out of distribution. Store the decision even when no order is sent. Later review submitted, canceled, partially filled and rejected orders together. If realized shortfall repeatedly breaches the bin forecast, suspend permission while investigating feed timing, queue delay, regime drift and contract migration.
“South African hours” or “U.S. morning” must resolve to exact historical endpoints. Publish both the UTC interval and the local interpretation used for each sample.
Compare the whole day
Create Bins Before Ranking Them
Use non-overlapping fixed UTC bins across the complete eligible session as the primary grid. Add local-session or event-relative overlays only as secondary analyses. Freeze bin width and minimum observation count before viewing results so the winning window is not engineered after the fact.
Primary grid
Fixed UTC intervals
Complete coverage prevents named-session selection from hiding adjacent conditions.
Local overlay
Historical clock labels
Johannesburg, London, New York and Chicago labels follow valid date-specific offsets.
Event overlay
Relative-time windows
Official release time is zero; pre- and post-event periods are registered separately.
Lifecycle
Dated-contract state
Active, migration and expiry-proximate observations do not share one ranking.
The best interval depends on the order
Measure Quoted, Traded and Realized Quality
Rank intervals for a declared quantity and urgency. Daily volume alone cannot identify the lowest-cost time; an active window can still have wider spreads or poor fills during information arrival. Report median conditions, tails, observation counts and capacity limits.
| Dimension | Measure | Required evidence | Boundary |
|---|---|---|---|
| Spread | Time-weighted inside spread | Sequenced bid and ask updates | Snapshots can miss brief widening |
| Depth | Quantity through fixed tick bands | Multi-level book at valid timestamps | Displayed size may cancel |
| Activity | Trade count, volume and size distribution | Corrected trade records | Activity is not low cost |
| Capacity | Modeled sweep for declared size | Synchronized book levels | Future replenishment is unknown |
| Experience | Fill rate, latency and implementation shortfall | Order lifecycle timestamps | Specific to route and policy |
Do not average unlike states
Separate Events, Holidays and Rolls
High-volume event windows and ordinary windows answer different questions. Build dedicated strata for scheduled policy and data releases, local and exchange holidays, early closes, pauses and contract migration. Feed gaps are failures, not quiet periods.
| State | Treatment | Reason |
|---|---|---|
| SARB decision | Official timestamp-relative window | Domestic repricing can dominate the clock effect |
| FOMC and U.S. data | Official event window plus ordinary comparison | Dollar information arrives at a known time |
| Holiday or early close | Separate or ineligible under frozen calendar | Participation and schedule differ |
| Roll and expiry | Dated-contract lifecycle stratum | Liquidity can migrate between expiries |
| Feed interruption | Fail the interval | Missing quotes cannot certify good conditions |
Convert a historical profile into current gates
Choose Go, Reduce, Wait or Reject
Thresholds are learned in training data and locked before validation. A current interval is eligible only when its exact contract, event state, spread, depth, quote stability and expected impact resemble the state that was tested for the intended order.
Go
All gates pass
The order size and style were validated in this state and current inputs remain inside bounds.
Reduce
Capacity is lower
Spread passes but depth or conservative impact supports only the smaller registered size.
Wait
Temporary exception
Event, unstable quotes or roll migration requires a new observation after the state clears.
Reject
Evidence is absent
Fields, sample coverage or live quality fail. The clock label cannot rescue the order.
clock & contract & event & spread & depth & impact
→
eligible only if all pass
The decision needs a feedback record
Review the Forecast Against the Fill
For every attempted order, store the decision timestamp, intended and accepted quantity, state-card version, arrival price, submissions, acknowledgements, fills, cancellations, fees and final benchmark. Review quality by time bin and state without deleting missed fills or rejected orders.
- UTC and local clock labels match the source timestamp.
- The dated contract and roll state are recorded.
- Spread, depth and expected impact were captured before submission.
- Official event proximity and holiday status are explicit.
- Partial fills, cancels and rejects remain in the cost record.
- Drift beyond registered tolerances suspends the interval’s permission.
No original result is reported. This page publishes no 6Z intraday spread, depth, volume, slippage, fill-rate or performance finding; it defines a DST-, event- and roll-aware protocol, not a best hour.
Sources, methods and editorial disclosure — reviewed August 25, 2026
- CME Rulebook Chapter 259 and the current CME Rulebook index for contract and exchange context; verify current hours and notices before trading.
- CME DataMine for official historical-data product categories.
- SARB MPC announcements and Federal Reserve FOMC calendars for official event timing.
Sources were reviewed August 25, 2026. This unsponsored article separates official schedule context, measurement design and execution decisions. It reports no original result or fixed best time.