Telegram RegisterThe public register of Telegram
Telegram profile photo for بوت♥️زخرفه♥️اسماء♥️اختصارات

Bot

بوت♥️زخرفه♥️اسماء♥️اختصارات

@rllbot

On this record: Growth · Engagement · Citations · Cite this entry

37,028monthly users

+5,294 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 ID5724481157
TypeBot
Username@rllbot
First recorded13 August 2026
Last confirmed live2 September 2026
Measurements held15
Confirmed unchanged1 time, most recently 2 September 2026
On Telegramt.me/rllbot

Growth

31,73438,91235,3236 August 2026 — 31,734 monthly users8 August 2026 — 32,780 monthly users10 August 2026 — 33,122 monthly users11 August 2026 — 33,743 monthly users12 August 2026 — 34,132 monthly users13 August 2026 — 34,132 monthly users14 August 2026 — 34,550 monthly users15 August 2026 — 35,111 monthly users17 August 2026 — 35,731 monthly users20 August 2026 — 36,058 monthly users22 August 2026 — 37,105 monthly users24 August 2026 — 36,583 monthly users27 August 2026 — 38,912 monthly users29 August 2026 — 38,392 monthly users2 September 2026 — 37,028 monthly users37,0286 August 20262 September 2026
15 measurements spanning 26 days, net +5,294. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 30,657–39,989 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
2 Sept 2026, 03:4337,028-1,364
29 Aug 2026, 12:3438,392-520
27 Aug 2026, 14:1538,912+2,329
24 Aug 2026, 06:0236,583-522
22 Aug 2026, 13:5337,105+1,047
20 Aug 2026, 00:3236,058+327
17 Aug 2026, 20:1635,731+620
15 Aug 2026, 16:4735,111+561
14 Aug 2026, 07:3734,550+418
13 Aug 2026, 19:2134,132no change
12 Aug 2026, 23:1534,132+389
11 Aug 2026, 20:1333,743+621
10 Aug 2026, 17:2733,122+342
8 Aug 2026, 13:1132,780+1,046
6 Aug 2026, 20:4631,734first 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 5 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.

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 2 September 2026 — this entry's latest reading, not the date you are reading this.

“بوت♥️زخرفه♥️اسماء♥️اختصارات” (@rllbot), 37,028 monthly users as measured 2 September 2026. Telegram Register, tgregister.com/channel/rllbot.

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.