Telegram RegisterThe public register of Telegram
Telegram profile photo for ربات بت فوروارد

Bot

ربات بت فوروارد

@betforward_bot

2 usernames

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

15,175monthly users

-2,556 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 ID7831902380
TypeBot
Usernames@betforward_bot @btfrbot
First recorded18 August 2026
Last confirmed live21 August 2026
Measurements held15
Confirmed unchanged1 time, most recently 21 August 2026
On Telegramt.me/betforward_bot

Growth

15,17517,73116,4536 August 2026 — 17,731 monthly users8 August 2026 — 17,126 monthly users9 August 2026 — 16,363 monthly users12 August 2026 — 16,284 monthly users13 August 2026 — 15,803 monthly users15 August 2026 — 16,163 monthly users16 August 2026 — 16,237 monthly users17 August 2026 — 15,886 monthly users18 August 2026 — 15,886 monthly users18 August 2026 — 15,853 monthly users19 August 2026 — 15,853 monthly users20 August 2026 — 15,736 monthly users20 August 2026 — 15,736 monthly users21 August 2026 — 15,175 monthly users21 August 2026 — 15,175 monthly users6 August 202621 August 2026
15 measurements spanning 16 days, net -2,556. 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 14,792–18,114 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
21 Aug 2026, 21:2615,175no change
21 Aug 2026, 17:4615,175-561
20 Aug 2026, 17:2415,736no change
20 Aug 2026, 16:5415,736-117
19 Aug 2026, 14:4815,853no change
18 Aug 2026, 21:2215,853-33
18 Aug 2026, 10:3015,886no change
17 Aug 2026, 17:4615,886-351
16 Aug 2026, 16:4716,237+74
15 Aug 2026, 01:2816,163+360
13 Aug 2026, 15:4815,803-481
12 Aug 2026, 15:5616,284-79
9 Aug 2026, 19:0616,363-763
8 Aug 2026, 16:5617,126-605
6 Aug 2026, 00:4317,731first 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 82 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 21 August 2026 — this entry's latest reading, not the date you are reading this.

“ربات بت فوروارد” (@betforward_bot), 15,175 monthly users as measured 21 August 2026. Telegram Register, tgregister.com/channel/betforward_bot.

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.