Garden Horizons // STOCK
Sign in
Restock Timer · Live

Garden Horizons Restock Timer — Next Refresh Countdown

Real-time countdown to the next 5-minute wall-clock refresh. Synced to UTC. All four shops roll together on each boundary.

Cycles today
192
192 of 288
Cadence
5:00
UTC wall-clock, all shops
Next cycle at
16:05
+tracked since launch
Live Next restock in
01:57
Cadence 05:00 Next drop 16:04 UTC
Next restock in 1m 57s
See current stock →
Upcoming Cycles
Next hour 12 cycles UTC
  1. :00
    16:00
    NOW
  2. :05
    16:05
    next
  3. :10
    16:10
    +10m
  4. :15
    16:15
    +15m
  5. :20
    16:20
    +20m
  6. :25
    16:25
    +25m
  7. :30
    16:30
    +30m
  8. :35
    16:35
    +35m
  9. :40
    16:40
    +40m
  10. :45
    16:45
    +45m
  11. :50
    16:50
    +50m
  12. :55
    16:55
    +55m
NOW Queued Cycle 0% elapsed

What is the Garden Horizons restock timer?

The restock timer is a live countdown to the next shop refresh in Grow a Garden. The game's four inventories — seeds, gear, eggs, and weather events — all rotate together on a fixed 5-minute wall-clock cycle, and this page shows you exactly how long until the next rotation.

Timing matters because rare items have short availability windows. A legendary seed or a Godly Sprinkler might only be on the shelf for five minutes before the next roll. If you know a refresh is 30 seconds away, you can be in-game and ready; if it's three minutes away, you can finish something else first.

The 5-minute cycle, explained carefully

Every Garden Horizons shop refreshes at :00 :05 :10 :15 :20 :25 of each hour — every 5 minutes, in real wall-clock time. Because it's anchored to UTC, your local timezone does not affect the schedule — the boundaries are the same wall-clock moments for every player on the planet.

The cycle is not "every 5 minutes since you logged in." It's "every 5 minutes since the top of the hour." That distinction matters. If you log in at 10:03, the next refresh is at 10:05 — only 2 minutes away, not a full 5. If you log in at 10:04:59, you catch the next refresh 1 second later.

Arithmetic: 12 refresh windows per hour × 24 hours = 288 cycles per day. That's 288 chances per day for a legendary item to surface, and roughly 1 out of every 20 of those (in community-observed averages) is when a given legendary item actually appears — which works out to about 14 appearances of any specific legendary per day, distributed with heavy variance.

Why your timing actually matters

If you're only hunting common items, timing barely matters — they appear every cycle and you'll never miss out. Timing becomes critical when you're hunting specific legendary or mythic items. A legendary seed that surfaces at :15 will be gone at :20, full stop. If you stepped away from the game for ten minutes, you missed it.

The tracker lets you plan around this: don't start another task if a refresh is in 30 seconds. Check last-seen to see which legendary items are overdue, then watch the countdown to catch them. Even our tracker has latency — we poll every 120 seconds per the upstream directive — so for the tightest hunts, be in the game, not refreshing this page.

Strategy: hunting rare items

  • Refresh the tracker page about 10 seconds before the boundary so the client-side countdown is precisely synced.
  • Have the game loaded and focused before :00 or :05 hits. A 10-second reaction time is the difference between getting the item and watching someone else announce it in chat.
  • Check last-seen before the boundary to know which items are overdue — if Godly Sprinkler has been absent two days, that's a good cycle to be ready for.
  • Don't chase single drops. Watch patterns over several cycles. If a specific item didn't appear this cycle, the next one is 5 minutes away.
  • Pair the countdown with the seed and gear shop pages — they update automatically.

Syncing tracker time with game time

Our countdown is UTC wall-clock, same as the game. In theory they tick the same second. In practice, there's always a small delta: the game server takes a moment to rotate its inventory, the community mirror we read from takes another moment to observe the rotation, and our poller follows a 120-second interval per the upstream's currentFetchInterval directive.

We don't smooth or hide this latency. The freshness indicator at the top of every stock page shows the exact second our poller last saw data. If that number is 30 seconds old right after a boundary, you know the tables might still be pre-rotation. That honesty costs nothing and means you always know how old the data is.

Frequently Asked Questions

Why does your countdown sometimes show 00:00 but my game hasn't refreshed?
Our countdown runs off the UTC wall clock, and so does the game — but the game server itself takes a small number of seconds to actually rotate, and the community mirror we read from needs another moment to observe the change. During a critical refresh, expect 0-30 seconds of lag end-to-end. The 5-minute cycle guide breaks this down.
Can you make the countdown more precise?
The countdown display ticks every second on the client. What we can't make more precise is our data freshness: we poll upstream on a 120-second cadence because that's the interval the mirror advertises. Polling faster would break protocol and risk getting rate-limited. The clock is accurate; the fetch is as fast as upstream permits.
What happens if I open the page right at :00?
You'll likely see the countdown reset to 04:59 and our stock tables still showing the previous cycle for a few seconds to a minute. That's the propagation window between the game rotating and our poller catching it. Refresh the page 30-60 seconds after the boundary and you'll see the new cycle.