Telegram RegisterThe public register of Telegram
Telegram profile photo for Ровесник Робот

Bot

Ровесник Робот

@RovesnikRobot

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

13,794monthly users

-960 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 ID5360370447
TypeBot
Username@RovesnikRobot
First recorded18 August 2026
Last confirmed live9 September 2026
Measurements held15
Confirmed unchanged1 time, most recently 9 September 2026
On Telegramt.me/RovesnikRobot

Growth

13,79416,21515,004.56 August 2026 — 14,754 monthly users8 August 2026 — 15,665 monthly users9 August 2026 — 15,974 monthly users13 August 2026 — 15,946 monthly users16 August 2026 — 16,215 monthly users18 August 2026 — 16,215 monthly users19 August 2026 — 16,046 monthly users20 August 2026 — 15,121 monthly users23 August 2026 — 15,062 monthly users25 August 2026 — 14,814 monthly users26 August 2026 — 14,026 monthly users30 August 2026 — 14,136 monthly users2 September 2026 — 13,875 monthly users6 September 2026 — 14,621 monthly users9 September 2026 — 13,794 monthly users6 August 20269 September 2026
15 measurements spanning 34 days, net -960. 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 13,431–16,578 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
9 Sept 2026, 14:3513,794-827
6 Sept 2026, 09:5614,621+746
2 Sept 2026, 15:3913,875-261
30 Aug 2026, 00:1814,136+110
26 Aug 2026, 20:2814,026-788
25 Aug 2026, 18:5814,814-248
23 Aug 2026, 02:5715,062-59
20 Aug 2026, 11:3315,121-925
19 Aug 2026, 14:5716,046-169
18 Aug 2026, 09:4516,215no change
16 Aug 2026, 05:1416,215+269
13 Aug 2026, 03:4415,946-28
9 Aug 2026, 05:1215,974+309
8 Aug 2026, 04:5715,665+911
6 Aug 2026, 04:3514,754first 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 46 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.

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

“Ровесник Робот” (@RovesnikRobot), 13,794 monthly users as measured 9 September 2026. Telegram Register, tgregister.com/channel/RovesnikRobot.

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.