Telegram RegisterThe public register of Telegram
Telegram profile photo for ☬ β¦“πŸ¦…π™Žπ™€π˜Ύπ™π™π™€ΰΏΨΆΨ―ΩΩ„ΫŒΩ†Ϊ©β¦” ☬

Bot

☬ β¦“πŸ¦…π™Žπ™€π˜Ύπ™π™π™€ΰΏΨΆΨ―ΩΩ„ΫŒΩ†Ϊ©β¦” ☬

@secure_mbot

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

17,060monthly users

+376 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 ID897467834
TypeBot
Username@secure_mbot
First recorded17 August 2026
Last confirmed live25 August 2026
Measurements held10
Confirmed unchanged2 times, most recently 25 August 2026
On Telegramt.me/secure_mbot

Growth

16,68417,06016,8726 August 2026 β€” 16,684 monthly users8 August 2026 β€” 16,797 monthly users12 August 2026 β€” 16,978 monthly users13 August 2026 β€” 16,961 monthly users16 August 2026 β€” 16,963 monthly users17 August 2026 β€” 16,963 monthly users18 August 2026 β€” 16,900 monthly users20 August 2026 β€” 16,925 monthly users23 August 2026 β€” 17,017 monthly users24 August 2026 β€” 17,060 monthly users6 August 202624 August 2026
10 measurements spanning 18 days, net +376. 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 16,628–17,116 and does not start at zero.
Measurement log β€” every monthly users count we have recorded
Measured (UTC)Monthly usersChange
24 Aug 2026, 19:5717,060+43
23 Aug 2026, 06:2517,017+92
20 Aug 2026, 17:3416,925+25
18 Aug 2026, 18:1616,900-63
17 Aug 2026, 20:0916,963no change
16 Aug 2026, 18:2416,963+2
13 Aug 2026, 17:5616,961-17
12 Aug 2026, 15:0616,978+181
8 Aug 2026, 14:5116,797+113
6 Aug 2026, 21:3016,684first 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 1 registered channel β€” 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 24 August 2026 β€” this entry's latest reading, not the date you are reading this.

β€œβ˜¬ β¦“πŸ¦…π™Žπ™€π˜Ύπ™π™π™€ΰΏΨΆΨ―ΩΩ„ΫŒΩ†Ϊ©β¦” β˜¬β€ (@secure_mbot), 17,060 monthly users as measured 24 August 2026. Telegram Register, tgregister.com/channel/secure_mbot.

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.