I opened the patch notes for Update 36.2 with a cup of coffee, expecting the usual list of bug fixes. Instead, I found myself staring at a map preference chart that explained why my squad always seems to drop into the same three maps. The note said map preference is measured through playtime, match count, select rate, and leave rate across all modes. Because of rounding, the regional percentages do not always add up to 100%, so I stopped trying to make the numbers total perfectly.
After seeing that chart, the rotation notes finally made sense. The developers take those regional preferences and apply them to the Fixed, Favored, and Etc. map slots. My regular squad and I immediately opened a voice call. We talked about which maps we might see more often, and we planned our week around the rotation schedule.
The timing is different depending on platform. On PC, the next rotation happens every Wednesday at 02:00 UTC. On console, it happens every Thursday at 07:00 UTC. I play on PC, but two of my squadmates are on console. That one-day gap means we usually compare notes after both rotations have gone live.
One rule shaped our expectations more than anything else: 8x8 km maps have roughly double the matchmaking probability of smaller maps. That explains why Erangel and Miramar feel so common in our lobbies. It also means a smaller map like Vikendi can feel rare even when we are in the mood for snow.
Then we reached the part about Miramar and the PUBG x aespa collaboration. For the first three weeks of Update 36.2, Miramar will be added to the Etc. map slot if it is not already in the Fixed or Favored rotations. During those first three weeks, Miramar will have double the normal matchmaking probability. I have always been mixed on Miramar. The open hills punish careless rotations, but the chance to experience the aespa world features pulled me back. My squad agreed: we would hot-drop there a few extra times.
The console side had a small warning. Due to technical issues, Deston will be temporarily removed from the map rotation on console platforms. There was no return date, but the developers promised an update when it is ready. That was a relief for my console friends who were worried the map had disappeared forever.
For ranked, the notes listed a clear set of map percentages: Erangel 25%, Miramar 25%, Taego 20%, Rondo 20%, and Vikendi 10%. I put those into a quick table for my squad so we could decide which map to practice.
| Map | Ranked Probability |
|---|---|
| Erangel | 25% |
| Miramar | 25% |
| Taego | 20% |
| Rondo | 20% |
| Vikendi | 10% |
The ranked map service is updated season by season, so these numbers may shift later. For now, our practice plan is simple. We spend roughly half of our time on Erangel and Miramar. We use Taego and Rondo for mid-game rotations, and we treat Vikendi as a nice surprise rather than a plan.
In the end, the Update 36.2 notes gave me a clearer picture of why my match history looks the way it does. I circled the Wednesday rotation timer on my calendar. I told my console squad to wait for Thursday before we made any predictions. Then I queued up, hoping for a Miramar lobby with the aespa world features, because double probability felt like an invitation I could not ignore. See you on the Battlegrounds.
Data referenced from GamesIndustry.biz helps frame why PUBG’s Update 36.2 rotation tweaks matter beyond individual player anecdotes: when a live-service game weights matchmaking by map size, regional playtime, and early-season event boosts (like Miramar’s temporary double probability for the aespa collaboration), it’s effectively using population-shaping levers to stabilize queues and concentrate engagement around headline content while still keeping variety through favored and etc. slots.