Channel
@gtabrowser
On this record: Topic · Previous handles · Growth · Engagement · Posts · Citations · Cite this entry
5,885subscribers
+5,799 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001796868597 |
|---|---|
| Type | Channel |
| Username | @gtabrowser |
| Created | 22 July 2022 — measured — dated from the channel’s first post |
| First recorded | 9 August 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/gtabrowser |
Gaming — a classification, not a measurement. An on-box language model (qwen3.6:35b-a3b, prompt version 1) read this channel’s own recent posts on 3 November 2026 and assigned it the closest of 31 fixed categories, at 98% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
@gtabrowser was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Nov 2026, 22:46 | 5,885 | +308 |
| 4 Nov 2026, 04:55 | 5,577 | +51 |
| 3 Nov 2026, 06:22 | 5,526 | +5,440 |
| 9 Aug 2026, 16:17 | 86 | no change |
| 7 Aug 2026, 07:45 | 86 | first reading |
25 posts held, back to 22 July 2022 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 29 October 2026 |
|---|---|
| Posts held | 25 (22 July 2022 – 29 October 2026) |
| Views total | 22,940 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Nov 2026, 06:22 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Telegram’s own ‘edited’ marker: 3 of 3 posts held from the last 30 days (100.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Online multiplayer test - is open 🟢 Player list - Z WebMenu - F4 New Menyoo - F8 This is testing version and there may be bugs Link: t.me/gtabrowser/2 upd: menyoo connected, some bugs have been fixed, and spawns are now in one place. Added synchronization of character skins, wanted level, and item in hand
If you have low FPS, enable this option chrome://flags/#ignore-gpu-blocklist 🟢 Launcher online status:
changelog 2
Промокод - 1021 Сумма - 300.00 ₽ Адрес - cashot.my/bonus 📲 Играйте на телефонах ⚡️Активация на странице Бонусы
Промокод - 1020 Сумма - 500.00 ₽ Адрес - cashot.my/bonus 📲 Играйте на телефонах ⚡Активация на странице Бонусы
Промокод - 1018 Сумма - 500.00 ₽ Адрес - cashot.my/bonus 🎁 Активация на странице Бонусы
Промокод - 1017 Сумма - 500.00 ₽ Адрес - cashot.my/bonus 🎁 Активация на странице Бонусы
Промокод - 1016 Сумма - 400.00 ₽ Адрес - cashot.my/bonus 🎁 Активация на странице Бонусы
Играйте на ставки, в новой игре AGARBET https://cashot.my/agario
Промокод - 1014 Сумма - 400.00 ₽ Адрес - cashot.my/bonus 🎁 Активация на странице Бонусы
Промокод - 1013 Сумма - 300.00 ₽ Адрес - cashot.my/bonus 🎁 Активация на странице Бонусы
Промокод - 1012 Сумма - 400.00 ₽ Адрес - cashot.my/bonus 🎁 Активация на странице Бонусы
Showing the 12 most recent of 25 posts we hold for @gtabrowser. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 6 November 2026 — this entry's latest reading, not the date you are reading this.
“Five browser” (@gtabrowser), 5,885 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/gtabrowser.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.