Bot
Universe 🌀
@universe_mainbot
On this record: Growth · Engagement · Citations · Cite this entry
35,942monthly users
+7,022 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | 8650808348 |
|---|---|
| Type | Bot |
| Username | @universe_mainbot |
| First recorded | 13 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/universe_mainbot |
Growth
| Measured (UTC) | Monthly users | Change |
|---|---|---|
| 14 Aug 2026, 19:33 | 35,942 | +2,659 |
| 13 Aug 2026, 19:49 | 33,283 | no change |
| 12 Aug 2026, 12:55 | 33,283 | -80 |
| 11 Aug 2026, 09:34 | 33,363 | -907 |
| 9 Aug 2026, 14:11 | 34,270 | +380 |
| 8 Aug 2026, 12:44 | 33,890 | +4,970 |
| 6 Aug 2026, 01:31 | 28,920 | 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 107 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.
@cryptomatone · 11,10888 postsMr.Vincher
@MrVincher_ton · 31,95985 postsCoinFlip
@coinflip_vip · 9,68541 postsUniverse
@universe_main · 5,01540 postsADrops | Crypto & Gifts
@adropscoin · 324,59335 postsNft 2.0 Crypto 😍
@not_2_0 · 11,71533 postsGlusheMoney
@glushemoney · 139,02129 postsКриптология
@criptodro · 136,16628 postsАКРОНИМ
@AcronummT · 47,08424 posts𝗡𝗙𝗧 𝗛𝗨𝗦𝗧𝗟𝗘 | 𝗖𝗥𝗬𝗣𝗧𝗢 𝗦𝗛𝗔𝗥𝗞 🦈
@nft_hust · 11,79124 postsDaily Combo
@They_pay · 15,37124 postsCrypto Alien
@kuscryptoalien · 5,27821 postsVOXEL CODES
@voxelcodes · 4,58918 postsCryptoPulse💸
@crupto_pulse_crupto · 11,86017 postsAlpineEarnsX. TG Apps. Play and Earn
@AlpineEarnsX · 2,10616 postsCrown AirDrop | ایردراپ | گیفت
@croownairdrop · 32,12215 postsNekroTON × Bu
@nekro_ton · 21,31615 postsПуть из найма в крипту
@voxel_man · 2,07615 postsКрипто Бибизьян
@G99Gifts · 22,10814 postsLove Mony - کسب درآمد آنلاین
@LoveMoney456 · 9,80014 postsMRKTmaker 💎
@mrktmaker_ton · 1,50314 postsRedSky | Universe
@cheki_telegram · 1,34813 postsСrypto Pepper🌶 | Трейдинг
@Crypto_Pepper_TRADING · 9,97912 postsGEM💎JAM
@giftgemjam · 19,51412 posts
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“Universe 🌀” (@universe_mainbot), 35,942 monthly users as measured 14 August 2026. Telegram Register, tgregister.com/channel/universe_mainbot.
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.