Telegram RegisterThe public register of Telegram
Telegram profile photo for MiroSec C2

Channel

MiroSec C2

@mirosecurity

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

180subscribers

-2,216 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1004457798856
TypeChannel
Username@mirosecurity
Created26 July 2026 — measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live6 October 2026
Measurements held14
Confirmed unchanged1 time, most recently 6 October 2026
On Telegramt.me/mirosecurity

Topic

Hacking & security — 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 11 August 2026 and assigned it the closest of 31 fixed categories, at 99% 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

1802,3961,2887 August 2026 — 2,396 subscribers7 August 2026 — 2,396 subscribers10 August 2026 — 2,222 subscribers13 August 2026 — 2,141 subscribers16 August 2026 — 1,479 subscribers20 August 2026 — 1,448 subscribers24 August 2026 — 1,425 subscribers27 August 2026 — 1,356 subscribers29 August 2026 — 1,357 subscribers1 September 2026 — 1,319 subscribers6 September 2026 — 190 subscribers13 September 2026 — 189 subscribers25 September 2026 — 182 subscribers6 October 2026 — 180 subscribers7 August 20266 October 2026
14 measurements spanning 60 days, net -2,216. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Oct 2026, 21:16180-2
25 Sept 2026, 05:59182-7
13 Sept 2026, 12:55189-1
6 Sept 2026, 09:14190-1,129
1 Sept 2026, 19:361,319-38
29 Aug 2026, 22:041,357+1
27 Aug 2026, 00:561,356-69
24 Aug 2026, 01:551,425-23
20 Aug 2026, 05:421,448-31
16 Aug 2026, 20:261,479-662
13 Aug 2026, 04:182,141-81
10 Aug 2026, 12:462,222-174
7 Aug 2026, 20:172,396no change
7 Aug 2026, 19:432,396first reading

Engagement

9 posts held, back to 26 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 9 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

6 Aug 2026, 13:38 UTC892 viewsread 7 August 2026

🔔 Incoming Traffic Overview 🔔 ➖➖➖➖➖➖➖➖➖➖➖➖ 📈 Metric Statistics: • Traffic: 623.68 MbPS • PPS: 56.90 K 📊 Peak Statistics: • Peak Traffic: 2.16 TbPS • Peak PPS: 197.48 M 🚨 Attack Type: • UDP (100.00%) 🚪 Source Port: • 12001/UDP (20.08%) • 12002/UDP (18.73%) • 7585/UDP (8.63%) • 2692/UDP (8.60%) • 10533/UDP (7.93%) 🏢 Source ASN: • AS27747 - Telecentro S.A. (17.47%) • AS8151 - UNINET (12.76%) • AS7303 - Telecom…

5 Aug 2026, 21:10 UTC≈2,360 viewsread 7 August 2026

Miro CNC Pricing / SSH/API/OVH 1 Concurrent | 120s Cooldown | 60s Max Time • 1 day / 5u • 7 days / 10u • 31 days / 20u Addons • Remove Cooldown / 8u • +60s Max Time (Maximum is 200s) / 4u • +1 concurrent(Maximum is 10 concurrent) / 8u • API Access / 15u • VIP Access / 5u • Raw/OVH Access / 40u u = usd($)

2 Aug 2026, 11:24 UTC≈4,040 viewsread 7 August 2026

Remember - we continue to maintain our 100% uptime! We operate on one main proxy and 3 backups if any ever go down. Join our backup server below to make sure you stay with us if the channel gets fucked t.me/mirobestpower

Signed yck

27 Jul 2026, 06:52 UTC≈26,300 viewsread 7 August 2026

DM TO ORDER BELOW! @mirosec666 📲 Power Proof Vouches backup : t.me/mirobestpower main channel: t.me/mirosecurity ❗️Note ~ as of now, Miro Security is a 2 person team; I am a reseller and provide lower prices than the official Miro channel. See here

Showing the 9 most recent of 9 posts we hold for @mirosecurity. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

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.

Named by

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

Names

Channels on the register whose handles appear in this channel's posts.

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

“MiroSec C2” (@mirosecurity), 180 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/mirosecurity.

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.