Bot

𝐑ᴇᴘᴏʀᴛ 𝐏ʀᴏᴛᴇᴄᴛɪᴏɴ 𝐁ᴏᴛ⚡

@TeleProtectorBot

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

76,216monthly users

+50,412 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 ID	7761632921
Type	Bot
Username	@TeleProtectorBot
First recorded	14 August 2026
Last confirmed live	25 August 2026
Measurements held	12
Confirmed unchanged	1 time, most recently 25 August 2026
On Telegram	t.me/TeleProtectorBot

Growth

12 measurements spanning 18 days, net +50,412. 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 17,537–83,870 and does not start at zero.

Measurement log — every monthly users count we have recorded
Measured (UTC)	Monthly users	Change
25 Aug 2026, 11:34	76,216	+10,408
24 Aug 2026, 14:38	65,808	+8,180
23 Aug 2026, 00:28	57,628	+10,200
20 Aug 2026, 14:52	47,428	+5,118
19 Aug 2026, 16:14	42,310	+5,186
17 Aug 2026, 19:55	37,124	+4,816
15 Aug 2026, 07:49	32,308	+6,514
14 Aug 2026, 20:53	25,794	no change
14 Aug 2026, 00:37	25,794	+603
11 Aug 2026, 21:56	25,191	-1,912
10 Aug 2026, 02:27	27,103	+1,299
7 Aug 2026, 19:15	25,804	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 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.

Named by

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

𝐑ᴇᴘᴏʀᴛ 𝐏ʀᴏᴛᴇᴄᴛɪᴏɴ 𝐁ᴏᴛ ɪɴꜰᴏ
@teleprotectorbot_info · 38,96012 posts 𝘿𝘼𝙍𝙆 𝙃𝙐
@darkhuchannel · 8481 post 𝙂𝘼𝙈𝙄𝙉𝙂 𝙂𝘼𝘿𝙂𝙀𝙏'𝙎
@GamingGadgetsStore · 2,8621 post Helping Zone With MR AD
@mradofficial4065 · 15,4231 post ✿ συтℓαωz ✿ ɴᴡᴀ
@OUTLAWZ_NWA · 14,1381 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 25 August 2026 — this entry's latest reading, not the date you are reading this.

“𝐑ᴇᴘᴏʀᴛ 𝐏ʀᴏᴛᴇᴄᴛɪᴏɴ 𝐁ᴏᴛ⚡” (@TeleProtectorBot), 76,216 monthly users as measured 25 August 2026. Telegram Register, tgregister.com/channel/TeleProtectorBot.

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.