Channel
@glamur_pubg
On this record: Topic · Growth · Engagement · Posts · Cite this entry
496subscribers
-66 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002687956209 |
|---|---|
| Type | Channel |
| Username | @glamur_pubg |
| Created | 5 May 2025 — measured — dated from the channel’s first post |
| First recorded | 9 August 2026 |
| Last confirmed live | 31 October 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 31 October 2026 |
| On Telegram | t.me/glamur_pubg |
Hacking & security — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 31 Oct 2026, 06:46 | 496 | -2 |
| 17 Oct 2026, 13:28 | 498 | -5 |
| 10 Oct 2026, 03:17 | 503 | -10 |
| 30 Sept 2026, 05:37 | 513 | -6 |
| 16 Sept 2026, 03:38 | 519 | -8 |
| 9 Sept 2026, 01:16 | 527 | -12 |
| 29 Aug 2026, 23:35 | 539 | -14 |
| 23 Aug 2026, 22:14 | 553 | -5 |
| 16 Aug 2026, 06:44 | 558 | -4 |
| 9 Aug 2026, 11:00 | 562 | no change |
| 9 Aug 2026, 10:52 | 562 | first reading |
3 posts held, back to 5 May 2025 — 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 3 posts for this entry, the most recent from 2 April 2026. An engagement rate over an empty window would be a number about nothing.
🔤🔤🔤🔤🔤🔤 ⚡️Akkauntingizga moshennik kirib olgan bo’lsa yoki aldab akkauntingizni olib qo’yishgan bo’lsa akkauntingizga kirmasdan ID orqali qaytarib olib beramiz🔥 Hizmatlar🆕 1️⃣: Chopilgan akaunt qaytarish 2️⃣: Yoqolgan privazkalar tozalash 3️⃣: Akauntdan begona telefonlarni chiqarib tashlash va aftorizatsiya qilish 4️⃣: Akaunt bandan chiqarish 5️⃣: Res bolgan akauntni qayta res qilish 6️⃣: resdan himoya (3 oyli 6 oyl…
Telegram kanal 👇 https://t.me/+lSAnUWaamww5NzEy https://t.me/+lSAnUWaamww5NzEy https://t.me/+lSAnUWaamww5NzEy
Channel created
Showing the 3 most recent of 3 posts we hold for @glamur_pubg. 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 31 October 2026 — this entry's latest reading, not the date you are reading this.
“MEDUZA AKAUNT SAVDO” (@glamur_pubg), 496 subscribers as measured 31 October 2026. Telegram Register, tgregister.com/channel/glamur_pubg.
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.