Bot
Наш слон 💪
@AppSlonbot
On this record: Growth · Engagement · Citations · Cite this entry
14,315monthly users
-3,952 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 | 7791085738 |
|---|---|
| Type | Bot |
| Username | @AppSlonbot |
| First recorded | 17 August 2026 |
| Last confirmed live | 7 September 2026 |
| Measurements held | 29 |
| Confirmed unchanged | 1 time, most recently 7 September 2026 |
| On Telegram | t.me/AppSlonbot |
Growth
| Measured (UTC) | Monthly users | Change |
|---|---|---|
| 7 Sept 2026, 02:54 | 14,315 | -627 |
| 4 Sept 2026, 07:41 | 14,942 | -333 |
| 2 Sept 2026, 22:55 | 15,275 | -148 |
| 1 Sept 2026, 23:19 | 15,423 | -177 |
| 31 Aug 2026, 23:34 | 15,600 | +92 |
| 30 Aug 2026, 21:59 | 15,508 | -203 |
| 28 Aug 2026, 23:16 | 15,711 | -363 |
| 28 Aug 2026, 01:43 | 16,074 | -32 |
| 27 Aug 2026, 05:11 | 16,106 | -125 |
| 26 Aug 2026, 06:28 | 16,231 | +116 |
| 25 Aug 2026, 04:54 | 16,115 | -242 |
| 24 Aug 2026, 01:14 | 16,357 | -353 |
| 22 Aug 2026, 09:58 | 16,710 | -259 |
| 20 Aug 2026, 23:44 | 16,969 | -162 |
| 20 Aug 2026, 00:32 | 17,131 | -164 |
| 19 Aug 2026, 00:34 | 17,295 | -71 |
| 17 Aug 2026, 21:13 | 17,366 | +109 |
| 17 Aug 2026, 19:34 | 17,257 | no change |
| 16 Aug 2026, 21:59 | 17,257 | -118 |
| 15 Aug 2026, 17:52 | 17,375 | 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 16 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.
Named by
Channels on the register whose posts name this channel's handle.
@ibanditos · 53,518400 postsВ приколе (18+)
@iprikole · 1,80915 postsНЕПОТРАЧЕНО | Скидки на WB
@ekonomniwb · 24,5395 postsХалявный Лис 🦊
@freelys · 69,3495 postsWILDBERRIES | Наши находки
@nashli_topchik · 10,8094 postsПолезные ссылки
@usefullproxy · 4,0282 postsЗАРАБАТЫВАЙ-БЕЗ-ВЛОЖЕНИЙ
@bablo_zarabotok · 2561 postБеларусь Сегодня
@belarus_news_onlinerby · 1,4371 postCrypto vector
@cryptovecto · 81 postЭТО ЗНАК!
@etoznakIIIII · 6,9031 postBeautiful Girls 💋
@Euro_Girlss · 18,8461 postпохудение | рпп | голод
@nofatye · 10,1831 postTrading. Быстрый способ разбогатеть!
@orodcmd · 51 postПослание из будущего
@posIanIefuture · 13,9151 postХалявный кролик 🐰
@rabbit_free · 6,0881 postСекса не разу не было
@Zvhu6 · 121 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 7 September 2026 — this entry's latest reading, not the date you are reading this.
“Наш слон 💪” (@AppSlonbot), 14,315 monthly users as measured 7 September 2026. Telegram Register, tgregister.com/channel/AppSlonbot.
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.