Telegram RegisterThe public register of Telegram
Telegram profile photo for Зайцы ФПС

Bot

Зайцы ФПС

@BunnyFPSBot

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

36,803monthly users

+7,792 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID1639824051
TypeBot
Username@BunnyFPSBot
First recorded14 August 2026
Last confirmed live28 October 2026
Measurements held38
Confirmed unchanged1 time, most recently 28 October 2026
On Telegramt.me/BunnyFPSBot

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 10 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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

23,50038,39130,945.57 August 2026 — 29,011 monthly users7 August 2026 — 29,279 monthly users9 August 2026 — 29,080 monthly users10 August 2026 — 28,920 monthly users11 August 2026 — 28,119 monthly users12 August 2026 — 27,493 monthly users14 August 2026 — 27,081 monthly users14 August 2026 — 27,081 monthly users16 August 2026 — 26,377 monthly users18 August 2026 — 24,839 monthly users19 August 2026 — 25,384 monthly users22 August 2026 — 24,998 monthly users25 August 2026 — 24,464 monthly users26 August 2026 — 24,400 monthly users27 August 2026 — 24,410 monthly users27 August 2026 — 24,528 monthly users30 August 2026 — 24,293 monthly users31 August 2026 — 24,041 monthly users2 September 2026 — 24,033 monthly users3 September 2026 — 24,053 monthly users6 September 2026 — 23,500 monthly users9 September 2026 — 27,633 monthly users12 September 2026 — 28,410 monthly users15 September 2026 — 29,000 monthly users17 September 2026 — 29,383 monthly users25 September 2026 — 31,645 monthly users3 October 2026 — 34,609 monthly users8 October 2026 — 35,419 monthly users12 October 2026 — 32,201 monthly users14 October 2026 — 33,882 monthly users16 October 2026 — 35,389 monthly users19 October 2026 — 35,931 monthly users20 October 2026 — 36,230 monthly users21 October 2026 — 37,724 monthly users23 October 2026 — 38,391 monthly users25 October 2026 — 38,219 monthly users27 October 2026 — 36,980 monthly users28 October 2026 — 36,803 monthly users36,8037 August 202628 October 2026
38 measurements spanning 83 days, net +7,792. 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 21,266–40,625 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 38
Measured (UTC)Monthly usersChange
28 Oct 2026, 20:0036,803-177
27 Oct 2026, 16:2036,980-1,239
25 Oct 2026, 16:0938,219-172
23 Oct 2026, 19:4638,391+667
21 Oct 2026, 11:0737,724+1,494
20 Oct 2026, 09:0636,230+299
19 Oct 2026, 12:0935,931+542
16 Oct 2026, 10:4635,389+1,507
14 Oct 2026, 11:0133,882+1,681
12 Oct 2026, 18:4932,201-3,218
8 Oct 2026, 08:1835,419+810
3 Oct 2026, 22:4034,609+2,964
25 Sept 2026, 02:4231,645+2,262
17 Sept 2026, 09:5829,383+383
15 Sept 2026, 07:5729,000+590
12 Sept 2026, 01:0028,410+777
9 Sept 2026, 19:1827,633+4,133
6 Sept 2026, 08:2223,500-553
3 Sept 2026, 22:5824,053+20
2 Sept 2026, 10:4424,033first 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 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 28 October 2026 — this entry's latest reading, not the date you are reading this.

“Зайцы ФПС” (@BunnyFPSBot), 36,803 monthly users as measured 28 October 2026. Telegram Register, tgregister.com/channel/BunnyFPSBot.

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.