Telegram RegisterThe public register of Telegram
Telegram profile photo for ๐‹๐จ๐‹

Bot

๐‹๐จ๐‹

@LL0_BOT

On this record: Growth ยท Engagement ยท Citations ยท Cite this entry

20,524monthly users

-1,144 since we began measuring on 7 August 2026

Risers and fallers across the register ยท movement among entries of 10,000โ€“31,623.

Register entry

Telegram ID6932093119
TypeBot
Username@LL0_BOT
First recorded16 August 2026
Last confirmed live25 August 2026
Measurements held15
Confirmed unchanged1 time, most recently 25 August 2026
On Telegramt.me/LL0_BOT

Growth

20,08621,66820,8777 August 2026 โ€” 21,668 monthly users8 August 2026 โ€” 21,594 monthly users9 August 2026 โ€” 21,509 monthly users11 August 2026 โ€” 21,466 monthly users12 August 2026 โ€” 21,400 monthly users13 August 2026 โ€” 21,286 monthly users14 August 2026 โ€” 20,928 monthly users16 August 2026 โ€” 20,928 monthly users16 August 2026 โ€” 20,830 monthly users17 August 2026 โ€” 20,356 monthly users19 August 2026 โ€” 20,608 monthly users21 August 2026 โ€” 20,645 monthly users23 August 2026 โ€” 20,086 monthly users24 August 2026 โ€” 20,465 monthly users25 August 2026 โ€” 20,524 monthly users20,5247 August 202625 August 2026
15 measurements spanning 18 days, net -1,144. 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 19,849โ€“21,905 and does not start at zero.
Measurement log โ€” every monthly users count we have recorded
Measured (UTC)Monthly usersChange
25 Aug 2026, 23:5320,524+59
24 Aug 2026, 21:1720,465+379
23 Aug 2026, 05:0320,086-559
21 Aug 2026, 18:0820,645+37
19 Aug 2026, 17:1220,608+252
17 Aug 2026, 14:3620,356-474
16 Aug 2026, 07:0820,830-98
16 Aug 2026, 03:4520,928no change
14 Aug 2026, 20:0520,928-358
13 Aug 2026, 14:0621,286-114
12 Aug 2026, 15:1421,400-66
11 Aug 2026, 11:4321,466-43
9 Aug 2026, 12:3721,509-85
8 Aug 2026, 13:1821,594-74
7 Aug 2026, 15:4721,668first 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 1 registered channel โ€” 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 25 August 2026 โ€” this entry's latest reading, not the date you are reading this.

โ€œ๐‹๐จ๐‹โ€ (@LL0_BOT), 20,524 monthly users as measured 25 August 2026. Telegram Register, tgregister.com/channel/LL0_BOT.

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.