Bot
WHYNOT.GAME
@whynotgamebot
On this record: Growth · Engagement · Citations · Cite this entry
24,087monthly users
+3,198 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | 8458657202 |
|---|---|
| Type | Bot |
| Username | @whynotgamebot |
| First recorded | 16 August 2026 |
| Last confirmed live | 18 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 18 August 2026 |
| On Telegram | t.me/whynotgamebot |
Growth
| Measured (UTC) | Monthly users | Change |
|---|---|---|
| 18 Aug 2026, 00:57 | 24,087 | +529 |
| 16 Aug 2026, 22:18 | 23,558 | +2,606 |
| 16 Aug 2026, 03:43 | 20,952 | no change |
| 12 Aug 2026, 22:16 | 20,952 | +121 |
| 12 Aug 2026, 00:05 | 20,831 | -474 |
| 9 Aug 2026, 19:03 | 21,305 | +113 |
| 8 Aug 2026, 21:24 | 21,192 | +303 |
| 6 Aug 2026, 04:20 | 20,889 | 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.
Mentions
Named by 30 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
@STRYXCS2 · 7218 postsZYBR Gaming
@zybr_gaming · 7214 postsInternal League
@tiernewshundread · 4388 postsAEON – CS2 Team
@aeon_esports · 1,9717 postsTEAM | ALNAZE
@alnazeteam · 2835 postshimizu
@ihimizu · 1,3205 postsAEON League
@amleague · 1344 postsЛюкс Рейда
@Re1dqq · 584 postsFUNERAL | Tournament
@FUNERALTEAM · 4293 postsMCT | CS2 TOURNAMENT
@mct_tour · 7583 postsTuimada Team | CS2
@tuimadacs2 · 973 postsУголок деда (CS2)
@cs2_ded · 1,1172 postsFREE SKINS CS2 | DOTA2 СКИНЫ КЛЮЧИ БЕСПЛАТНО
@FreeSkins_CS2_Dota2 · 9762 postsLegion eSports | CS2
@Legion_eSportss · 1272 postsWHYNOT.GAME
@whynot_game · 4,1692 postsAFL | Amateur football league
@AFL_Zheleznogorsk · 3091 postantixxx
@antixxx_tg · 521 postОтзывы CSDropsHub
@CSDropsHubotziv · 151 postEzSkins | Cs2 Bots
@EzSkinsBots · 311 postgregory
@ggregorynt · 331 postMGL Esports
@mglesports · 1891 postПрофессиональная Киберспортивная Лига | ПКЛ CS2
@pcleague · 1,3341 postНовости Counter-Strike 2/ Бесплатные скины
@robikcs · 941 postПросто Tizzy
@tizzycs2 · 1,5301 post
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
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 18 August 2026 — this entry's latest reading, not the date you are reading this.
“WHYNOT.GAME” (@whynotgamebot), 24,087 monthly users as measured 18 August 2026. Telegram Register, tgregister.com/channel/whynotgamebot.
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.