Telegram RegisterThe public register of Telegram
Telegram profile photo for Бесплатные Proxy MTProto | Обход замедлений

Channel

Бесплатные Proxy MTProto | Обход замедлений

@ProxyMTProto_live

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

20,115subscribers

-430 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1003707410501
TypeChannel
Username@ProxyMTProto_live
Created11 February 2026 — measured — dated from the channel’s first post
First recorded6 August 2026
Last confirmed live25 September 2026
Measurements held35
Confirmed unchanged1 time, most recently 25 September 2026
On Telegramt.me/ProxyMTProto_live

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

20,11520,54520,3306 August 2026 — 20,545 subscribers6 August 2026 — 20,545 subscribers7 August 2026 — 20,520 subscribers8 August 2026 — 20,517 subscribers9 August 2026 — 20,492 subscribers10 August 2026 — 20,482 subscribers11 August 2026 — 20,437 subscribers12 August 2026 — 20,394 subscribers13 August 2026 — 20,358 subscribers14 August 2026 — 20,325 subscribers16 August 2026 — 20,314 subscribers17 August 2026 — 20,295 subscribers18 August 2026 — 20,288 subscribers19 August 2026 — 20,344 subscribers20 August 2026 — 20,371 subscribers22 August 2026 — 20,356 subscribers23 August 2026 — 20,343 subscribers25 August 2026 — 20,350 subscribers25 August 2026 — 20,347 subscribers26 August 2026 — 20,339 subscribers27 August 2026 — 20,327 subscribers28 August 2026 — 20,306 subscribers29 August 2026 — 20,289 subscribers30 August 2026 — 20,279 subscribers31 August 2026 — 20,261 subscribers1 September 2026 — 20,250 subscribers2 September 2026 — 20,248 subscribers4 September 2026 — 20,250 subscribers6 September 2026 — 20,248 subscribers9 September 2026 — 20,258 subscribers12 September 2026 — 20,255 subscribers13 September 2026 — 20,250 subscribers15 September 2026 — 20,223 subscribers17 September 2026 — 20,203 subscribers25 September 2026 — 20,115 subscribers6 August 202625 September 2026
35 measurements spanning 50 days, net -430. 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 20,051–20,610 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 35
Measured (UTC)SubscribersChange
25 Sept 2026, 18:5720,115-88
17 Sept 2026, 10:0120,203-20
15 Sept 2026, 10:1820,223-27
13 Sept 2026, 21:0220,250-5
12 Sept 2026, 03:1620,255-3
9 Sept 2026, 22:4020,258+10
6 Sept 2026, 15:4020,248-2
4 Sept 2026, 05:2120,250+2
2 Sept 2026, 21:3820,248-2
1 Sept 2026, 18:0520,250-11
31 Aug 2026, 18:2420,261-18
30 Aug 2026, 21:3320,279-10
29 Aug 2026, 22:3420,289-17
28 Aug 2026, 22:2520,306-21
27 Aug 2026, 18:5320,327-12
26 Aug 2026, 19:2920,339-8
25 Aug 2026, 21:5320,347-3
25 Aug 2026, 00:1320,350+7
23 Aug 2026, 11:1520,343-13
22 Aug 2026, 00:0520,356first reading

Engagement

36 posts held, back to 11 February 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 59 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
16.7%
avg views ÷ 20,115 subscribers
Avg views / post
3,370
3 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
3
of 36 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 2 September 2026
Posts held36 (11 February 2026 – 2 September 2026)
Views total10,100
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 00: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.

Recent posts

2 Sept 2026, 07:19 UTC≈2,580 viewsread 3 September 2026

MTProto Proxy Server: gk5dfzrx.helper.website Port: 443 Secret: ee09f4084df9bd67007f92ac663d323fdb636c6f7564666c6172652e636f6d ⚠️ Время подключения прокси 20-30 секунд | The proxy connection time is 20–30 seconds. Используйте кнопку ниже для подключения. Use the button below to connect automatically. @ProxyMTProto_live

1 Sept 2026, 07:19 UTC≈3,850 viewsread 3 September 2026

MTProto Proxy Server: dkj0klhs.helper.website Port: 443 Secret: ee8dae9fe3b4b1af9a30b96d8862b18e14636c6f7564666c6172652e636f6d ⚠️ Время подключения прокси 20-30 секунд | The proxy connection time is 20–30 seconds. Используйте кнопку ниже для подключения. Use the button below to connect automatically. @ProxyMTProto_live

1 Sept 2026, 07:16 UTC≈3,670 viewsread 3 September 2026

MTProto Proxy Server: dkj0klhs.helper.website Port: 443 Secret: ee8dae9fe3b4b1af9a30b96d8862b18e14636c6f7564666c6172652e636f6d ⚠️ Время подключения прокси 20-30 секунд | The proxy connection time is 20–30 seconds. Используйте кнопку ниже для подключения. Use the button below to connect automatically. @ProxyMTProto_live

28 Aug 2026, 18:02 UTC≈6,050 viewsread 3 September 2026

MTProto Proxy Server: g9cuwvzt.helper.website Port: 443 Secret: ee429843692a574e5efeb2fb3b75d2f7a5636c6f7564666c6172652e636f6d ⚠️ Время подключения прокси 20-30 секунд | The proxy connection time is 20–30 seconds. Используйте кнопку ниже для подключения. Use the button below to connect automatically. @ProxyMTProto_live

27 Aug 2026, 17:33 UTC≈6,130 viewsread 3 September 2026

MTProto Proxy Server: atpmgpfj.helper.website Port: 443 Secret: ee00301b7eb04ac6024806a7c10159a7c1636c6f7564666c6172652e636f6d ⚠️ Время подключения прокси 20-30 секунд | The proxy connection time is 20–30 seconds. Используйте кнопку ниже для подключения. Use the button below to connect automatically. @ProxyMTProto_live

24 Aug 2026, 17:32 UTC≈7,830 viewsread 3 September 2026

MTProto Proxy Server: ljox44lz.helper.website Port: 443 Secret: eeb4f9b88528d51bd43c20e7d400020711636c6f7564666c6172652e636f6d ⚠️ Время подключения прокси 20-30 секунд | The proxy connection time is 20–30 seconds. Используйте кнопку ниже для подключения. Use the button below to connect automatically. @ProxyMTProto_live

23 Aug 2026, 17:32 UTC≈7,360 viewsread 3 September 2026

MTProto Proxy Server: x8dlyy87.helper.website Port: 443 Secret: eec4d4d3b9ee538338d2307be745aa8d8f636c6f7564666c6172652e636f6d ⚠️ Время подключения прокси 20-30 секунд | The proxy connection time is 20–30 seconds. Используйте кнопку ниже для подключения. Use the button below to connect automatically. @ProxyMTProto_live

22 Aug 2026, 17:32 UTC≈7,170 viewsread 3 September 2026

MTProto Proxy Server: gk5dfzrx.helper.website Port: 443 Secret: ee09f4084df9bd67007f92ac663d323fdb636c6f7564666c6172652e636f6d ⚠️ Время подключения прокси 20-30 секунд | The proxy connection time is 20–30 seconds. Используйте кнопку ниже для подключения. Use the button below to connect automatically. @ProxyMTProto_live

21 Aug 2026, 17:31 UTC≈6,570 viewsread 3 September 2026

MTProto Proxy Server: dkj0klhs.helper.website Port: 443 Secret: ee8dae9fe3b4b1af9a30b96d8862b18e14636c6f7564666c6172652e636f6d ⚠️ Время подключения прокси 20-30 секунд | The proxy connection time is 20–30 seconds. Используйте кнопку ниже для подключения. Use the button below to connect automatically. @ProxyMTProto_live

21 Aug 2026, 08:14 UTC≈7,460 viewsread 3 September 2026

MTProto Proxy Server: dkj0klhs.helper.website Port: 443 Secret: ee8dae9fe3b4b1af9a30b96d8862b18e14636c6f7564666c6172652e636f6d ⚠️ Время подключения прокси 20-30 секунд | The proxy connection time is 20–30 seconds. Используйте кнопку ниже для подключения. Use the button below to connect automatically. @ProxyMTProto_live

20 Aug 2026, 18:33 UTC≈7,660 viewsread 3 September 2026

MTProto Proxy Server: gyjaak3i.helper.website Port: 443 Secret: ee1477759e4e530a0d28588907a4a32f3f636c6f7564666c6172652e636f6d ⚠️ Время подключения прокси 20-30 секунд | The proxy connection time is 20–30 seconds. Используйте кнопку ниже для подключения. Use the button below to connect automatically. @ProxyMTProto_live

19 Aug 2026, 18:35 UTC≈3,020 viewsread 20 August 2026

MTProto Proxy Server: g9cuwvzt.helper.website Port: 443 Secret: ee429843692a574e5efeb2fb3b75d2f7a5636c6f7564666c6172652e636f6d ⚠️ Время подключения прокси 20-30 секунд | The proxy connection time is 20–30 seconds. Используйте кнопку ниже для подключения. Use the button below to connect automatically. @ProxyMTProto_live

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

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

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

“Бесплатные Proxy MTProto | Обход замедлений” (@ProxyMTProto_live), 20,115 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/ProxyMTProto_live.

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.