Telegram RegisterThe public register of Telegram
Telegram profile photo for STRIKE

Bot

STRIKE

@StrikeOfficialBot

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

21,761monthly users

+593 since we began measuring on 6 August 2026

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

Register entry

Telegram ID8601567128
TypeBot
Username@StrikeOfficialBot
First recorded16 August 2026
Last confirmed live4 October 2026
Measurements held17
Confirmed unchanged1 time, most recently 26 September 2026
On Telegramt.me/StrikeOfficialBot

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 why it has no browse page of its own yet.

Growth

21,06738,28229,674.56 August 2026 — 21,168 monthly users8 August 2026 — 22,978 monthly users11 August 2026 — 22,242 monthly users12 August 2026 — 21,067 monthly users16 August 2026 — 21,834 monthly users16 August 2026 — 21,834 monthly users19 August 2026 — 23,932 monthly users23 August 2026 — 26,302 monthly users25 August 2026 — 33,765 monthly users26 August 2026 — 35,722 monthly users28 August 2026 — 37,354 monthly users31 August 2026 — 37,187 monthly users3 September 2026 — 38,282 monthly users5 September 2026 — 35,659 monthly users11 September 2026 — 32,862 monthly users15 September 2026 — 31,759 monthly users26 September 2026 — 21,761 monthly users21,7616 August 202626 September 2026
17 measurements spanning 51 days, net +593. 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 18,485–40,864 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
26 Sept 2026, 00:3821,761-9,998
15 Sept 2026, 04:3631,759-1,103
11 Sept 2026, 17:3732,862-2,797
5 Sept 2026, 17:1635,659-2,623
3 Sept 2026, 16:4038,282+1,095
31 Aug 2026, 07:2637,187-167
28 Aug 2026, 00:2437,354+1,632
26 Aug 2026, 20:5535,722+1,957
25 Aug 2026, 18:1133,765+7,463
23 Aug 2026, 02:1426,302+2,370
19 Aug 2026, 15:0323,932+2,098
16 Aug 2026, 02:4121,834no change
16 Aug 2026, 02:1621,834+767
12 Aug 2026, 23:3621,067-1,175
11 Aug 2026, 01:5522,242-736
8 Aug 2026, 02:0622,978+1,810
6 Aug 2026, 10:5321,168first 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 12 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 26 September 2026 — this entry's latest reading, not the date you are reading this.

“STRIKE” (@StrikeOfficialBot), 21,761 monthly users as measured 26 September 2026. Telegram Register, tgregister.com/channel/StrikeOfficialBot.

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.