Telegram RegisterThe public register of Telegram
Telegram profile photo for Randy Marsh

Bot

Randy Marsh

@randymbot

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

92,183monthly users

+7,832 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 ID649611690
TypeBot
Username@randymbot
First recorded10 August 2026
Last confirmed live26 August 2026
Measurements held16
Confirmed unchanged1 time, most recently 26 August 2026
On Telegramt.me/randymbot

Growth

80,49792,18386,3406 August 2026 — 84,351 monthly users7 August 2026 — 84,725 monthly users8 August 2026 — 84,942 monthly users9 August 2026 — 84,203 monthly users10 August 2026 — 84,203 monthly users12 August 2026 — 85,299 monthly users12 August 2026 — 84,849 monthly users14 August 2026 — 83,927 monthly users17 August 2026 — 83,021 monthly users18 August 2026 — 82,484 monthly users19 August 2026 — 80,497 monthly users21 August 2026 — 81,682 monthly users23 August 2026 — 81,324 monthly users24 August 2026 — 81,022 monthly users25 August 2026 — 89,646 monthly users26 August 2026 — 92,183 monthly users6 August 202626 August 2026
16 measurements spanning 21 days, net +7,832. 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 78,744–93,936 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
26 Aug 2026, 19:5392,183+2,537
25 Aug 2026, 18:4489,646+8,624
24 Aug 2026, 16:5981,022-302
23 Aug 2026, 01:3581,324-358
21 Aug 2026, 16:2681,682+1,185
19 Aug 2026, 12:1280,497-1,987
18 Aug 2026, 08:4282,484-537
17 Aug 2026, 10:1783,021-906
14 Aug 2026, 07:5483,927-922
12 Aug 2026, 21:3584,849-450
12 Aug 2026, 00:0285,299+1,096
10 Aug 2026, 19:5784,203no change
9 Aug 2026, 05:0384,203-739
8 Aug 2026, 04:1284,942+217
7 Aug 2026, 01:4284,725+374
6 Aug 2026, 02:2584,351first 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 3 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 26 August 2026 — this entry's latest reading, not the date you are reading this.

“Randy Marsh” (@randymbot), 92,183 monthly users as measured 26 August 2026. Telegram Register, tgregister.com/channel/randymbot.

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.