Telegram RegisterThe public register of Telegram
Telegram profile photo for MTProtoPub - 免费电报代理和VPN分享

Channel

MTProtoPub - 免费电报代理和VPN分享

@MTProtoPub

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

5,762subscribers

+75 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001599404994
TypeChannel
Username@MTProtoPub
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live16 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/MTProtoPub

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 12 September 2026 and assigned it the closest of 31 fixed categories, at 72% 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

5,6875,7675,7278 August 2026 — 5,687 subscribers8 August 2026 — 5,696 subscribers12 August 2026 — 5,714 subscribers15 August 2026 — 5,713 subscribers18 August 2026 — 5,724 subscribers22 August 2026 — 5,758 subscribers25 August 2026 — 5,764 subscribers28 August 2026 — 5,767 subscribers31 August 2026 — 5,757 subscribers2 September 2026 — 5,756 subscribers12 September 2026 — 5,759 subscribers16 September 2026 — 5,762 subscribers5,7628 August 202616 September 2026
12 measurements spanning 39 days, net +75. 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 5,675–5,779 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 03:415,762+3
12 Sept 2026, 10:385,759+3
2 Sept 2026, 23:565,756-1
31 Aug 2026, 04:165,757-10
28 Aug 2026, 12:385,767+3
25 Aug 2026, 09:325,764+6
22 Aug 2026, 13:445,758+34
18 Aug 2026, 17:385,724+11
15 Aug 2026, 08:335,713-1
12 Aug 2026, 03:415,714+18
8 Aug 2026, 23:305,696+9
8 Aug 2026, 04:155,687first reading

Engagement

7 posts held, back to 18 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 5 pages 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 7 posts for this entry, the most recent from 29 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

25 reactions across 5 posts, in 5 distinct kinds. The most used accounts for 80.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2080.0%
👍28.00%
❤‍🔥14.00%
🔥14.00%
🤣14.00%

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 6 of the 7 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 25 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 7 most recent posts we hold, published 18 July 2026 to 29 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.

Recent posts

29 Jul 2026, 14:07 UTC≈1,820 views12 reactionsread 12 August 2026
Photo

🚀 今日流量添加通知 添加时间:2026.07.29 当前节点:🇸🇬 Singapore高速线路 🎙 稳定连接 🛡 优化网络体验 🔄 持续维护更新 💬 使用方法: 切记关闭vpn!!! https://t.me/proxy?server=45.88.42.76&port=12432&secret=eeb7f01f7abec67bbaf227ce230659e08a7777772e6d6963726f736f66742e636f6d https://t.me/proxy?server=45.11.3.74&port=22124&secret=eed77ecc3d0cc0bbed1809bd5ae989e1977777772e6d6963726f736f66742e636f6d

11🤣1

27 Jul 2026, 03:40 UTC≈1,510 views4 reactionsread 12 August 2026
Forwarded from @NavoMessengerFile

File, posted without a caption

4

22 Jul 2026, 07:20 UTC≈2,260 views5 reactionsread 12 August 2026

Server:47.76.65.237 Port:16003 Secret:0ljMZVXUupldONjY550VhRXNTpVeW5WZoxWTwV2aUdFMJFVe5c3QzdGdLlUb3l2N @ResoHubNet #MTProto #MTProxy

3👍2

21 Jul 2026, 01:25 UTC≈1,790 views2 reactionsread 12 August 2026
Forwarded from @NavoMessengerFile

Navo 2.0.1发布: 1,现代化的Apple液态玻璃风格ui,四端风格统一 2,内置精选代理,无需额外翻墙软件即可使用 3,ai聊天摘要,一键总结群、频道内容 反馈群: @navoapp

1❤‍🔥1

18 Jul 2026, 06:07 UTC≈2,250 views2 reactionsread 12 August 2026
Photo

Navo-独立、非官方的 Android / Windows / macOS 即时通讯客户端。使用现有 Telegram 账号登录,在熟悉的网络上体验更轻量的客户端。 @NavoMessenger

1🔥1

Showing the 7 most recent of 7 posts we hold for @MTProtoPub. 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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

“MTProtoPub - 免费电报代理和VPN分享” (@MTProtoPub), 5,762 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/MTProtoPub.

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.