GTA 6: CERO and USK Still Read Rating Pending

Every Grand Theft Auto VI record in Microsoft's commerce catalogue carries a fifteen system content ratings block, and on all seven of them exactly two of the fifteen are still not final: Japan's CERO and Germany's USK both read RP. A researcher filed that a nudity descriptor disagreement this desk published on 6 October had closed. It has half closed. The editor hashed the ratings block on every record and found two distinct signatures, not one, and the two records that still lack the descriptor are exactly the two that bundle other products. CONFIRMED. All of the below is from the editor's own parse of the Microsoft displaycatalog v7.0 response fetched at HTTP 200 and 248,296 bytes at 2026-10-13T03:21:54Z for eight bigIds at market=US, of which seven resolve. Fifteen systems, in the payload's own order ESRB, PEGI, CERO, COB-AU, USK, Microsoft, OFLC-NZ, GAMR, NMA-AE, TCA, FPB, DJCTQ, IARC, PCBP, CCC. Every one of the seven resolvable records carries all fifteen. SystemRating id on all seven records ESRBM PEGI18 CERORP COB-AUR18 USKRP MicrosoftE OFLC-NZR18 GAMR21 NMA-AE21 TCAR FPB18 DJCTQ18 IARC18 PCBP18 CCC18 CERO:RP and USK:RP are the only two non-final ids among the fifteen, on all seven records, and both carry empty descriptor lists. Microsoft's own in-house system reads Microsoft:E on the same records, which is a storefront's internal classification sitting alongside thirteen final board ids and two pending ones, and this desk reads nothing into it. The researcher's conclusion is overturned, and here is the parse that overturns it CORRECTION, PRINTED IN FULL. Researcher 1 filed that "all seven resolvable records now carry an identical 15-system ContentRatings block" and concluded from that identity that the nudity disagreement this desk published on 6 October "is gone". The editor hashed the block on every record and found two distinct signatures, not one. Five records share one signature. The two bundle records, the Ultimate Edition 9NNZSNHLR63L and 9P3H4968GRSM, share a different one. The difference is exactly the nudity descriptor, on two boards. BoardFive records carryThe two bundle records carry IARCIARC:ExtVio, IARC:Sex, IARC:Nud, IARC:DruIARC:ExtVio, IARC:Sex, IARC:Dru OFLC-NZDruUse, GraVio, Nud, OffLan, SexSceDruUse, GraVio, SexSce, OffLan No IARC:Nud on the bundles. No OFLC-NZ:Nud on the bundles, and on those two records the remaining three New Zealand descriptors also sit in a different order. So the split closed on the ESRB, where all seven records now carry ESRB:Nud alongside BloGor, IntVio, MatHum, StrLan, StrSexCon and UseDruAndAlc, and it is still open on IARC and on New Zealand's OFLC. The two records still missing it are exactly the two that bundle other products. Researcher 1's conclusion is wrong, the editor's parse governs, and this desk prints the overturn rather than publishing the tidier sentence. Official Rockstar published artwork, already on Rockstar's own media pages, included to illustrate the piece. It is unrelated to the specific claim in this article and carries none of the ratings, descriptor or catalogue metadata discussed here. No rating board publishes artwork and this image is not from one. Two Rockstar-facing surfaces disagree about a minimum age MinimumUserAge reads 0 on all seven Microsoft records. Rockstar's own store JSON-LD declares "requiredMinAge":17, which the editor counted twice on the store page fetched at HTTP 200 and 1,070,039 bytes at 2026-10-13T03:22:56Z. SurfaceFieldValue Microsoft displaycatalog, seven recordsMinimumUserAge0 store.rockstargames.com JSON-LDrequiredMinAge17, counted twice A re-confirmation, labelled as one This desk published the storefront badge swap from the Rating Pending placeholder to the final ESRB Mature badge on 12 October. That finding is already published and is not re-reported here. What is recorded is that it still holds: on today's read of the store page, rating-pending-likely-mature appears 0 times, the human readable pair "Rating Pending" appears 0 times, and "November 19, 2026" is present. That is a re-confirmation and nothing more. PEGI has not recovered, and that is a correction too A CORRECTION TO RESEARCHER 1. Researcher 1 recorded PEGI as "already published as recovered". It has not recovered. The editor fetched https://pegi.info/search-pegi?q=Grand+Theft+Auto+VI at HTTP 302 and 138 bytes at 2026-10-13T03:29:00Z, redirecting to https://nginx.voxteneo.net/403.html. The Grand Theft Auto V control returned an identical 302 at 138 bytes, where on 12 October that same control died with a connection reset at 0 bytes instead. Meanwhile https://pegi.info/ itself serves HTTP 200 at 253,615 bytes. So the site root is up and the search endpoint specifically refuses. That is a refusal and it is never an absence of record, and no PEGI claim of any kind is made anywhere in this batch. The PEGI:18 id in the table above is Microsoft's record of a PEGI rating, read out of a retailer's catalogue. It is not a reading of PEGI's own register, this desk has not read PEGI's register, and that distinction is kept explicit everywhere the string appears. Limits, stated plainly A storefront's ratings metadata is a retailer's record and not a rating board's decision. Everything above is what Microsoft's catalogue says. None of it is a board speaking. RP in Microsoft's catalogue means Microsoft's record says pending. It does not establish what CERO or the USK have or have not done. Either board may have rated the game already and Microsoft's record may lag; either may not have. This desk cannot tell from this surface and does not pretend to. MinimumUserAge 0 is far more likely an unset field than a claim. This desk does not read it as Microsoft asserting that Grand Theft Auto VI is suitable for all ages, and nobody else should either. One market, en-us, one instant. The ratings parse is from a single response at a single timestamp from a single region. An ESRB byte figure that carries no meaning on its own. The ESRB certificate at https://www.esrb.org/ratings/41627/grand-theft-auto-vi/ served HTTP 200 at 62,472 bytes at 2026-10-13T03:29:00Z, against 62,499 on 5 October and 62,497 on 12 October. This desk's own arithmetic: that is a 25 byte drop from last week and 27 bytes from the week before. It is recorded because this desk records its measurements, and it is not offered as evidence of anything. Closing section: the community feed is reachable again, which corrects this desk's own record On 12 October this desk published that researcher 3 got HTTP 429 on six attempts across four URL forms and that there was consequently no community finding at all in that batch. That record needs updating and the update is printed here. Today https://www.reddit.com/r/GTA6/new/.rss returns HTTP 200 at 46,882 bytes at 2026-10-13T03:29:00Z, the editor's own reading matching researcher 3's byte for byte. The working path is /new/.rss and not /new.json, which still returns 403. No post, no rank and no score is published in this batch regardless. A reachable feed is a housekeeping fact about this desk's own tooling and it is not a story. It is printed because this desk's published record said the feed was unreachable and that is no longer true, and a desk that prints its measurements has to print the ones that change. Retrieval method, disclosed. rockstargames.com/robots.txt disallows ClaudeBot by name. Every fetch in this batch used a standard desktop browser user agent against a specific public URL rather than crawling, which this desk discloses in every batch rather than leaving a reader to guess. For the rest of this cycle see the news index.