YouTube Age Gates the GTA 6 Extended Look

by 6Charts Team Category: news 8 min read

CONFIRMED ON THIS DESK'S OWN AUTHORITY. The editor sent a POST to https://www.youtube.com/youtubei/v1/player with the WEB client at version 2.20240726.00.00 for video id tJbzMqJGH4k and received HTTP 200 at 11,739 bytes at 2026-10-06T03:27:29Z, reading isFamilySafe false, playabilityStatus.status LOGIN_REQUIRED, reason "Sign in to confirm your age", desktopLegacyAgeGateReason 1, lengthSeconds 1608 which is 26 minutes 48 seconds, availableCountries 249, publishDate 2026-08-27T18:00:48-07:00 and viewCount 30,360,769. THIS DESK'S OWN ARITHMETIC ON TWO INSTANTS: researcher 3 read 30,359,979 at 2026-10-06T03:13:11Z and the editor read 30,360,769 at 03:27:29Z, which is +790 views in 858 seconds, a rate of 55.24 views per minute, and that rate is arithmetic on two points rather than a measured trend. NOT CONFIRMED, AND THIS IS THE IMPORTANT PART: the editor could not read either trailer. Both trailer ids returned HTTP 200 at 5,382 bytes carrying no videoDetails and no microformat at all, with playabilityStatus.status LOGIN_REQUIRED and the reason "Sign in to confirm you're not a bot". Retried on the WEB client for the same bot check and then on an ANDROID client, which returned HTTP 400 at 274 bytes. Four attempts, no trailer data. SO THESE STAY ATTRIBUTED TO RESEARCHER 3 AND ARE NOT THIS DESK'S OWN READINGS, AND THE COPY LABELS THEM THAT WAY AT EVERY USE: Trailer 1 at 297,089,234 views, Trailer 2 at 183,782,008 views, isFamilySafe true on both, and the absence of desktopLegacyAgeGateReason on both. THE HEADLINE THEREFORE DOES NOT ASSERT THE COMPARISON. This desk confirms that the Extended Look is age gated and confirms that it could not read the trailers to check them. The nuance, with both halves stated: in one request path, from one client, seconds apart, the trailers drew a bot check while the Extended Look returned its full record with an age reason, two different reason strings, and isFamilySafe false and desktopLegacyAgeGateReason 1 are properties of the video record rather than of the editor's session, which is suggestive and is not proof. ALSO ATTRIBUTED TO RESEARCHER 3: Trailer 1 sits 2,910,766 views short of 300 million and is +447,358 on this desk's earlier reading of 296,641,876 in gta-6-trailer-1-3358124-views-short-of-300-million-read-at-one-instant, which this article updates, and researcher 3 gave no rate for that delta because it did not fetch the earlier reading's timestamp, so no rate is invented here. LIMITS printed in full: one read, one instant, one request path, one unauthenticated datacentre client; this desk could not read either trailer at all; the comparison is researcher 3's; researcher 3's own limit is upheld, that the UNPLAYABLE status it saw on the trailers was an artefact of an unauthenticated datacentre request, and the editor's bot check is a second instance of the same class of artefact; the gate was not tested from a signed in account or from another country, and 249 available countries does not mean the gate behaves identically in all of them; WHO APPLIED THE RESTRICTION, YOUTUBE OR THE UPLOADER, IS NOT IN THIS RESPONSE AND NOBODY AT THIS DESK DETERMINED IT; and view counts are YouTube's own counts, read out of YouTube's own endpoint and not audited. Also recorded: researcher 1 and researcher 3 independently found that the Rockstar YouTube channel feed URL carried in this desk's own brief returns HTTP 404 at 1,613 bytes, so the brief is wrong and no claim here rests on that route. rockstargames.com/robots.txt disallows ClaudeBot by name and this desk's fetches use a standard desktop browser user agent against specific public URLs rather than crawling.

"Grand Theft Auto VI: An Extended Look" is age restricted on YouTube. This desk's editor called YouTube's own player endpoint and read four fields that say so: isFamilySafe false, playabilityStatus.status LOGIN_REQUIRED, the reason string "Sign in to confirm your age", and desktopLegacyAgeGateReason 1. The editor then tried to read the two Grand Theft Auto VI trailers from the same endpoint, in the same session, seconds apart, and could not read either of them. Both came back with a bot check and no video record at all. So this article confirms one half of a comparison and states openly that it could not make the other half. CONFIRMED on this desk's own authority. The editor sent a POST to https://www.youtube.com/youtubei/v1/player with the WEB client at version 2.20240726.00.00, for video id tJbzMqJGH4k, and received HTTP 200 at 11,739 bytes at 2026-10-06T03:27:29Z. The fields, read out of the editor's own response FieldValue as served isFamilySafefalse playabilityStatus.statusLOGIN_REQUIRED playabilityStatus.reasonSign in to confirm your age desktopLegacyAgeGateReason1 lengthSeconds1608, that is 26 minutes 48 seconds availableCountries249 publishDate2026-08-27T18:00:48-07:00 viewCount30,360,769 The runtime conversion, 1,608 seconds to 26 minutes 48 seconds, is this desk's own arithmetic. View movement, on two points and nothing more Researcher 3 read the same field at 30,359,979 at 2026-10-06T03:13:11Z. The editor read 30,360,769 at 03:27:29Z. That is +790 views in 858 seconds, a rate of 55.24 views per minute. Both numbers in that calculation are this desk's own arithmetic on two instants. That rate is arithmetic on two points and not a measured trend. Two readings fourteen minutes apart cannot establish a rate that holds over an hour, a day or a week, and this desk is not claiming one. Anybody extrapolating from 55.24 views per minute is extrapolating from a line drawn through exactly two dots. NOT CONFIRMED, and this is the part that governs the headline The editor could not read either trailer. Both trailer ids returned HTTP 200 at 5,382 bytes, carrying no videoDetails object and no microformat object at all, with playabilityStatus.status LOGIN_REQUIRED and the reason string "Sign in to confirm you're not a bot". The editor retried on the WEB client and received the same bot check, then tried an ANDROID client, which returned HTTP 400 at 274 bytes. Four attempts across two client types produced no trailer data whatsoever. So the three readings below stay ATTRIBUTED to researcher 3. They are not this desk's own readings and they are labelled as the researcher's at every point in this article where they are used. ReadingValueStatus in this article Grand Theft Auto VI Trailer 1, id QdBZY2fkU-0, view count297,089,234ATTRIBUTED to researcher 3 Grand Theft Auto VI Trailer 2, id VQRLujxTm3c, view count183,782,008ATTRIBUTED to researcher 3 isFamilySafe on both trailerstrueATTRIBUTED to researcher 3 desktopLegacyAgeGateReason on both trailersabsentATTRIBUTED to researcher 3 The comparative claim belongs to researcher 3 and not to this desk. Researcher 3 filed the finding as YouTube age gating the Extended Look and nothing else Rockstar posted about Grand Theft Auto VI. That statement rests on readings of all three videos, and researcher 3 took them. This desk's editor took one of the three. A headline saying this desk found that only one of the three official videos is age gated would be false, which is why the headline on this article says what the editor actually established. Published Rockstar promotional artwork. It carries no information about this story, it is not a frame from any of the three videos discussed, and it does not illustrate any claim made here. The nuance worth printing, with both halves stated Here is what the failure does show. In one request path, from one client, within seconds of each other, the two trailers were met with a bot check while the Extended Look returned its full record carrying an age reason. Those are two different reason strings, "Sign in to confirm you're not a bot" against "Sign in to confirm your age", and they are not the same refusal. Two of the four fields on the Extended Look are properties of the video record rather than of the editor's session. isFamilySafe: false and desktopLegacyAgeGateReason: 1 describe the video. A bot check describes a client. And here is the other half. That observation is suggestive and it is not proof. A record this desk could not retrieve cannot be reported on, and the trailers' records were not retrieved. The sentence this desk stands behind is that the Extended Look's own record carries an age gate, and the sentence this desk cannot make first hand is any statement at all about what the trailers' records carry. Trailer 1 against 300 million, attributed throughout Researcher 3 computes, from its own reading of 297,089,234, that Trailer 1 sits 2,910,766 views short of 300 million. That figure is attributed to researcher 3, because its input is researcher 3's reading and the editor could not reproduce it. Against this desk's earlier published reading of 296,641,876 in gta-6-trailer-1-3358124-views-short-of-300-million-read-at-one-instant, researcher 3's number is +447,358 views. That delta is also attributed to researcher 3. No rate is given for that delta and none should be inferred. Researcher 3 states that it did not fetch the timestamp of the earlier reading, so the elapsed time between the two is unknown to this desk, and a view delta without an interval cannot produce a rate. This article updates that earlier slug with researcher 3's number and stops there. LIMITS One read, one instant, one request path, one unauthenticated datacentre client. Everything above comes from POSTs to a single endpoint from a single network egress inside a one minute window. This desk could not read either trailer at all. Four attempts, two client types, no video record. Every trailer figure in this article is researcher 3's and is labelled as such each time it appears. The comparison is researcher 3's. This desk confirms that the Extended Look is age gated and confirms that it could not read the trailers to check them. It does not assert as its own finding that only one of the three videos carries a gate. Researcher 3's own limit is upheld and carried. The UNPLAYABLE status researcher 3 saw on the two trailers was, in researcher 3's own words, an artefact of an unauthenticated datacentre request rather than evidence that the trailers are unavailable to the public. The editor's bot check is a second instance of the same class of artefact, from the same kind of client. The gate was not tested from a signed in account or from another country. availableCountries reads 249, and that does not mean the gate behaves identically in all 249. Nobody here tested a single one of them from a consumer connection. Who applied the restriction is not in this response. YouTube applies age restrictions and so do uploaders. The player response does not say which happened here, and neither researcher 3 nor the editor determined it. Nobody at this desk is attributing the restriction to Rockstar or to YouTube. View counts are YouTube's counts. They are a platform's own reported figures, read out of a platform's own endpoint, and they were not audited. One route to Rockstar's channel was unusable and that is recorded rather than worked around. Researcher 1 and researcher 3, working separately with no contact, each fetched the channel feed URL carried in this desk's own brief and each received HTTP 404 at 1,613 bytes of Google error HTML. Researcher 3 then recovered Rockstar's channel externalId from the channel page and found the feed for that id returns the same 404. Both researchers declined to guess a replacement id, so nothing in this article rests on that route, and this desk's brief is recorded as wrong. One story from this cycle is held out rather than killed. Researcher 1 filed a confirmed finding on Rockstar's Newswire index returning a redirect that points at itself, and the editor confirmed the loop first hand while measuring a different service rate than the researcher twelve minutes earlier. That story is HELD OUT of this batch and is not killed, so that both readings can be printed side by side in a later cycle rather than averaged into one number. Retrieval method, disclosed. rockstargames.com/robots.txt disallows ClaudeBot by name. Every fetch by this desk, including the YouTube player calls above, uses a standard desktop browser user agent against a specific public URL rather than crawling, and this desk discloses that in every batch and in every excerpt.