Telegram RegisterThe public register of Telegram
Telegram profile photo for Boinkers

Bot

Boinkers

@boinker_bot

Verified by Telegram

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

891,689monthly users

+405,539 since we began measuring on 5 August 2026

Risers and fallers across the register · movement among entries of 316,228–1,000,000.

Register entry

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

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 84% 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

474,575956,249715,4125 August 2026 — 486,150 monthly users6 August 2026 — 486,150 monthly users7 August 2026 — 486,786 monthly users8 August 2026 — 487,684 monthly users9 August 2026 — 488,799 monthly users10 August 2026 — 484,696 monthly users11 August 2026 — 479,854 monthly users12 August 2026 — 476,262 monthly users13 August 2026 — 474,575 monthly users14 August 2026 — 486,312 monthly users16 August 2026 — 540,729 monthly users17 August 2026 — 566,889 monthly users19 August 2026 — 574,195 monthly users20 August 2026 — 580,249 monthly users21 August 2026 — 574,763 monthly users22 August 2026 — 580,912 monthly users24 August 2026 — 587,468 monthly users26 August 2026 — 590,210 monthly users27 August 2026 — 673,841 monthly users28 August 2026 — 718,239 monthly users29 August 2026 — 753,217 monthly users30 August 2026 — 787,113 monthly users31 August 2026 — 818,567 monthly users1 September 2026 — 829,280 monthly users2 September 2026 — 842,950 monthly users4 September 2026 — 862,686 monthly users6 September 2026 — 905,267 monthly users9 September 2026 — 932,958 monthly users12 September 2026 — 935,553 monthly users14 September 2026 — 956,249 monthly users15 September 2026 — 949,570 monthly users17 September 2026 — 891,689 monthly users891,6895 August 202617 September 2026
32 measurements spanning 43 days, net +405,539. 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 402,324–1,028,500 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 32
Measured (UTC)Monthly usersChange
17 Sept 2026, 19:17891,689-57,881
15 Sept 2026, 19:17949,570-6,679
14 Sept 2026, 00:20956,249+20,696
12 Sept 2026, 04:19935,553+2,595
9 Sept 2026, 20:20932,958+27,691
6 Sept 2026, 11:22905,267+42,581
4 Sept 2026, 03:36862,686+19,736
2 Sept 2026, 17:25842,950+13,670
1 Sept 2026, 17:13829,280+10,713
31 Aug 2026, 15:15818,567+31,454
30 Aug 2026, 15:38787,113+33,896
29 Aug 2026, 14:02753,217+34,978
28 Aug 2026, 16:02718,239+44,398
27 Aug 2026, 14:11673,841+83,631
26 Aug 2026, 12:53590,210+2,742
24 Aug 2026, 15:25587,468+6,556
22 Aug 2026, 21:09580,912+6,149
21 Aug 2026, 12:46574,763-5,486
20 Aug 2026, 13:16580,249+6,054
19 Aug 2026, 09:45574,195first 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 744 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.

“Boinkers” (@boinker_bot), 891,689 monthly users as measured 17 September 2026. Telegram Register, tgregister.com/channel/boinker_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.