Telegram RegisterThe public register of Telegram

Bot

ربات چت ناشناس

@BitChats1Bot

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

53,389monthly users

-27,458 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 ID8080534484
TypeBot
Username@BitChats1Bot
First recorded12 August 2026
Last confirmed live13 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/BitChats1Bot

Growth

53,38980,84767,1186 August 2026 — 80,847 monthly users8 August 2026 — 69,852 monthly users9 August 2026 — 63,667 monthly users10 August 2026 — 55,444 monthly users12 August 2026 — 55,444 monthly users12 August 2026 — 54,916 monthly users13 August 2026 — 53,389 monthly users6 August 202613 August 2026
7 measurements spanning 6 days, net -27,458. 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 49,270–84,966 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
13 Aug 2026, 05:2353,389-1,527
12 Aug 2026, 04:1254,916-528
12 Aug 2026, 02:0655,444no change
10 Aug 2026, 10:3755,444-8,223
9 Aug 2026, 09:5363,667-6,185
8 Aug 2026, 10:1069,852-10,995
6 Aug 2026, 22:0680,847first 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

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

“ربات چت ناشناس” (@BitChats1Bot), 53,389 monthly users as measured 13 August 2026. Telegram Register, tgregister.com/channel/BitChats1Bot.

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.