Bot
Mohafez ²
@Goqlvdopqgsoqbot
On this record: Previous handles · Growth · Engagement · Cite this entry
37,081monthly users
+7,334 since we began measuring on 15 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | 8995810754 |
|---|---|
| Type | Bot |
| Username | @Goqlvdopqgsoqbot |
| First recorded | 15 August 2026 |
| Last confirmed live | 20 August 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 20 August 2026 |
| On Telegram | t.me/Goqlvdopqgsoqbot |
Previous handles
@Goqlvdopqgsoqbot 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.
held 15 August 2026 – 15 August 2026
Growth
| Measured (UTC) | Monthly users | Change |
|---|---|---|
| 20 Aug 2026, 17:37 | 37,081 | +1,315 |
| 19 Aug 2026, 17:33 | 35,766 | +1,539 |
| 18 Aug 2026, 16:57 | 34,227 | +2,052 |
| 17 Aug 2026, 19:15 | 32,175 | +2,428 |
| 15 Aug 2026, 18:40 | 29,747 | no change |
| 15 Aug 2026, 18:30 | 29,747 | first reading |
Engagement
No post feed to measure. Telegram publishes a readable post stream for channels, not for bots, so views, reactions and engagement rates do not exist for this entry — they are not missing, pending or withheld. The register records what this handle is and what it resolves to.
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 20 August 2026 — this entry's latest reading, not the date you are reading this.
“Mohafez ²” (@Goqlvdopqgsoqbot), 37,081 monthly users as measured 20 August 2026. Telegram Register, tgregister.com/channel/Goqlvdopqgsoqbot.
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.