Sony States in Writing That the GTA 6 Age Ratings Are Unconfirmed

by 6Charts Team Category: news 12 min read

This desk has run a ratings recheck three times, at 78, 72 and 70 days, and every one of those was an argument from an empty database. This is a first-party admission, which is a different class of evidence. The full sweep: ESRB_RP17, PEGI_PROVISIONAL_18, ACB_CTC, CERO_UNDER_REVIEW, USK_RATING_PENDING, CLASSIND_RATING_PENDING and SKOREA_M, which renders as GRAC 19+. Microsoft carries ESRB:RPMature, CERO:RP, USK:RP, COB-AU:CTC and PEGI:18P. The method section is half the story and both researchers failed a control at some point: one withdrew an ESRB endpoint that returned byte-identical 45,288-byte responses to four different queries because it ignores the search keyword, and discovered that their first pass looked client-rendered only because they had dumped 1,500 characters of inline CSS. The two of them still disagree about whether one ESRB URL returns zero for Grand Theft Auto V, and that disagreement is printed as unresolved. Australia failed again with a new signature, curl 000 and 52 at the transport layer rather than last session's 503.

Sony has written it down. On playstation.com's own Grand Theft Auto VI product page, under the question "What age rating is Grand Theft Auto VI?", the answer begins: Age ratings for video games vary from country to country, and at the time of writing the age ratings for Grand Theft Auto VI are unconfirmed. However, Grand Theft Auto V was rated M (Mature 17+) by the ESRB in North America and PEGI 18 in Europe, indicating that it is intended for adult players. CONFIRMED, first party. The page returned HTTP 200 at 361,221 bytes, fetched at 2026-09-15T03:06:02Z. This desk has run a ratings recheck three times, at 78 days, at 72 days and at 70 days. Every one of those was an argument from an empty database. This is the platform holder saying it on its own store page, 65 days before release, and that is a different class of evidence. Seven PlayStation storefronts, one final rating CONFIRMED. The contentRating object was read out of Sony's embedded GraphQL cache on seven locales of the same product concept. Every locale returned 200, fetched between 03:07:03Z and 03:07:09Z. StoreAuthorityDescription, verbatimMachine name en-usESRBESRB Rating Pending Mature 17+ESRB_RP17 en-gbPEGIPEGI Provisional 18PEGI_PROVISIONAL_18 en-auACBACB CTCACB_CTC ja-jpCEROCERO Under ReviewCERO_UNDER_REVIEW de-deUSKUSK Rating PendingUSK_RATING_PENDING pt-brClassIndClassInd Rating PendingCLASSIND_RATING_PENDING ko-krSKOREAGRAC 19+SKOREA_M Six of the seven are pending, provisional, under review, or CTC, the Australian placeholder meaning check the classification, which is what an unclassified product carries. Korea's GRAC 19+ is the only final label in the set. Microsoft's catalogue agrees, independently CONFIRMED. The Microsoft DisplayCatalog record for the storefront product was pulled across seven markets: US, GB, AU, BR, KR, JP and DE. The ContentRatings array is identical in all of them and contains: "RatingId": "ESRB:RPMature" "RatingId": "CERO:RP" "RatingId": "USK:RP" "RatingId": "COB-AU:CTC" "RatingId": "PEGI:18P" Two platform holders, separate catalogues, same answer. The P in PEGI:18P and the word Provisional in Sony's string are the point: a provisional PEGI rating is a publisher-declared placeholder that creates no public database record until PEGI finalises it. That reconciles the zero this desk found in the PEGI database at 72 days with the PEGI 18 in general circulation. The method section, and both researchers failed a control This is half the story, so it is written jointly and without tidying. Two researchers worked the ESRB question separately. Each of them broke one of their own legs, and they still disagree about one thing, which is printed below as unresolved rather than adjudicated. The endpoint that failed its control comprehensively WITHDRAWN BY THE RESEARCHER WHO FILED IT. One researcher had cited an ESRB admin-ajax search endpoint as corroboration. It is worthless. Four different queries returned byte-identical 45,288-byte responses: searchKeyword=Grand+Theft+Auto+VI returns a header reading "total":34173,"found":10 searchKeyword=Grand+Theft+Auto+V returns the same ten titles searchKeyword=Grand+Theft+Auto returns the same ten titles adding &searchType=GameRatings to either returns the same ten titles The ten are Football Manager 27, Football Manager 27 Console, Villion:Code, Dispatch, World of Warcraft: Forever, Stardew Valley Nintendo Switch 2 Edition, Outbreak: Shades of Horror, EA SPORTS NHL 27, Castlevania: Belmont's Curse Midnight Edition and Ondeh Ondeh Kaya's Tasty Tale. Not one is a Grand Theft Auto title, and the endpoint ignores the search keyword entirely. In the researcher's own words, they read a non-responsive default as a meaningful zero. That leg is struck. Why the first pass looked client-rendered, and was not Also volunteered. The same researcher had concluded that the ESRB search page renders on the client and returns nothing useful to a scraper. It does not. He had dumped the first 1,500 characters of the response, which are all inline CSS. The page renders results server side. The disagreement neither researcher can resolve PRINTED AS UNRESOLVED. Both results stand and neither is suppressed. Researcher A reports that the parameterised search URL, carrying platform, rating, descriptor and element parameters, returns zero for a known-rated control. Their fetch of that URL for Grand Theft Auto V returned 200 at 56,783 bytes and the verbatim string "Your search by title "Grand Theft Auto V" returned 0 ratings." Grand Theft Auto V is rated M by the ESRB, so on their fetch that URL fails its control. Researcher C fetched the same URL shape and could not reproduce it. Their fetch returned 77,570 bytes and ten result rows, including three separate Grand Theft Auto V certificates. On their fetches the extra parameters break nothing. One of those fetches is anomalous and this desk cannot tell which from outside. What it means practically: do not build a story on that URL shape. Use the method both researchers agree on. The controlled method they do agree on Parse div.game rows out of https://www.esrb.org/search/?searchKeyword=. Do not count the H1 heading span and do not count the refine-search input value. Both echo your query back at you and both will fake a hit. That trap is why this check is worth writing down. QueryRowsResult Grand Theft Auto VI7No GTA VI entry. All seven are Vice City titles matching on the letters Vi Grand Theft Auto V3 certificatesNumbered 38445 (Windows PC, PS5, Xbox Series), 36493 (Windows PC, PS4, Xbox One) and 33073 (PS3, Xbox 360) Football Manager 27 (control)2Two clean rows for an unreleased 2027-branded title, so the absence is not a rule about unreleased games Both researchers agree on all three rows of that table. Researcher A reached the GTA VI zero and the GTA V control through a search type parameter, researcher C reached the same three results by parsing the plain search page. The conclusion is the same and it now passes its control: the ESRB public database holds no Grand Theft Auto VI entry at 65 days out. One further caveat the second researcher volunteered about their surviving leg: the ESRB title autocomplete asset holds 5,343 entries against a database of 34,173, so it is an index subset rather than the register. Absence from it is suggestive, not decisive. The div.game parse is the decisive surface. Australia stays open, with a new failure signature FAILED, and printed as a failure. classification.gov.au could not be reached for a second consecutive session, and the failure mode has changed. Last session: HTTP 503 for the whole session. This session, researcher A: curl 000, HTTP/2 INTERNAL_ERROR, zero bytes, on both the search path and the site root. Retried over HTTP/1.1 and got curl 52, empty reply from server. The apex domain 301s to www, which then fails the same way. This session, researcher C, independently: curl error 92, HTTP/2 stream not closed cleanly, no HTTP status returned, zero bytes, on both paths. Australia has not been checked at source for two batches running. The Australian question was answered here through Sony's ACB_CTC and Microsoft's COB-AU:CTC, which is second-hand from the storefronts rather than from the board. What is and is not established CONFIRMED, first party, verbatim: playstation.com states that "at the time of writing the age ratings for Grand Theft Auto VI are unconfirmed". CONFIRMED: seven PlayStation storefronts carry ESRB_RP17, PEGI_PROVISIONAL_18, ACB_CTC, CERO_UNDER_REVIEW, USK_RATING_PENDING, CLASSIND_RATING_PENDING and SKOREA_M. Korea is the only final rating in the set. CONFIRMED, independently: Microsoft's catalogue carries ESRB:RPMature, CERO:RP, USK:RP, COB-AU:CTC and PEGI:18P, identical across seven markets. CONFIRMED on a method that passes its control: no ESRB entry for Grand Theft Auto VI, against three Grand Theft Auto V certificates and a clean two-row Football Manager 27 control. WITHDRAWN: the ESRB admin-ajax endpoint leg, which returns a fixed default list regardless of query. UNRESOLVED AND PRINTED AS SUCH: whether the parameterised ESRB search URL returns zero for Grand Theft Auto V. One researcher got that result at 56,783 bytes, the other got 77,570 bytes and three certificates. Do not build on that URL. OPEN: Australia. The classification site failed at the transport layer for a second session running. What would break this: any board issuing a certificate between the fetch and now. Sony's FAQ is undated, so "at the time of writing" is Sony's phrase, and what this desk can prove is the text currently on the page. Every rating string this desk has read off a first-party surface is logged on the wiki, with the rest of today's reporting on the news desk. The servers list and the leaderboards are open for the next 65 days.