Telegram RegisterThe public register of Telegram
Telegram profile photo for Telegram Proxy Channel

Channel

Telegram Proxy Channel

@mtpro_xyz

On this record: Topic · Growth · Engagement · What this channel posts · Stars · Posts · Citations · Handles named that no longer answer · Cite this entry

157,359subscribers

+244 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID-1001156720321
TypeChannel
Username@mtpro_xyz
DescriptionFresh MTProto and WEB Telegram proxy servers every day. VPN/V2Ray/VLESS Access. Прокси для Telegram/телеграмм/телеграм/тг. Bot: @mtpro_xyz_bot https://mtpro.xyz Unofficial Telegram channel
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live18 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/mtpro_xyz

Topic

Other / unclassifiable — 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 9 August 2026 and assigned it the closest of 31 fixed categories, at 97% 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

156,481157,359156,9207 August 2026 — 157,115 subscribers7 August 2026 — 157,115 subscribers8 August 2026 — 157,111 subscribers8 August 2026 — 157,056 subscribers9 August 2026 — 157,038 subscribers10 August 2026 — 157,079 subscribers11 August 2026 — 157,165 subscribers12 August 2026 — 157,178 subscribers14 August 2026 — 157,194 subscribers15 August 2026 — 157,189 subscribers16 August 2026 — 157,102 subscribers17 August 2026 — 157,079 subscribers18 August 2026 — 156,983 subscribers19 August 2026 — 156,941 subscribers20 August 2026 — 156,877 subscribers22 August 2026 — 156,822 subscribers23 August 2026 — 156,659 subscribers25 August 2026 — 156,596 subscribers26 August 2026 — 156,551 subscribers27 August 2026 — 156,506 subscribers28 August 2026 — 156,481 subscribers28 August 2026 — 156,508 subscribers29 August 2026 — 156,530 subscribers30 August 2026 — 156,562 subscribers1 September 2026 — 156,614 subscribers1 September 2026 — 156,640 subscribers3 September 2026 — 156,656 subscribers4 September 2026 — 156,722 subscribers7 September 2026 — 156,806 subscribers10 September 2026 — 156,985 subscribers12 September 2026 — 157,063 subscribers14 September 2026 — 157,152 subscribers16 September 2026 — 157,229 subscribers18 September 2026 — 157,359 subscribers7 August 202618 September 2026
34 measurements spanning 42 days, net +244. 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 156,349–157,491 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
18 Sept 2026, 03:20157,359+130
16 Sept 2026, 00:57157,229+77
14 Sept 2026, 08:01157,152+89
12 Sept 2026, 19:16157,063+78
10 Sept 2026, 23:19156,985+179
7 Sept 2026, 19:40156,806+84
4 Sept 2026, 17:17156,722+66
3 Sept 2026, 00:38156,656+16
1 Sept 2026, 23:07156,640+26
1 Sept 2026, 00:06156,614+52
30 Aug 2026, 20:18156,562+32
29 Aug 2026, 20:58156,530+22
28 Aug 2026, 23:17156,508+27
28 Aug 2026, 00:22156,481-25
27 Aug 2026, 03:18156,506-45
26 Aug 2026, 02:55156,551-45
25 Aug 2026, 03:38156,596-63
23 Aug 2026, 19:45156,659-163
22 Aug 2026, 03:16156,822-55
20 Aug 2026, 21:07156,877first reading

Engagement

1,739 posts held, back to 7 August 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 137 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
3.37%
avg views ÷ 157,359 subscribers
Avg views / post
5,300
904 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
904
of 1,739 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. It is computed over the 3 of 904 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 29 September 2026
Posts held1,739 (7 August 2026 – 29 September 2026)
Views total4,788,210
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken30 Sept 2026, 04:27 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
≈1
Links
≈65,500

Lifetime counters from Telegram’s own channel header, read 30 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Telegram Stars

Stars received
3
across the posts below
Posts paid on
2
of 1,000 we hold a reading for · 0.2%
Most on one post
2
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @mtpro_xyz. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 1,000 most recent posts we hold for this entry (the sample is capped at 1,000), published 27 August 2026 to 29 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

29 Sept 2026, 19:31 UTC≈5,320 viewsread 30 September 2026

🇬🇧GB https://t.me/webproxy?server=talya.stream&bot=@mtpro_xyz_bot&channel=@mtpro_xyz

29 Sept 2026, 19:31 UTC≈5,240 viewsread 30 September 2026

🇩🇪DE https://t.me/proxy?server=vertex.lanternmoss.top&bot=@mtpro_xyz_bot&channel=@mtpro_xyz

29 Sept 2026, 19:31 UTC≈4,620 viewsread 30 September 2026

🇩🇪DE https://t.me/proxy?server=quasar.lanternmoss.top&bot=@mtpro_xyz_bot&channel=@mtpro_xyz

29 Sept 2026, 19:30 UTC≈3,800 viewsread 30 September 2026

🇩🇪DE https://t.me/proxy?server=ion.pebblewisp.xyz&bot=@mtpro_xyz_bot&channel=@mtpro_xyz

29 Sept 2026, 19:30 UTC≈3,500 viewsread 30 September 2026

🇮🇷IR https://t.me/proxy?server=great.cipservice.co.uk&bot=@mtpro_xyz_bot&channel=@mtpro_xyz

29 Sept 2026, 19:30 UTC≈2,920 viewsread 30 September 2026

🇮🇷IR https://t.me/proxy?server=fruit.golgoli2.co.uk&bot=@mtpro_xyz_bot&channel=@mtpro_xyz

29 Sept 2026, 19:30 UTC≈2,780 viewsread 30 September 2026

🇩🇪DE https://t.me/proxy?server=forest.velvetoak.work&bot=@mtpro_xyz_bot&channel=@mtpro_xyz

29 Sept 2026, 19:30 UTC≈2,720 viewsread 30 September 2026

🇩🇪DE https://t.me/proxy?server=flint.driftquill.click&bot=@mtpro_xyz_bot&channel=@mtpro_xyz

29 Sept 2026, 19:30 UTC≈2,760 viewsread 30 September 2026

🇩🇪DE https://t.me/proxy?server=dune.lanternmoss.top&bot=@mtpro_xyz_bot&channel=@mtpro_xyz

29 Sept 2026, 19:30 UTC≈2,890 viewsread 30 September 2026

🇮🇷IR https://t.me/proxy?server=digi.golgoli2.co.uk&bot=@mtpro_xyz_bot&channel=@mtpro_xyz

29 Sept 2026, 19:30 UTC≈3,540 viewsread 30 September 2026

🇩🇪DE https://t.me/proxy?server=93.123.85.211&bot=@mtpro_xyz_bot&channel=@mtpro_xyz

29 Sept 2026, 13:31 UTC≈9,480 viewsread 30 September 2026

🇷🇺RU https://t.me/webproxy?server=independence.surf&bot=@mtpro_xyz_bot&channel=@mtpro_xyz

Showing the 12 most recent of 1,739 posts we hold for @mtpro_xyz. 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 12 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.

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

“Telegram Proxy Channel” (@mtpro_xyz), 157,359 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/mtpro_xyz.

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.