Telegram RegisterThe public register of Telegram
Telegram profile photo for BFG

Bot

BFG

@bfgproject

2 usernames

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

30,183monthly users

-20,040 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 ID1721358063
TypeBot
Usernames@bfgproject @bforgame_bot
First recorded12 August 2026
Last confirmed live14 November 2026
Measurements held53
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/bfgproject

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 9 September 2026 and assigned it the closest of 31 fixed categories, at 100% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Growth

30,18352,20041,191.57 August 2026 — 50,223 monthly users7 August 2026 — 51,479 monthly users8 August 2026 — 51,160 monthly users9 August 2026 — 51,211 monthly users10 August 2026 — 51,140 monthly users12 August 2026 — 51,140 monthly users12 August 2026 — 52,200 monthly users13 August 2026 — 51,916 monthly users14 August 2026 — 51,961 monthly users16 August 2026 — 51,700 monthly users17 August 2026 — 51,968 monthly users19 August 2026 — 51,924 monthly users21 August 2026 — 52,140 monthly users23 August 2026 — 52,125 monthly users25 August 2026 — 51,903 monthly users26 August 2026 — 51,859 monthly users27 August 2026 — 51,143 monthly users27 August 2026 — 51,054 monthly users29 August 2026 — 49,452 monthly users31 August 2026 — 50,293 monthly users31 August 2026 — 50,290 monthly users3 September 2026 — 49,636 monthly users5 September 2026 — 49,079 monthly users8 September 2026 — 48,374 monthly users11 September 2026 — 46,998 monthly users13 September 2026 — 46,499 monthly users14 September 2026 — 44,484 monthly users16 September 2026 — 44,192 monthly users18 September 2026 — 42,618 monthly users25 September 2026 — 44,224 monthly users3 October 2026 — 40,004 monthly users8 October 2026 — 38,799 monthly users12 October 2026 — 39,341 monthly users14 October 2026 — 39,897 monthly users16 October 2026 — 39,637 monthly users17 October 2026 — 39,240 monthly users18 October 2026 — 39,305 monthly users20 October 2026 — 39,198 monthly users21 October 2026 — 38,926 monthly users23 October 2026 — 36,509 monthly users24 October 2026 — 35,353 monthly users26 October 2026 — 34,544 monthly users27 October 2026 — 34,208 monthly users30 October 2026 — 33,715 monthly users1 November 2026 — 33,355 monthly users2 November 2026 — 33,284 monthly users4 November 2026 — 33,225 monthly users5 November 2026 — 33,415 monthly users7 November 2026 — 33,377 monthly users8 November 2026 — 33,127 monthly users10 November 2026 — 31,661 monthly users11 November 2026 — 30,785 monthly users14 November 2026 — 30,183 monthly users7 August 202614 November 2026
53 measurements spanning 100 days, net -20,040. 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 26,880–55,503 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 53
Measured (UTC)Monthly usersChange
14 Nov 2026, 18:4630,183-602
11 Nov 2026, 21:5730,785-876
10 Nov 2026, 02:2831,661-1,466
8 Nov 2026, 16:5633,127-250
7 Nov 2026, 09:0033,377-38
5 Nov 2026, 07:1533,415+190
4 Nov 2026, 03:5633,225-59
2 Nov 2026, 02:4533,284-71
1 Nov 2026, 05:2633,355-360
30 Oct 2026, 06:0833,715-493
27 Oct 2026, 06:2634,208-336
26 Oct 2026, 04:1034,544-809
24 Oct 2026, 00:3635,353-1,156
23 Oct 2026, 00:1036,509-2,417
21 Oct 2026, 19:0938,926-272
20 Oct 2026, 13:5139,198-107
18 Oct 2026, 18:4939,305+65
17 Oct 2026, 16:0539,240-397
16 Oct 2026, 13:1139,637-260
14 Oct 2026, 10:4939,897first 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 5 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 14 November 2026 — this entry's latest reading, not the date you are reading this.

“BFG” (@bfgproject), 30,183 monthly users as measured 14 November 2026. Telegram Register, tgregister.com/channel/bfgproject.

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.