Telegram RegisterThe public register of Telegram
Telegram profile photo for Bnb Forge

Bot

Bnb Forge

@BnbForge_Bot

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

22,245monthly users

+6,878 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 ID8630831667
TypeBot
Username@BnbForge_Bot
First recorded18 August 2026
Last confirmed live4 September 2026
Measurements held17
Confirmed unchanged1 time, most recently 4 September 2026
On Telegramt.me/BnbForge_Bot

Growth

13,01422,30617,6607 August 2026 — 15,367 monthly users8 August 2026 — 14,907 monthly users10 August 2026 — 14,001 monthly users11 August 2026 — 13,044 monthly users13 August 2026 — 13,014 monthly users14 August 2026 — 13,773 monthly users17 August 2026 — 14,859 monthly users18 August 2026 — 15,729 monthly users18 August 2026 — 15,729 monthly users21 August 2026 — 17,947 monthly users23 August 2026 — 18,993 monthly users25 August 2026 — 20,345 monthly users27 August 2026 — 20,928 monthly users30 August 2026 — 21,539 monthly users31 August 2026 — 21,733 monthly users2 September 2026 — 22,306 monthly users4 September 2026 — 22,245 monthly users22,2457 August 20264 September 2026
17 measurements spanning 28 days, net +6,878. 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 11,620–23,700 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
4 Sept 2026, 04:0222,245-61
2 Sept 2026, 15:2722,306+573
31 Aug 2026, 19:1521,733+194
30 Aug 2026, 20:1521,539+611
27 Aug 2026, 19:1420,928+583
25 Aug 2026, 16:1820,345+1,352
23 Aug 2026, 02:5318,993+1,046
21 Aug 2026, 14:0717,947+2,218
18 Aug 2026, 16:3615,729no change
18 Aug 2026, 14:4215,729+870
17 Aug 2026, 13:4414,859+1,086
14 Aug 2026, 15:4513,773+759
13 Aug 2026, 05:2713,014-30
11 Aug 2026, 04:1113,044-957
10 Aug 2026, 03:1214,001-906
8 Aug 2026, 04:3114,907-460
7 Aug 2026, 06:1615,367first 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 6 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 4 September 2026 — this entry's latest reading, not the date you are reading this.

“Bnb Forge” (@BnbForge_Bot), 22,245 monthly users as measured 4 September 2026. Telegram Register, tgregister.com/channel/BnbForge_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.