TG 链接: https://t.me/webproxy?server=tgeller.shuzizhaimin.com&secret=548593a9c0688f4f7d9d57377897d964 TG 链接: tg://webproxy?server=tgeller.shuzizhaimin.com&secret=548593a9c0688f4f7d9d57377897d964

Channel
TG 代理免费分享
@mtprotocc
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry
12,982subscribers
-251 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001475501863 |
|---|---|
| Type | Channel |
| Username | @mtprotocc |
| Description | 付费稳定机场订阅,中国大陆长期可用 更多内容请访问 https://clashsubs.net |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 63 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/mtprotocc |
Topic
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 11 September 2026 and assigned it the closest of 31 fixed categories, at 51% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Nov 2026, 11:10 | 12,982 | +1 |
| 9 Nov 2026, 14:06 | 12,981 | -3 |
| 8 Nov 2026, 07:50 | 12,984 | -2 |
| 7 Nov 2026, 05:36 | 12,986 | -3 |
| 6 Nov 2026, 04:26 | 12,989 | -6 |
| 5 Nov 2026, 04:50 | 12,995 | -3 |
| 4 Nov 2026, 04:18 | 12,998 | -4 |
| 3 Nov 2026, 02:56 | 13,002 | -7 |
| 2 Nov 2026, 06:11 | 13,009 | -2 |
| 1 Nov 2026, 07:18 | 13,011 | -5 |
| 31 Oct 2026, 06:59 | 13,016 | +3 |
| 30 Oct 2026, 08:18 | 13,013 | -9 |
| 29 Oct 2026, 07:17 | 13,022 | -4 |
| 28 Oct 2026, 04:17 | 13,026 | +4 |
| 27 Oct 2026, 01:38 | 13,022 | +4 |
| 25 Oct 2026, 22:54 | 13,018 | -3 |
| 25 Oct 2026, 02:01 | 13,021 | +7 |
| 24 Oct 2026, 00:28 | 13,014 | +11 |
| 22 Oct 2026, 21:36 | 13,003 | +7 |
| 21 Oct 2026, 15:18 | 12,996 | first reading |
Engagement
21 posts held, back to 10 April 2023 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 68 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 25.4%
- avg views ÷ 12,982 subscribers
- Avg views / post
- 3,300
- 1 post measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 1
- of 21 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 15 October 2026 |
|---|---|
| Posts held | 21 (10 April 2023 – 15 October 2026) |
| Views total | 3,300 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Nov 2026, 20:20 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
- Photos
- 6
- Links
- 62
Lifetime counters from Telegram’s own channel header, read 11 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 1 post held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Telegram 新的 Web 代理(官方全新通道,抗封锁) 要求 Telegram 软件为最新版本。 tg://webproxy?server=tg.noos.eu.cc&secret=80664137832346567966628550109410 来源 @eoops_bot
CF 玩具节点 完成一次「屎诗级」更新 🚀 原本需要部署两套 Worker,现在一个 Worker 全包,服务端共用一套代码同时支持 VLESS 与 Trojan。 代码少了,部署简单了,头发也保住了。 Clash 类型订阅链接 https://text.speedtests.ccwu.cc/sub/cb792fe7-78c2-4284-89b3-8e755c811114/CF/ClashMac 注:ClashMac 中添加订阅链接,然后在配置中挂载使用。 Surge 类型订阅链接 https://text.speedtests.ccwu.cc/sub/c2ed14d6-37e8-4d07-9225-682686a283fc/CF/Surge 原帖介绍 https://t.me/Pinched666/827
访问TG DC 1 2 3 4 5太慢了? 我们免费MTP使用MASQUE出口,实测下载如何DC的文件都能随便拉满。 > 点击一键连接 <
TMProxy+TLS代理: 运行中 服务器IP:38.93.202.240 服务器端口:443 MTProxy Secret: ee9c5bfbac85b364927a7dcd6eaa0bf407617a7572652e6d6963726f736f66742e636f6d TG一键链接: https://t.me/proxy?server=38.93.202.240&port=443&secret=ee9c5bfbac85b364927a7dcd6eaa0bf407617a7572652e6d6963726f736f66742e636f6d
https://t.me/proxy?server=45.251.241.47&port=32666&secret=ee78ccbdbd479a496759e3511b6d1be312617a7572652e6d6963726f736f66742e636f6d
TMProxy+TLS代理: 运行中 服务器IP:154.36.144.188 服务器端口:1080 MTProxy Secret: ee7b0dd48d0fdde84b0f9a60ce004e254a617a7572652e6d6963726f736f66742e636f6d TG一键链接: https://t.me/proxy?server=154.36.144.188&port=1080&secret=ee7b0dd48d0fdde84b0f9a60ce004e254a617a7572652e6d6963726f736f66742e636f6d TG一键链接: tg://proxy?server=154.36.144.188&port=1080&secret=ee7b0dd48d0fdde84b0f9a60ce004e254a617a7572652e6d6963726f736f66742e636f6d
https://t.me/proxy?server=only-apple-can-do.eller.top&port=61443&secret=ee0b652b72004e30f8ab5263d87bd12f0a636c6f7564666c6172652e636f6d 测试代理,看能坚持几天。 仅限 IOS 和 PC
免费TG代理 https://t.me/proxy?server=3arx9g2v.8542112.xyz&port=49290&secret=ee48ff843c619bc29619af45a2d707f07e617a7572652e6d6963726f736f66742e636f6d 赞助机场 #TeaArtCloud (https://4aa.fun)
🚀 免费 Telegram 代理节点! 一键连接,无需翻墙,不限速永久免费! tg://proxy?server=154.219.121.102&port=10086&secret=ee5d9e7dec448d2e39bdc96a4bc2f1d027636c6f7564666c6172652e636f6d https://t.me/proxy?server=182.237.2.241&port=8443&secret=ee0d2eecbbdfa033cebf5176ec4eefd431636c6f7564666c6172652e636f6d https://t.me/proxy?server=154.23.172.215&port=8443&secret=ee4e86586a0eb8b33383acaee894327a8d636c6f7564666c6172652e636f6d
姐妹们我服了,之前用的那个VPN是真·下头🤡!不是卡到想砸电脑,就是一天到晚掉线,整个人直接emo到不行… 直到我遇到了 COCODUCK VPN🦆,我直接原地升天,绝绝子好吗!! 🌍 全球节点随便选,刷油管、冲XHS海外版、海淘统统不卡 📱 多设备登录贼方便,手机电脑都能用 💸 价格真的香,性价比吊打一众大厂牌 🌈 关键是界面干净简洁,操作0门槛,新手友好得不行! 你们说,抛开事实不谈,你就一点也不想试一下吗?! 我把邀请链接贴这了:https://cocoduck.live/auth/register?code=11196cc1b2 冲进来一起飞~💨别再被下头VPN折磨啦!
TG免费代理 https://t.me/proxy?server=119.167.230.212&port=46329&secret=ee20768c2071621c01c26bbec2abb122b5617a7572652e6d6963726f736f66742e636f6d 赞助频道:https://t.me/onesproxys5
Showing the 12 most recent of 21 posts we hold for @mtprotocc. 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.
Posts recorded as deleted after publishing
We recorded 1 post on @mtprotocc as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
- First seen missing
- 3 November 2026
- Most recent seen missing
- 3 November 2026
- Median time before seen missing
- 5 months
- Seen missing in the last 30 days
- 1
Forward network
Republishes
Channels on the register whose posts this channel has forwarded.
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
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@mtprotocc named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 4 November 2026 – 4 November 2026
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 11 November 2026 — this entry's latest reading, not the date you are reading this.
“TG 代理免费分享” (@mtprotocc), 12,982 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/mtprotocc.
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.