Channel
@MysteriaNet_relay
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
454subscribers
+12 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004237402373 |
|---|---|
| Type | Channel |
| Username | @MysteriaNet_relay |
| Created | 12 June 2026 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/MysteriaNet_relay |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 13:55 | 454 | +2 |
| 23 Aug 2026, 21:04 | 452 | +4 |
| 16 Aug 2026, 17:28 | 448 | +6 |
| 8 Aug 2026, 05:05 | 442 | no change |
| 7 Aug 2026, 11:32 | 442 | first reading |
13 posts held, back to 12 June 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 13 posts for this entry, the most recent from 22 July 2026. An engagement rate over an empty window would be a number about nothing.
7 reactions across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 7 | 100.0% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 1 of the 13 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 7 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 12 June 2026 to 22 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
MysteriaNetRelay-Notice pinned «新客户开户要求: 目前重新开放注册 人工开户 个人客户 1TB起 机场客户 4TB起 12.5CNY/TB/月付 开户后需要进行过滤测试，测试通过后会重新进行计费并重置流量(相当于免费跑)，测试失败则进行退款 仅允许使用 Vless 和 Anytls 协议，其他协议已通过防火墙屏蔽 个人规则为：被迁移至测试组后，在4小时内跑满 50GB 流量(可以使用流量消耗器)，期间没有被墙 则正常入组 机场规则为：被迁移至测试组后，3天内跑够300GB 流量，向 @Kaze_522 提供一下你在面板有正常搭建…»
新客户开户要求: 目前重新开放注册 人工开户 个人客户 1TB起 机场客户 4TB起 12.5CNY/TB/月付 开户后需要进行过滤测试，测试通过后会重新进行计费并重置流量(相当于免费跑)，测试失败则进行退款 仅允许使用 Vless 和 Anytls 协议，其他协议已通过防火墙屏蔽 个人规则为：被迁移至测试组后，在4小时内跑满 50GB 流量(可以使用流量消耗器)，期间没有被墙 则正常入组 机场规则为：被迁移至测试组后，3天内跑够300GB 流量，向 @Kaze_522 提供一下你在面板有正常搭建节点的截图，并提供给订阅客户使用，且在期间被墙频率在3小时左右一次 则正常入组 每个测试组同时容纳 2个机场客户和4个个人客户，如果测试组满则需要排队，排队期间会被安置到一台 AWS-JP 使用 在通过过滤组后要求始终预存一个月套餐价格的余额 过滤组当前可用: AWS-JP 过滤后当前可用: AWS-HK AWS-SG …
❤7
目前暂停了部分经常被防火墙识别的客户，可能会有误封的情况，麻烦私信 @kaze_522 证明一下你的协议配置
4TB 套餐调整至 100 规则数
AWS-JP AWS-SG AWS-HK 提供了 IPV6 入口，请在面板查看
AWS-HK 调整到 0.5x 倍率 至少持续时间:7days
AWS-HK 已上线 1 倍率
AWS-JP 调整到 0.5x 倍率 至少持续时间:7days
MysteriaNetRelay-Notice pinned Deleted message
AWS-SG 调整到 0.5x 倍率 至少持续时间:7days
推荐所有客户更换到 Anytls 或者 Vless，使用其他协议可能会更容易被 GFW检测。 推荐所有机场老板自查一下 https://github.com/Null404-0/SubSieve 如果节点墙 IP 的速度太快，后期可能会考虑仅限制以上两种代理协议并开启 SNI 白名单
Channel name was changed to «MysteriaNetRelay-Notice»
Showing the 12 most recent of 13 posts we hold for @MysteriaNet_relay. 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.
Named by 3 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.
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.
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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“MysteriaNetRelay-Notice” (@MysteriaNet_relay), 454 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/MysteriaNet_relay.
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.