Telegram RegisterThe public register of Telegram
Telegram profile photo for Darilo

Bot

Darilo

@Darilo_robot

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

18,922monthly users

-1,078 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 ID8262697620
TypeBot
Username@Darilo_robot
First recorded16 August 2026
Last confirmed live25 August 2026
Measurements held17
Confirmed unchanged1 time, most recently 25 August 2026
On Telegramt.me/Darilo_robot

Growth

18,73820,00019,3697 August 2026 — 20,000 monthly users9 August 2026 — 19,923 monthly users10 August 2026 — 19,802 monthly users11 August 2026 — 19,728 monthly users12 August 2026 — 19,509 monthly users13 August 2026 — 19,470 monthly users14 August 2026 — 19,421 monthly users16 August 2026 — 19,121 monthly users16 August 2026 — 19,121 monthly users17 August 2026 — 19,245 monthly users18 August 2026 — 19,323 monthly users19 August 2026 — 19,277 monthly users20 August 2026 — 18,738 monthly users21 August 2026 — 18,813 monthly users23 August 2026 — 18,843 monthly users24 August 2026 — 18,812 monthly users25 August 2026 — 18,922 monthly users18,9227 August 202625 August 2026
17 measurements spanning 18 days, net -1,078. 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 18,549–20,189 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
25 Aug 2026, 15:5218,922+110
24 Aug 2026, 17:5318,812-31
23 Aug 2026, 04:0718,843+30
21 Aug 2026, 17:5918,813+75
20 Aug 2026, 14:5418,738-539
19 Aug 2026, 13:1319,277-46
18 Aug 2026, 15:3219,323+78
17 Aug 2026, 14:2719,245+124
16 Aug 2026, 20:4219,121no change
16 Aug 2026, 07:2819,121-300
14 Aug 2026, 17:5619,421-49
13 Aug 2026, 06:5519,470-39
12 Aug 2026, 07:4219,509-219
11 Aug 2026, 06:4219,728-74
10 Aug 2026, 04:2419,802-121
9 Aug 2026, 03:5419,923-77
7 Aug 2026, 19:4620,000first 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 10 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 25 August 2026 — this entry's latest reading, not the date you are reading this.

“Darilo” (@Darilo_robot), 18,922 monthly users as measured 25 August 2026. Telegram Register, tgregister.com/channel/Darilo_robot.

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.