Telegram RegisterThe public register of Telegram
Telegram profile photo for SafeBot🛡

Bot

SafeBot🛡

@Robotsafebot

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

17,766monthly users

-2,101 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 ID7587039726
TypeBot
Username@Robotsafebot
First recorded17 August 2026
Last confirmed live27 August 2026
Measurements held17
Confirmed unchanged1 time, most recently 27 August 2026
On Telegramt.me/Robotsafebot

Growth

17,76619,86718,816.57 August 2026 — 19,867 monthly users9 August 2026 — 19,396 monthly users10 August 2026 — 19,033 monthly users12 August 2026 — 18,917 monthly users13 August 2026 — 18,818 monthly users14 August 2026 — 18,768 monthly users16 August 2026 — 18,718 monthly users17 August 2026 — 18,718 monthly users17 August 2026 — 18,603 monthly users18 August 2026 — 18,334 monthly users19 August 2026 — 18,122 monthly users21 August 2026 — 17,971 monthly users22 August 2026 — 17,863 monthly users24 August 2026 — 17,835 monthly users25 August 2026 — 17,792 monthly users26 August 2026 — 17,769 monthly users27 August 2026 — 17,766 monthly users7 August 202627 August 2026
17 measurements spanning 20 days, net -2,101. 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 17,451–20,182 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
27 Aug 2026, 10:1417,766-3
26 Aug 2026, 13:4517,769-23
25 Aug 2026, 13:1217,792-43
24 Aug 2026, 14:0917,835-28
22 Aug 2026, 20:1917,863-108
21 Aug 2026, 11:2617,971-151
19 Aug 2026, 10:1218,122-212
18 Aug 2026, 13:1218,334-269
17 Aug 2026, 12:0718,603-115
17 Aug 2026, 09:1518,718no change
16 Aug 2026, 02:3518,718-50
14 Aug 2026, 09:4718,768-50
13 Aug 2026, 00:3518,818-99
12 Aug 2026, 02:5818,917-116
10 Aug 2026, 08:3819,033-363
9 Aug 2026, 12:0119,396-471
7 Aug 2026, 19:4519,867first 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“SafeBot🛡” (@Robotsafebot), 17,766 monthly users as measured 27 August 2026. Telegram Register, tgregister.com/channel/Robotsafebot.

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.