https://vt.tiktok.com/ZSeDgDR5u/
Signed Nᴀʟᴅɪ

Channel
@BJGamingg
On this record: Topic · Growth · Engagement · Posts · Cite this entry
1,153subscribers
-38 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001240023224 |
|---|---|
| Type | Channel |
| Username | @BJGamingg |
| Created | 15 April 2019 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 11 October 2026 |
| On Telegram | t.me/BJGamingg |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 18 September 2026 and assigned it the closest of 31 fixed categories, at 52% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Oct 2026, 11:15 | 1,153 | -1 |
| 5 Oct 2026, 12:18 | 1,154 | -6 |
| 27 Sept 2026, 09:16 | 1,160 | -2 |
| 18 Sept 2026, 12:59 | 1,162 | -3 |
| 14 Sept 2026, 06:40 | 1,165 | -4 |
| 10 Sept 2026, 15:41 | 1,169 | -4 |
| 5 Sept 2026, 07:00 | 1,173 | -1 |
| 1 Sept 2026, 15:05 | 1,174 | -1 |
| 26 Aug 2026, 09:04 | 1,175 | -3 |
| 23 Aug 2026, 15:38 | 1,178 | -5 |
| 20 Aug 2026, 01:32 | 1,183 | -2 |
| 16 Aug 2026, 15:13 | 1,185 | -2 |
| 13 Aug 2026, 01:37 | 1,187 | -2 |
| 10 Aug 2026, 07:33 | 1,189 | -2 |
| 6 Aug 2026, 09:21 | 1,191 | no change |
| 6 Aug 2026, 09:11 | 1,191 | first reading |
11 posts held, back to 9 March 2020 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of 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 2 December 2021. An engagement rate over an empty window would be a number about nothing.
https://vt.tiktok.com/ZSeDgDR5u/
Signed Nᴀʟᴅɪ
See u
Signed Nᴀʟᴅɪ
ʙᴊɢᴀᴍɪɴɢ ᴏꜰꜰɪᴄɪᴀʟ pinned Deleted message
Photo, posted without a caption
Signed BJ彡I'ᴍ Nᴀʟᴅɪ
Photo, posted without a caption
Signed BJ彡I'ᴍ Nᴀʟᴅɪ
Photo, posted without a caption
Signed BJ彡I'ᴍ Nᴀʟᴅɪ
Photo, posted without a caption
Signed BJ彡I'ᴍ Nᴀʟᴅɪ
Photo, posted without a caption
Signed BJ彡I'ᴍ Nᴀʟᴅɪ
Photo, posted without a caption
Signed BJ彡I'ᴍ Nᴀʟᴅɪ
Photo, posted without a caption
Signed BJ彡I'ᴍ Nᴀʟᴅɪ
Photo, posted without a caption
Signed BJ彡I'ᴍ Nᴀʟᴅɪ
Showing the 11 most recent of 11 posts we hold for @BJGamingg. 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.
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 11 October 2026 — this entry's latest reading, not the date you are reading this.
“ʙᴊɢᴀᴍɪɴɢ ᴏꜰꜰɪᴄɪᴀʟ” (@BJGamingg), 1,153 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/BJGamingg.
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.