Bot

Protectron

@ProtectronBot

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

91,931monthly users

-10,896 since we began measuring on 6 August 2026

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

Register entry

Telegram ID	696267355
Type	Bot
Username	@ProtectronBot
First recorded	10 August 2026
Last confirmed live	10 November 2026
Measurements held	39
Confirmed unchanged	1 time, most recently 10 November 2026
On Telegram	t.me/ProtectronBot

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

39 measurements spanning 97 days, net -10,896. 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 88,025–105,577 and does not start at zero.

Measurement log — every monthly users count we have recorded, most recent 20 of 39
Measured (UTC)	Monthly users	Change
10 Nov 2026, 19:29	91,931	-431
9 Nov 2026, 08:20	92,362	+2,312
7 Nov 2026, 20:46	90,050	-4,304
5 Nov 2026, 15:49	94,354	-884
3 Nov 2026, 16:07	95,238	-2,185
31 Oct 2026, 19:20	97,423	+147
29 Oct 2026, 16:40	97,276	-4,233
28 Oct 2026, 13:06	101,509	-1,574
25 Oct 2026, 11:48	103,083	-15
24 Oct 2026, 11:39	103,098	+139
23 Oct 2026, 11:06	102,959	+1,987
20 Oct 2026, 04:29	100,972	-2,580
19 Oct 2026, 03:04	103,552	+82
18 Oct 2026, 03:01	103,470	+603
16 Oct 2026, 03:37	102,867	-306
12 Oct 2026, 05:41	103,173	-113
7 Oct 2026, 12:55	103,286	+3,592
2 Oct 2026, 16:02	99,694	+4,848
18 Sept 2026, 13:40	94,846	+1,574
14 Sept 2026, 11:57	93,272	first 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 10 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.

Named by

Channels on the register whose posts name this channel's handle.

Koleksi Bot
@botkoleksi · 11,58410 posts 中文机器人大全
@bot_zh · 7,1764 posts Создание чат-ботов и сайтов | bezzego
@bezzego_channel · 481 post BOSS AUTOBOTs
@bossautobots · 1,4291 post 摆渡人🛶导航
@DaoHangBaiDuRen · 1,1171 post Forensic Materials
@forensicmaterials · 1081 post Protectron News
@protectronnews · 311 post Telegram新手指引频道
@QingYun00 · 1731 post NEET PG/FRCS/MD PREPARATION✅
@studyrisefoundationpgprep · 6021 post 📢TG电报教程|中文频道
@ZhongwenPindao0 · 541 post

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

“Protectron” (@ProtectronBot), 91,931 monthly users as measured 10 November 2026. Telegram Register, tgregister.com/channel/ProtectronBot.

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.