Trading hours
Trading hours control when a Radar rule is active. Set the hours and days (in UTC) when you want an agent on duty. Outside those times, the rule doesn't match.
Think of it like TradingView's trading sessions — but instead of marking chart backgrounds, Radar actually trades during those hours.
Quick start: London session only
Here's a rule that's only active during London cash hours:
| Field | Value |
|---|---|
| Agent | London Scalper |
| Hours | 08:00–16:00 UTC |
| Days | Monday–Friday |
| Regime | (any) |
Your agent goes on duty at 08:00 UTC on weekdays and goes off duty at 16:00 UTC. Outside those times, this rule doesn't match.
How trading hours work
Everything is in UTC
All Radar hours are in UTC (Coordinated Universal Time). You select hours and days in UTC, and Radar checks the current UTC time against your selection.
| Your local time zone | Offset from UTC |
|---|---|
| London (winter) | UTC+0 |
| London (summer/BST) | UTC+1 |
| New York (winter/EST) | UTC-5 |
| New York (summer/EDT) | UTC-4 |
| Tokyo | UTC+9 (no DST) |
| Sydney (winter) | UTC+10 |
| Sydney (summer/AEDT) | UTC+11 |
Tip: Search "current UTC time" to see what hour it is in UTC right now.
Membership, not ranges
Trading hours work by membership — is the current UTC hour in your selected set?
| If you select hours... | The rule matches when... |
|---|---|
| 08, 09, 10, 11, 12, 13, 14, 15 | Current UTC hour is any of those (08:00–15:59 UTC) |
| 22, 23, 0, 1, 2 | Current UTC hour is any of those (overnight wrap) |
| 13 only | Current UTC hour is 13 (13:00–13:59 UTC) |
You can select non-consecutive hours. Want to trade only at market opens? Select just 08 and 13.
Days work the same way
| If you select days... | The rule matches when... |
|---|---|
| Monday–Friday | Current UTC day is Mon, Tue, Wed, Thu, or Fri |
| Saturday, Sunday | Current UTC day is weekend (crypto markets) |
| Monday, Wednesday, Friday | Current UTC day is one of those |
Session presets
BattleGrid provides presets for common trading sessions. These convert to UTC hours when you save.
Available presets
| Preset | Hours (UTC) | Notes |
|---|---|---|
| New York Open | 13:00–14:00 UTC | NYSE opening hour |
| New York Cash | 13:30–20:00 UTC | NYSE regular trading hours |
| London Open | 08:00–09:00 UTC | LSE opening hour |
| London Cash | 08:00–16:30 UTC | LSE regular trading hours |
| Tokyo Open | 00:00–01:00 UTC | TSE opening hour |
| Tokyo Cash | 00:00–06:00 UTC | TSE regular trading hours |
| London-New York Overlap | 13:00–16:00 UTC | Highest forex liquidity |
Important: Presets don't follow daylight saving
When you select a preset, it converts to fixed UTC hours at save time. If daylight saving changes later, your hours stay the same.
Example: You select "New York Cash" in January (EST, UTC-5). It saves as 13:30–20:00 UTC. In July (EDT, UTC-4), it's still 13:30–20:00 UTC — which is now 09:30–16:00 local New York time.
If you need DST-adjusted hours, manually update your rule twice a year, or use the equivalent UTC hours for the current season.
Settings
| Setting | What it means |
|---|---|
| Hours | Which UTC hours (0–23) the rule is active. Select one or more. |
| Days | Which UTC days (Sunday–Saturday) the rule is active. Select one or more. |
Limits
| Constraint | Rule |
|---|---|
| All 24 hours + all 7 days | Rejected — this always matches. Use the default agent (on duty when no rule matches) or an always-on rule (on duty all the time, behind your other rules) instead. |
| Empty hours or days | Rejected — you must select at least one of each. |
Worked example: New York and London overlap
You want to trade only during the highest-liquidity period when both London and New York are open.
Setup
| Field | Value |
|---|---|
| Agent | Liquidity Hunter |
| Hours | 13, 14, 15 (13:00–15:59 UTC) |
| Days | Monday, Tuesday, Wednesday, Thursday, Friday |
| Regime | (any) |
What happens
| Time (UTC) | Day | Rule matches? | Why |
|---|---|---|---|
| 12:30 UTC | Monday | No | Hour 12 not selected |
| 13:15 UTC | Monday | Yes | Hour 13 is selected, Monday is selected |
| 15:45 UTC | Monday | Yes | Hour 15 is selected |
| 16:00 UTC | Monday | No | Hour 16 not selected |
| 14:00 UTC | Saturday | No | Saturday not selected |
Worked example: Overnight session
You want to trade during Asian hours, which cross midnight UTC.
Setup
| Field | Value |
|---|---|
| Agent | Asia Session Trader |
| Hours | 22, 23, 0, 1, 2, 3, 4, 5, 6 (22:00–06:59 UTC) |
| Days | Monday, Tuesday, Wednesday, Thursday, Friday |
What happens
| Time (UTC) | Rule matches? | Why |
|---|---|---|
| 21:00 UTC Monday | No | Hour 21 not selected |
| 23:30 UTC Monday | Yes | Hour 23 is selected |
| 00:15 UTC Tuesday | Yes | Hour 0 is selected (it's now Tuesday) |
| 05:45 UTC Tuesday | Yes | Hour 5 is selected |
| 07:00 UTC Tuesday | No | Hour 7 not selected |
Note: There's no special "overnight" mode. Just select the hours you want, including hours that cross midnight.
Good to know
-
Hours and days must both match. If you select hours 08–16 and days Mon–Fri, hour 10 on Saturday doesn't match.
-
Check your UTC conversion. The most common mistake is getting the UTC offset wrong. Double-check before saving.
-
Consider daylight saving. If you care about local market hours, update your rules when clocks change (or accept the shift).
-
Crypto trades 24/7. Unlike stocks, crypto markets don't close. You can trade any hour, any day.
-
Gaps are fine. Want to trade only at 08:00 and 13:00 UTC? Just select those two hours.
Advanced: How hours interact with regimes
A rule can have both hours and a regime condition. Both must match for the rule to activate.
| Hours match? | Regime match? | Rule matches? |
|---|---|---|
| Yes | Yes | ✓ Yes |
| Yes | No | No |
| No | Yes | No |
| No | No | No |
Example: A rule requires a Bull trend during London hours (08:00–16:00 UTC). At 09:00 UTC in a Bear range, the rule doesn't match (regime condition fails). At 09:00 UTC in a Bull trend, the rule matches.
Advanced: What "outside hours" means
When the current UTC time is outside your selected hours:
- This rule doesn't match — its agent isn't on duty from this rule
- Other rules are still checked — another rule might match
- Default agent may activate — if no rules match and you have a default
- No "cold" state — hours alone never cause "No regime reading yet"
The coin is only Idle if no rules match AND there's no default agent.