Telegram RegisterThe public register of Telegram
Telegram profile photo for Gabbar Gaming

Channel

Gabbar Gaming

@GabarGAMING_XT

On this record: Growth · Engagement · Posts · Citations · Cite this entry

121subscribers

-4 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001266454281
TypeChannel
Username@GabarGAMING_XT
Created9 September 2020measured — cross-checked against a third-party dataset (TGDataset)
First recorded9 August 2026
Last confirmed live23 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 23 August 2026
On Telegramt.me/GabarGAMING_XT

Growth

1211251237 August 2026 — 125 subscribers7 August 2026 — 124 subscribers9 August 2026 — 124 subscribers15 August 2026 — 123 subscribers23 August 2026 — 121 subscribers7 August 202623 August 2026
5 measurements spanning 16 days, net -4. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 120–126 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 00:26121-2
15 Aug 2026, 15:22123-1
9 Aug 2026, 03:02124no change
7 Aug 2026, 20:50124-1
7 Aug 2026, 00:37125first reading

Engagement

11 posts held, back to 2 October 2021the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 11 posts for this entry, the most recent from 23 August 2022. An engagement rate over an empty window would be a number about nothing.

Recent posts

30 Nov 2021, 06:36 UTC≈2,110 viewsread 9 August 2026
Forwarded from @pubgmglobalaccountsFile

✓VIP SCRIPT ✓Sᴜᴘᴘᴏʀᴛ Bʀᴜᴛᴀʟ ✓ROOT AND NON ROOT ✓ALL PUBG 🔥 PASSWORD = Gillop Support = @GuriGaming_XTT

2 Oct 2021, 11:49 UTC≈3,510 viewsread 9 August 2026

🧡Today I'm going to upload a FULL BRUTAL SUPPORT bypass . 🧡 🔥ONLY for BGMI🔥 ❤️For Android 10 and Android 11❤️ Join - @GabarGAMING_XT

2 Oct 2021, 02:27 UTC≈3,000 viewsread 9 August 2026
File

MODDED PAK FILE: FIX 10MIN BAN Paste: /storage/emulated/0/Android/data/com.pubg.imobile/files/UE4Game/ShadowTrackerExtra/ShadowTrackerExtra/Saved/Paks/ @GabarGAMING_XT

Showing the 11 most recent of 11 posts we hold for @GabarGAMING_XT. 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.

Forward network

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.

Cite this entry

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 23 August 2026 — this entry's latest reading, not the date you are reading this.

“Gabbar Gaming” (@GabarGAMING_XT), 121 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/GabarGAMING_XT.

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.