Telegram RegisterThe public register of Telegram
Telegram profile photo for BotFather

Bot

BotFather

@BotFather

Verified by TelegramNot marked by Telegram, checked 9 August 2026

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

8,805,452monthly users

+856,197 since we began measuring on 5 August 2026

Risers and fallers across the register · movement among the largest entries.

Register entry

Telegram ID93372553
TypeBot
Username@BotFather
First recorded6 August 2026
Last confirmed live17 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/BotFather

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 88% 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 why it has no browse page of its own yet.

Growth

7,949,2558,962,5798,455,9175 August 2026 — 7,949,255 monthly users6 August 2026 — 7,949,255 monthly users6 August 2026 — 8,008,517 monthly users7 August 2026 — 8,082,821 monthly users8 August 2026 — 8,111,881 monthly users10 August 2026 — 8,122,955 monthly users11 August 2026 — 8,189,099 monthly users11 August 2026 — 8,216,462 monthly users13 August 2026 — 8,281,906 monthly users14 August 2026 — 8,395,030 monthly users15 August 2026 — 8,483,485 monthly users16 August 2026 — 8,518,674 monthly users18 August 2026 — 8,560,363 monthly users18 August 2026 — 8,596,153 monthly users19 August 2026 — 8,656,887 monthly users20 August 2026 — 8,742,303 monthly users22 August 2026 — 8,774,887 monthly users24 August 2026 — 8,711,287 monthly users25 August 2026 — 8,384,261 monthly users26 August 2026 — 8,409,519 monthly users27 August 2026 — 8,501,365 monthly users28 August 2026 — 8,574,366 monthly users29 August 2026 — 8,666,489 monthly users30 August 2026 — 8,705,765 monthly users31 August 2026 — 8,722,420 monthly users1 September 2026 — 8,753,856 monthly users2 September 2026 — 8,794,463 monthly users3 September 2026 — 8,859,039 monthly users6 September 2026 — 8,909,280 monthly users9 September 2026 — 8,859,039 monthly users12 September 2026 — 8,905,642 monthly users13 September 2026 — 8,962,579 monthly users15 September 2026 — 8,905,833 monthly users17 September 2026 — 8,805,452 monthly users8,805,4525 August 202617 September 2026
34 measurements spanning 42 days, net +856,197. 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 7,797,256–9,114,578 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 34
Measured (UTC)Monthly usersChange
17 Sept 2026, 08:378,805,452-100,381
15 Sept 2026, 10:168,905,833-56,746
13 Sept 2026, 19:368,962,579+56,937
12 Sept 2026, 01:598,905,642+46,603
9 Sept 2026, 17:378,859,039-50,241
6 Sept 2026, 07:218,909,280+50,241
3 Sept 2026, 22:008,859,039+64,576
2 Sept 2026, 11:178,794,463+40,607
1 Sept 2026, 08:368,753,856+31,436
31 Aug 2026, 11:348,722,420+16,655
30 Aug 2026, 09:138,705,765+39,276
29 Aug 2026, 06:128,666,489+92,123
28 Aug 2026, 04:288,574,366+73,001
27 Aug 2026, 03:558,501,365+91,846
26 Aug 2026, 04:248,409,519+25,258
25 Aug 2026, 05:498,384,261-327,026
24 Aug 2026, 02:078,711,287-63,600
22 Aug 2026, 07:088,774,887+32,584
20 Aug 2026, 20:548,742,303+85,416
19 Aug 2026, 21:188,656,887first 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

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 977 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 17 September 2026 — this entry's latest reading, not the date you are reading this.

“BotFather” (@BotFather), 8,805,452 monthly users as measured 17 September 2026. Telegram Register, tgregister.com/channel/BotFather.

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.