Channel
Mo PUBGM
@Mo_PUBGM
On this record: Growth · Engagement · Cite this entry
7,932subscribers
-684 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002246475988 |
|---|---|
| Type | Channel |
| Username | @Mo_PUBGM |
| Created | Between 1 May 2024 and 31 October 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 25 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/Mo_PUBGM |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 03:16 | 7,932 | -77 |
| 27 Aug 2026, 06:46 | 8,009 | -84 |
| 25 Aug 2026, 17:51 | 8,093 | no change |
| 24 Aug 2026, 11:44 | 8,093 | -107 |
| 20 Aug 2026, 10:32 | 8,200 | -85 |
| 17 Aug 2026, 16:47 | 8,285 | -97 |
| 14 Aug 2026, 16:19 | 8,382 | -103 |
| 11 Aug 2026, 03:11 | 8,485 | -121 |
| 7 Aug 2026, 19:20 | 8,606 | -10 |
| 7 Aug 2026, 13:12 | 8,616 | first reading |
Engagement
No public post preview. We read this entry on 25 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.
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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“Mo PUBGM” (@Mo_PUBGM), 7,932 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/Mo_PUBGM.
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.