What GTA 6's Storefront Records Say, and a Correction We Owe

Grand Theft Auto VI's Xbox catalogue record lists a package of 344,731,648 bytes. That is 344.73 megabytes in decimal terms, or 328.76 mebibytes. Nobody sensible thinks that is the size of the game. Batch 41 said so, and gave three reasons. Two of those three reasons were wrong, and this article retracts them, because a correction is worth more than the finding it corrects. Then it sets out what actually survives a proper control run, what the rating placeholders literally say, and why two date fields in the same family of records disagree by a day without anything having changed. Correction: two of our three "placeholder" tells were worthless On 31 August we wrote that the 344,731,648-byte package is a provisioning stub rather than a shipping build, and we rested part of that on two fields in the record: MaxInstallSizeInBytes reading 0, and Version reading "0". The argument was that a real, populated package carries a version and an install size, so a record with neither has not been filled in. That argument does not survive a control, and we ran one this time. Our researcher pulled two shipped, released Xbox titles through the identical endpoint with the identical query shape: Forza Horizon 6 umbrella product 9NR1R1XWLCNB, read at 03:14:04 UTC on 1 September: real packages of 157,873,491,968 and 170,595,942,400 bytes, and both of them report MaxInstallSizeInBytes of 0 and Version of "0". Forza Horizon 5 umbrella product 9NNX1VVR3KNQ, same call: packages of 162,640,646,144, 152,655,745,024 and 159,934,996,480 bytes, again with MaxInstallSizeInBytes of 0 and Version of "0". Both of those are finished games that people have installed. Both report exactly the two values we treated as evidence of an unfinished record. Those two fields are endpoint-wide defaults and they carry no information at all. We withdraw that reasoning. It was our failure to run a control before publishing an inference, and the fix was a single extra query that we should have made the first time. A second reading of ours that needs the same treatment Earlier still, this desk made something of the fact that Grand Theft Auto VI's retail store pages return an empty Packages array. That has now failed the same way. CONFIRMED, read at 03:13:29 UTC: the two purchasable Grand Theft Auto VI records, 9P3H4968GRSM for the standard edition and 9NNZSNHLR63L for the Ultimate Edition, both return zero packages. CONFIRMED, read at 03:13:46 UTC: so does 9N431PX143P8, the Forza Horizon 6 Standard Edition purchase record, for a game that shipped. So "Packages: 0" on a retail SKU is an artefact of the record type. Purchase records point at an umbrella product; the umbrella product is where the package data lives. It is not a signal about anything, and we should not have read it as one. What actually remains anomalous, after the controls Three things, and all three survive the control run intact. The size. The Grand Theft Auto VI umbrella product 9NL3WWNZLZZN carries a single package of 344,731,648 bytes. The Forza Horizon 6 and Forza Horizon 5 umbrellas carry packages between roughly 150 and 170 gigabytes. A modern open-world console title with a 344.7-megabyte package is not carrying a shipping build. One language. Grand Theft Auto VI's package declares Languages: ["en-us"]. Forza Horizon 6's umbrella declares 44 languages. Forza Horizon 5's declares 57. One package, shared. All three Grand Theft Auto VI SKUs on that record, 0010, 0011 and 0017, point at the same single package. The controls carry several distinct packages per family. The rest of the package record, for completeness, read at 03:13:28 UTC: PackageId 3202719e-b4b4-421c-9f8f-70d1c4a7d60b, PackageFormat XVC, Architectures ["x64"], PlatformDependencies Windows.Xbox only, PackageRank 51000, FulfillmentDate null. How much weight will that carry? Less than it looks, and the hedges here are the point of the article. That 344.7 megabytes is a placeholder is an inference drawn from controls, not a Microsoft statement. Microsoft documents nothing about what this field means for an unreleased product. We are reasoning from what two shipped titles look like to what an unshipped one probably is, and that is a decent argument rather than a fact. Package metadata for an unreleased title is routinely rewritten close to launch. Whatever is in this record today tells you nothing about what will be in it in November. And this record forecasts nothing about the real install size, about certification, about whether the game has gone gold, or about launch readiness. Anybody reading a schedule out of a storefront metadata field is reading something that is not there. The only honest statement is that Microsoft has a package slot provisioned for this game and it does not currently contain a shipping build. Is GTA 6 rated yet? What the placeholders literally say No board that publishes has rated it, 79 days out, and the storefronts carry placeholder labels rather than ratings. These are the exact strings, all read at source. PlayStation Store US, concept 10000730, read at 03:11:32 UTC. The contentRating object gives authority ESRB, description "ESRB Rating Pending Mature 17+", name ESRB_RP17, an empty interactiveElements array, and a single descriptor: ESRB_MAY_CONTAIN_CONTENT_INAPPROPRIATE_FOR_CHILDREN, "May contain content inappropriate for children". PlayStation Store GB, standard edition product record, read at 03:10:44 UTC. Authority PEGI, description "PEGI Provisional 18", name PEGI_PROVISIONAL_18, with both the interactiveElements and descriptors arrays empty. xbox.com product page for 9P3H4968GRSM, read at 03:18:22 UTC. Board name ESRB, rating string "RATING PENDING LIKELY MATURE 17+", ratingAge 17, empty descriptors and interactiveDescriptions arrays, and one disclaimer: "May contain content inappropriate for children. Visit ESRB.org for rating information." The boards' own databases return nothing. ESRB's public search finds no title called Grand Theft Auto VI. PEGI's search returns zero results. USK's search returns no matching title, and the three occurrences of the string in that page's HTML were checked in context and are query echoes in the page title, the breadcrumb and the search box rather than result rows. The controls, which are what make those negatives usable. The same ESRB query shape for Grand Theft Auto V returns Grand Theft Auto V. The same PEGI query for Grand Theft Auto V returns six results. The same USK query returns multiple Grand Theft Auto V entries. All three search engines work. Grand Theft Auto VI is simply not in them. What the rating placeholders do not mean "ESRB_RP17" and "RATING PENDING LIKELY MATURE 17+" are not ratings. They are ESRB's placeholder for an unrated product expected to land at Mature. Do not write that Grand Theft Auto VI is rated 17+. "PEGI Provisional 18" is likewise provisional, issued ahead of full classification. Empty descriptor arrays are expected on placeholder ratings. That includes the empty interactive-elements arrays, which is where an "In-Game Purchases" flag would appear if one existed. There is no such flag on any storefront record today, and that is exactly what a Rating Pending entry looks like. It is not evidence about anything a game will or will not contain, and it should not be pressed into service as corroboration for any claim about monetisation. None of this is a delay story. Boards publish on a lag and typically at or near certification, and this publisher has historically certified late. Absence today is normal for a title 79 days out, and it says nothing about whether a board has issued a certificate internally. Two gaps, recorded rather than glossed: Australia's classification board was unreachable from our egress across four attempts, and Korea's GRAC could not be resolved to a Grand Theft Auto VI record because its search requires a form submission. Those are gaps in our checking, not negative findings. Why do two storefront fields disagree about the pre-order deadline? This is not a date change. Nothing has moved. It is two fields in the same family of records that describe different things and have, as far as we can tell, always read differently. The prose field. The Grand Theft Auto VI description opens, verbatim: "Purchase prior to November 20 to receive: -The Vintage Vice City Pack -One Month of GTA+". That text is on the catalogue record and on the live xbox.com page. It is timezone-unqualified. The machine-readable field. The purchase Availability.Conditions.EndDate on every purchasable Grand Theft Auto VI SKU reads 2026-11-19T04:59:59Z, which is 23:59:59 on 18 November in US Eastern time. The OriginalReleaseDate on both editions is 2026-11-19T05:00:00Z, one second later, which is midnight Eastern on 19 November. Both are correct descriptions of different things. The prose is a marketing statement about the offer. The EndDate governs the availability record for that SKU on Microsoft's storefront, and bonus content is fulfilled by Rockstar rather than by the storefront record. Both values are US-market: our query specified the US market only and we did not check others. The service note, which is the only practical advice here: take the earlier date. If you want the pre-order bonus, buy before 19 November 04:59:59 UTC and the question does not arise. For context, the release date itself is not in dispute anywhere. The PlayStation Store gives 2026-11-19T05:00:00Z in the US and 2026-11-19T00:00:00Z in Great Britain, and the string "November 19, 2026" appears seven times on Rockstar's own Grand Theft Auto VI page with no other release date anywhere on it. The negative datapoint: nothing has been edited since 2 July Filed last because it is a negative, and negatives get over-read when they lead. CONFIRMED, read between 03:08:14 and 03:09:19 UTC. Every Grand Theft Auto VI product in Microsoft's catalogue carries a LastModifiedDate inside a two-hour window on 2 July 2026. The standard edition reads 2026-07-02T17:28:40Z, the Ultimate Edition 17:17:00Z, the umbrella product 17:51:35Z, and the four associated durable products fall between 17:21 and 17:38 the same afternoon. Nothing was edited for the Extended Look premiere on 27 August, and nothing has been edited since. The control matters more than the finding. Grand Theft Auto V Enhanced on PC, product 9NXFX68ZNKK0, same publisher, carries a LastModifiedDate of 2026-08-24T06:05:50Z and a live discount window running 27 August to 2 September at $14.99 against a $29.99 list price. So Rockstar is actively editing Microsoft catalogue records right now. It is just not editing this one. The hedge. LastModifiedDate reflects publisher-side catalogue edits. Storefront presentation, banners, badges and merchandising can all change without it moving. A quiet record is the ordinary state of a pre-order product whose copy is already final. This does not mean Rockstar has done nothing; it means this specific record has not been touched. It says nothing about the PlayStation side, where no equivalent field is exposed publicly. One method note that applies to the Rockstar-hosted checks in this article: Rockstar's robots.txt disallows this desk's default crawler by name, along with several other automated agents. Those fetches were made with a standard desktop Chrome user agent so that today's readings are directly comparable with previous crawls. We record that deviation every time rather than burying it. What is and is not established Retracted: our use of MaxInstallSizeInBytes 0 and Version "0" as evidence of a placeholder package. Forza Horizon 6 and Forza Horizon 5 both report the same two values on shipped, released packages. Those tells carry no information. Retracted: our reading of "Packages: 0" on the retail SKUs as a signal. The Forza Horizon 6 purchase record returns zero packages in exactly the same way. CONFIRMED, and still anomalous: a single 344,731,648-byte package shared by all three GTA VI SKUs, declaring one language, against control umbrellas at 150 to 170 gigabytes declaring 44 and 57 languages and carrying several packages each. Inference, not a Microsoft statement: that 344.7MB is a placeholder. Microsoft documents nothing about this field pre-release, package metadata is rewritten close to launch, and none of this forecasts install size, certification, gold status or launch readiness. CONFIRMED, exact strings: ESRB_RP17 "ESRB Rating Pending Mature 17+" on PlayStation US, PEGI_PROVISIONAL_18 "PEGI Provisional 18" on PlayStation GB, and "RATING PENDING LIKELY MATURE 17+" with ratingAge 17 on xbox.com, all with empty interactive-element arrays. CONFIRMED, with three working controls: ESRB, PEGI and USK public searches return no Grand Theft Auto VI record while the same queries return Grand Theft Auto V. Explicitly not claimed: that Grand Theft Auto VI is rated 17+ or PEGI 18. Both strings are placeholders. Empty descriptor arrays are normal for a Rating Pending entry and are not evidence about the finished game's content. Explicitly not a date change: the "prior to November 20" prose and the 2026-11-19T04:59:59Z availability EndDate are two fields describing different things. Neither has moved. If you want the bonus, use the earlier one. CONFIRMED as a negative: every GTA VI Microsoft catalogue record carries a LastModifiedDate in a two-hour window on 2 July 2026, and nothing moved for the Extended Look, while the GTA V Enhanced control was edited on 24 August. Explicitly not speculated on: what any of this implies about development status. A quiet catalogue record and a placeholder package are ordinary states, not signals. Every storefront field we have checked and re-checked since June is logged on the wiki, corrections included. The rest of today's reporting is on the news desk, and the servers list and leaderboards are open for anybody who has read enough JSON for one morning.