Telegram RegisterThe public register of Telegram
Telegram profile photo for Raidar

Bot

Raidar

@raidar

2 usernames

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

35,391monthly users

-5,492 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 ID5994885234
TypeBot
Usernames@raidar @RaidarRobot
First recorded12 August 2026
Last confirmed live23 October 2026
Measurements held84
Confirmed unchanged1 time, most recently 23 October 2026
On Telegramt.me/raidar

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 21 August 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

35,39149,32742,3597 August 202623 October 2026
84 measurements spanning 77 days, net -5,492. 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 33,301–51,417 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 84
Measured (UTC)Monthly usersChange
23 Oct 2026, 10:1435,391no change
23 Oct 2026, 04:3635,391-322
22 Oct 2026, 06:3635,713no change
22 Oct 2026, 01:2635,713-420
21 Oct 2026, 03:1636,133no change
20 Oct 2026, 18:0836,133-800
19 Oct 2026, 16:5036,933no change
18 Oct 2026, 21:0536,933-444
18 Oct 2026, 15:2637,377no change
17 Oct 2026, 18:5537,377-469
17 Oct 2026, 13:4637,846no change
16 Oct 2026, 18:1837,846-261
15 Oct 2026, 16:4138,107no change
15 Oct 2026, 13:0938,107-130
14 Oct 2026, 16:1638,237no change
14 Oct 2026, 09:3738,237+179
13 Oct 2026, 10:0838,058no change
12 Oct 2026, 21:2138,058-1,442
9 Oct 2026, 06:4039,500-344
8 Oct 2026, 08:1739,844first 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 16 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 23 October 2026 — this entry's latest reading, not the date you are reading this.

“Raidar” (@raidar), 35,391 monthly users as measured 23 October 2026. Telegram Register, tgregister.com/channel/raidar.

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.