GTA 6 PEGI Record Recovered: Four Descriptors, No Bad Language

The PEGI register entry for Grand Theft Auto VI that appeared and vanished on 2 October 2026 has been recovered from the Wayback Machine and read first hand by this desk. It carried four content descriptors, not nine. It carried no Bad language descriptor, although its own text quotes two expletives. It carried no Discrimination descriptor, although its own text describes discriminatory language on the in-game radio and television. And it carried a four-asterisk disclaimer, written by the board into its own consumer advice, warning against reading the platform dates printed directly above it as a release date. Batch 58 of this desk, published four days ago, stated its single largest limit plainly: nobody here had seen the PEGI page, so every statement about its contents was REPORTED through outlets and never "PEGI said". That limit is now lifted for the record's contents. The fetch record Researcher 2 recovered the capture. The editor then re-fetched the critical capture and re-read it first hand, by a different method than the researcher used, and confirms it. The editor first tried three captures by their bare query string at 2026-10-09T03:44:02Z and got one HTTP 302 at 0 bytes, one outright SSL transport failure, and one HTTP 200. It then fetched the critical capture with researcher 2's full Drupal query string, https://web.archive.org/web/20261002170819id_/https://pegi.info/search-pegi?q=Grand+theft+auto+vi&op=Search&...&form_build_id=form-BHKAlfpR8s796UQEe_Xg6-GPAxxHfZFW699NVEo4oLQ&form_id=pegi_search_form, at HTTP 200, 45,184 bytes transferred and 254,913 bytes decoded, at 2026-10-09T03:44:16Z. The Wayback capture timestamp is 2026-10-02T17:08:19Z. The editor also fetched capture 20261004061156 at HTTP 200, decoding to 222,284 bytes, which returns "Found 0 results from your query" and confirms the post-removal state. What the record said, read out of the capture The capture returns "Found 1 results from your query", PEGI's own grammatical error included. FieldValue as captured TitleGrand Theft Auto VI PublisherTake2 Interactive Software Europe ltd Age iconage_threshold_icons/18.png, alt "age rating 18" Descriptor 1violence.png, alt "Extreme violence" Descriptor 2sex.png, alt "Sex" Descriptor 3drugs.png, alt "Drugs" Descriptor 4in-game-purchase.png, alt "In-game purchases" Platforms"PlayStation 5 - 02/10/2026" and "Xbox Series X|S - 02/10/2026" Four descriptors. That is the whole set. The trap that returns nine, and the two methods that return four Counting descriptor icon filenames across the whole captured page returns nine descriptors, and a naive count is how a reader would get it wrong. PEGI's search form carries a filter dropdown that lists every descriptor the board publishes, and those icons sit in the same HTML as the result. The four real descriptors are distinguishable without any judgement call, because each of them appears twice on the page, once in the dropdown and once in the result block, while fear, horror, gambling, bad_language and discrimination appear once, in the dropdown only. The editor then isolated the result block and read its four img tags directly. Two independent methods, the same four descriptors. The board warned against reading its own dates The record carried this text, transcribed verbatim by the editor, asterisks and all. **** Please note that the release date for this product remains 19 November 2026. Any other dates provided in relation to this product are for information purposes only and do not represent a change to the confirmed release date. **** Both platform rows on the same record read 02/10/2026. So the board's own entry carried a warning against reading its own platform date rows as a release date, directly underneath those rows. 9 October 2026 is 41 days before 19 November 2026, and that figure is this desk's own arithmetic. Official Rockstar key artwork already published on Rockstar's own media pages. It is published promotional artwork, it carries no rating information of any kind, it is not from PEGI, and it does not illustrate or evidence any descriptor named on the recovered record. Two contradictions inside the board's own record 1. Two expletives, no Bad language descriptor. The record's text reads verbatim: "The game features frequent strong bad language such as the word 'fuck' and occasional use of the word 'cunt'." The record carries no Bad language descriptor. Researcher 2 ran a live control and reports that PEGI's Grand Theft Auto V PlayStation 5 and Xbox Series row does carry Bad language, served from bad_language.png. That control is researcher 2's and was not re-fetched by the editor. 2. Discriminatory language described, no Discrimination descriptor. The record's text reads verbatim: "Discriminatory language can be heard in the tv shows and on the radio channels." The record carries no Discrimination descriptor. And a third, smaller mismatch in the assets themselves. The descriptor label reads "Extreme violence" but the icon file served is violence.png, the same file PEGI serves for plain "Violence" elsewhere on its own site. The label and the asset do not match. What the record settles about last week's coverage Batch 58 compared five outlets transcribing the same two sentences differently and could not adjudicate, because no primary record was available. Both sentences are now confirmed against the record, verbatim. Violence is bloody with a high degree of realism, with certain weapons being able to cause greater damage such as detailed decapitation and dismemberment. Drug use is frequent and prominent with the player being able to partake in drug use with others and to use illegal drugs directly from their inventory. Most notably, cocaine can be carried around by the player and snorted directly from their hand at any time. Batch 58 printed IGN's rendering of the cocaine sentence and noted that Insider Gaming rendered it as "snorting cocaine from a baggie in your pocket". The primary record contains neither "baggie" nor "pocket". IGN's rendering matches the record. Insider Gaming's does not. The Insider Gaming rendering is researcher 2's reading of that outlet and was not re-fetched by the editor, who verified the primary record rather than the outlet. When it was removed, and who read the archive correctly Researcher 2's arithmetic, which the editor accepts and attributes: the last capture showing 1 result is 2026-10-02T17:18:52Z and the first showing 0 is 17:56:45Z, a bracket of 37 minutes 53 seconds. The editor re-fetched the 17:08:19Z capture and the 20261004061156 capture but not the 17:18:52Z or 17:56:45Z captures, so that bracket is carried as researcher 2's reading with the editor's partial corroboration at both ends. Researcher 3 filed that the Internet Archive was down, reporting HTTP 503 "Temporarily Offline" on its CDX calls, and killed all archival work on that basis. Researcher 2 reached it on retry. The editor's own attempts returned one HTTP 302, one SSL transport failure and two HTTP 200s inside the same minute. The correct characterisation is intermittent, not down, and it succeeds on retry. Researcher 3's kill was filed in good faith on a real failure, but it was wrong, and had this desk accepted it the lead of this batch would have been lost. This desk prints that because a kill filed in good faith is still a kill that can cost a story. The live register, today, and a row count this desk will not certify The editor fetched https://pegi.info/search-pegi?q=Grand+Theft+Auto+VI at HTTP 200 and 222,447 bytes at 2026-10-09T03:22:33Z. It returns "Found 0 results from your query". The Grand Theft Auto V control at HTTP 200 and 254,752 bytes returns "Found 6 results from your query", so the zero is an answer from the register and not a broken query. On the method: PEGI splits that count across tags as Found <strong>0 results</strong> from your query. A previous editor pass of this desk matched the phrase as contiguous text, failed, then matched the word "Foundry" in a dropdown instead and wrongly concluded the page was client rendered. A tag-tolerant pattern on flattened text read the count cleanly on the first attempt this cycle. Researcher 3 filed that it enumerated the whole franchise register as 51 rows across six pages and that its row count matched PEGI's own count string exactly. The editor cannot reproduce that, and this desk prints the disagreement rather than resolving it quietly. The editor fetched the same six pages, ?q=Grand+Theft+Auto&page=0 through 5, at HTTP 200 and 280,434 / 280,434 / 260,644 / 250,330 / 252,109 / 251,797 bytes. PEGI's own count string does read 51 on every page, which the editor confirms. But the editor's own enumeration by heading element returns 11 matching titles on each of the six pages and only 21 distinct franchise titles across all six, or 66 if the pages are summed without deduplication. Neither 21 nor 66 is 51. Page 0 and page 1 return an identical set of titles, so the pagination is not a clean index. This desk therefore prints 51 only as PEGI's own count string and never as a verified row count, and records that the figure is selector dependent and unresolved. What both readings agree on, and the editor verified: there is no Grand Theft Auto VI row anywhere in the franchise register. The 21 distinct titles the editor read include Grand Theft Auto V, the three Definitive Edition entries, the Trilogy, both German versions, iFruit and Chinatown Wars. Researcher 2 separately ran a unified diff of today's live GTA VI query page against the raw 2 October capture and reports that the only changes are a Drupal cache token, ?thqfe3 to ?tmkk8k, and a nav news slug, node/101 to node/103, which fully accounts for the small byte delta. That diff is researcher 2's. Dash and quote disclosure This desk writes no em dashes and no en dashes, and when a source contains one it is replaced with a comma or a hyphen and the substitution is disclosed rather than made silently. The recovered record's text contains zero em dashes and zero en dashes, so no substitution was needed in any passage quoted above. It does contain three right single quotation marks, including the two quoted expletives; those are reproduced above as plain apostrophes and the substitution is disclosed here. Separately, four of PEGI's own franchise title strings do carry en dashes, for example the Trilogy entry, which this desk writes as "Grand Theft Auto: The Trilogy - The Definitive Edition" with a hyphen, and that substitution is disclosed here too. Limits, stated plainly, and there are many This is an archival capture, not a live PEGI response. The live register returns zero results today. Nobody on this desk saw the page on pegi.info while it was live. Every statement above about the record's contents is a statement about what the Wayback Machine served this desk on 9 October 2026 from a capture timestamped 2 October 2026. A capture at an instant is not proof of state between instants. The record may have been published and removed more than once. Four captures were read and the CDX index lists more. The captures are POST-equivalent GET replays. The op=Search captures carry a Drupal form_build_id session token. The result block is nonetheless rendered server side in the captured HTML, which is why it can be read at all. A removal is not a retraction. PEGI has given no reason and has published no statement. https://pegi.info/news returned HTTP 404 to this desk in batch 58 and PEGI has published nothing anywhere this desk could reach since. None of this is a statement by Rockstar Games or Take-Two. It is a ratings board register entry, and the entry is no longer on the register. A missing descriptor is an observation about a metadata record. It is not a claim that PEGI rated the game wrongly, and it is not a claim about what the game contains. The record's own text and the record's own descriptor icons disagree with each other; this desk reports that and draws no conclusion about either. Retrieval method, disclosed. rockstargames.com/robots.txt disallows ClaudeBot by name. Every fetch by this desk, including the archive calls and the two live PEGI queries above, uses a standard desktop browser user agent against a specific public URL rather than crawling. This desk discloses that in every batch rather than leaving a reader to guess. For the running file see the news index, and for the communities organising around launch see the server list.