The short answer
The short answer
The current build-time record uses a reset at 17:00 UTC, which is 01:00 the next day in China Standard Time, 02:00 in Japan and Korea, 19:00 in Central European Summer Time, 18:00 in British Summer Time, 13:00 in US Eastern Daylight Time, and 10:00 in US Pacific Daylight Time. Check the dated record below because the source timestamp and daylight-saving conversion matter. The map sequence is also read from build data, not guessed from a permanent calendar.
Today's PEAK map and next reset
The live-looking answer belongs in a static HTML block so search engines and readers can see it without running browser JavaScript. The card below is generated from the same build-time data used by the main map page. It includes the date, sequence, reset status, source, and media when those fields are verified.
If a source has not been checked for the build date, the card stays pending. That is an important part of this PEAK map rotation schedule: a blank or pending result is more accurate than a made-up seed, a copied screenshot, or a stale reset countdown.
Build-time daily map
Today's PEAK map
- Biome
- Shore, Tropics, Mesa, Gloom, Citadel
- Record date
- Next reset
- 17:00 UTC (daily)
This snapshot is written during the build. Confirm the route in PEAK after a reset or update. Check today's live map
PEAK reset times in UTC and local time
The site treats the reset timestamp as data, not as a universal promise. The current verified record is 17:00 UTC, and the conversion table below makes the same instant easier to use across common player time zones. A local clock may show a different calendar date, especially in Asia-Pacific zones where the reset arrives after midnight.
Daylight-saving rules can change local display for Europe and North America. UTC is the stable comparison point. When your clock differs from the table, compare the ISO timestamp in the daily map source and your own time-zone setting rather than assuming the route is late.
| Reference zone | Reset time | Reading note |
|---|---|---|
| UTC | 17:00 | Stable source-time reference. |
| China Standard Time (UTC+8) | 01:00 next day | The current record reaches China after midnight. |
| Japan / Korea (UTC+9) | 02:00 next day | Japan and Korea share this offset. |
| Central Europe (summer UTC+2) | 19:00 | Winter local time is one hour earlier. |
| United Kingdom (summer UTC+1) | 18:00 | Winter local time is one hour earlier. |
| US Eastern (daylight UTC-4) | 13:00 | Standard time is one hour earlier. |
| US Pacific (daylight UTC-7) | 10:00 | Standard time is one hour earlier. |
Does PEAK have a fixed rotation schedule?
Do not infer a permanent weekly sequence from a handful of daily records. A source can prove what it reported on a particular date, while a patch can introduce a biome, remove a route context, or alter how a rotation is presented. The responsible answer is that the schedule follows the current game and maintained source; any fixed cycle must be confirmed by official documentation or a longer, verified record.
This is why the page separates reset time from rotation pattern. A reset can happen at a recurring observed time while the sequence changes. Conversely, a content update can change the available route context without changing the clock. Keep both facts dated and check the official update feed before treating an older pattern as current.
- Clock Use the verified ISO reset timestamp and convert it to your time zone.
- Sequence Read the dated biome or route record; do not fill missing days by interpolation.
- Patch context Check official notes when a new biome or route announcement appears.
- Session check Confirm the route in-game after the reset and after a major update.
Recent verified PEAK rotation records
The table below is maintained as a dated record rather than a prediction engine. Each row is added only when the daily fetcher has a matching build date, a safe source URL, and enough location fields to identify the route context. A future build can add the next row without rewriting the explanatory sections.
Use recent rows to compare observations, not to assume that the next day will repeat the previous order. The record is especially useful for checking whether a route note belongs to the current version and for spotting when a patch has changed the available context.
| Date | Map or sequence | Biome context | Source |
|---|---|---|---|
| Shore → Tropics → Mesa → Gloom → Citadel | Shore, Tropics, Mesa, Gloom, Citadel | PEAK Map Today | |
| Shore → Tropics → Mesa → Gloom → Citadel | Shore, Tropics, Mesa, Gloom, Citadel | PEAK Map Today | |
| Shore → Tropics → Alpine → Gloom → Citadel | Shore, Tropics, Alpine, Gloom, Citadel | PEAK Map Today | |
| Shore → Roots → Alpine → Gloom → Citadel | Shore, Roots, Alpine, Gloom, Citadel | PEAK Map Today | |
| Shore -> Roots -> Mesa -> Gloom -> Citadel | Shore, Roots, Mesa, Gloom, Citadel | PEAK Map Today | |
| Shore -> Tropics -> Alpine -> Gloom -> Citadel | Shore, Tropics, Alpine, Gloom, Citadel | PEAK Map Today |
Rows are appended only when the build source has a matching date and enough location fields to identify the route context. They describe observations, not a guaranteed future cycle. Learning the biome names? Start with the biomes list, then compare these dated records.
How patch notes fit into the schedule
A reset schedule tells you when to check; patch notes tell you what may have changed around that check. If the route looks different after an update, open the patch notes and compare the post date with the map record. Keep the two sources separate: a patch headline does not substitute for the current route, and a daily route does not explain every mechanic change.
For a practical pre-climb routine, check the current date, read the reset timestamp in your own time zone, open the route, and agree on the first decision with your group. This turns the PEAK map rotation schedule into a small habit that survives changes to the map pool.
- Before reset Finish the current run and note the version if a route observation matters.
- At reset Refresh the dated map entry and compare the ISO timestamp with your local clock.
- After an update Read official patch notes before reusing a route or equipment recommendation.
Quick answers
PEAK map rotation schedule FAQ
How often does the PEAK map change?
The site records a daily build-time entry when it can be verified, but the available route sequence and cadence should be confirmed from the current game and source. Do not turn one observed sequence into a permanent cycle.
What time does the PEAK map reset?
The current verified record uses 17:00 UTC. That is 01:00 the next day in China Standard Time, 02:00 in Japan and Korea, 19:00 CEST, 18:00 BST, 13:00 US Eastern Daylight Time, and 10:00 US Pacific Daylight Time. Recheck the dated ISO timestamp after updates or daylight-saving changes.
Where is today's PEAK map?
Open today's PEAK map for the current source-backed entry. The main map page remains the canonical daily answer and shows pending status when no dated location data is verified.
Does PEAK use a fixed rotation cycle?
A fixed cycle should not be assumed without current official confirmation. The schedule page preserves dated observations and explains how patches can change the route context.
Why does my reset time look different?
Your local time zone or daylight-saving offset may differ from the reference. Compare your clock with the ISO reset timestamp in UTC and then confirm the active route in-game.
Where can I find PEAK patch notes?
Use the official Steam news feed or this site's patch notes page, which records official titles and dates before adding cautious route context.
Sources and limits
A dated schedule, not a guessed calendar
Reset and route values are injected from the maintained data/today-map.json record. Recent rows come from the verified map history file. Official Steam news provides update context. The game session remains the final source when a reset, route, or patch does not match an older record.