Telegram RegisterThe public register of Telegram
Telegram profile photo for Telеgram Prоxy MTProto

Channel

Telеgram Prоxy MTProto

@ProxyFreeMTProto

2 usernames

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

167,735subscribers

+1,319 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002455128193
TypeChannel
Usernames@ProxyFreeMTProto @telehelp
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live30 August 2026
Measurements held47
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/ProxyFreeMTProto

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 8 August 2026 and assigned it the closest of 31 fixed categories, at 74% 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

166,416167,820167,1186 August 2026 — 166,416 subscribers6 August 2026 — 166,416 subscribers6 August 2026 — 166,439 subscribers7 August 2026 — 166,441 subscribers7 August 2026 — 166,469 subscribers7 August 2026 — 166,476 subscribers8 August 2026 — 166,496 subscribers8 August 2026 — 166,508 subscribers9 August 2026 — 166,482 subscribers9 August 2026 — 166,472 subscribers10 August 2026 — 166,498 subscribers10 August 2026 — 166,527 subscribers11 August 2026 — 166,645 subscribers11 August 2026 — 166,846 subscribers12 August 2026 — 166,983 subscribers12 August 2026 — 167,093 subscribers13 August 2026 — 167,232 subscribers14 August 2026 — 167,558 subscribers14 August 2026 — 167,716 subscribers15 August 2026 — 167,728 subscribers16 August 2026 — 167,717 subscribers16 August 2026 — 167,776 subscribers17 August 2026 — 167,776 subscribers17 August 2026 — 167,760 subscribers18 August 2026 — 167,765 subscribers18 August 2026 — 167,761 subscribers19 August 2026 — 167,759 subscribers19 August 2026 — 167,784 subscribers20 August 2026 — 167,820 subscribers20 August 2026 — 167,790 subscribers21 August 2026 — 167,766 subscribers21 August 2026 — 167,783 subscribers22 August 2026 — 167,728 subscribers23 August 2026 — 167,732 subscribers24 August 2026 — 167,655 subscribers24 August 2026 — 167,668 subscribers25 August 2026 — 167,668 subscribers25 August 2026 — 167,645 subscribers26 August 2026 — 167,628 subscribers27 August 2026 — 167,689 subscribers27 August 2026 — 167,689 subscribers28 August 2026 — 167,694 subscribers28 August 2026 — 167,690 subscribers29 August 2026 — 167,723 subscribers29 August 2026 — 167,724 subscribers30 August 2026 — 167,735 subscribers30 August 2026 — 167,735 subscribers167,7356 August 202630 August 2026
47 measurements spanning 24 days, net +1,319. 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 166,205–168,031 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 47
Measured (UTC)SubscribersChange
30 Aug 2026, 05:43167,735no change
30 Aug 2026, 03:34167,735+11
29 Aug 2026, 03:03167,724+1
29 Aug 2026, 02:35167,723+33
28 Aug 2026, 06:03167,690-4
28 Aug 2026, 01:16167,694+5
27 Aug 2026, 05:27167,689no change
27 Aug 2026, 02:54167,689+61
26 Aug 2026, 03:01167,628-17
25 Aug 2026, 23:36167,645-23
25 Aug 2026, 06:03167,668no change
24 Aug 2026, 22:25167,668+13
24 Aug 2026, 07:49167,655-77
23 Aug 2026, 06:23167,732+4
22 Aug 2026, 14:54167,728-55
21 Aug 2026, 18:19167,783+17
21 Aug 2026, 08:23167,766-24
20 Aug 2026, 18:53167,790-30
20 Aug 2026, 11:42167,820+36
19 Aug 2026, 15:23167,784first reading

Engagement

53 posts held, back to 24 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 54 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
69.1%
avg views ÷ 167,735 subscribers
Avg views / post
116,000
42 posts measured
Reaction rate
0.991%
reactions ÷ views · ER floor
Posts in window
42
of 53 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 29 August 2026
Posts held53 (24 July 202629 August 2026)
Views total4,868,500
Reactions total48,240
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken30 Aug 2026, 02:11 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.

Reaction mix

59,758 reactions across 53 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍59,758100.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 53 of the 53 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 59,758reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

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

Telegram Stars

Stars received
357
across the posts below
Posts paid on
40
of 53 we hold a reading for · 75%
Most on one post
242
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @ProxyFreeMTProto. 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 53 most recent posts we hold for this entry, published 24 July 2026 to 29 August 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 Aug 2026, 10:46 UTC≈30,200 views642 reactions2 Starsread 30 August 2026

Server: ultima.telehelp.top Port: 443 Secret: eedffa323b22e7ab155f9806c3c9629f8c756c74696d612e74656c6568656c702e746f70 @TeleHelp

👍642

28 Aug 2026, 11:03 UTC≈46,800 views800 reactionsread 30 August 2026

Server: link.telehelp.top Port: 443 Secret: ee243af7382f8853a59265ac6dd3aa39a26c696e6b2e74656c6568656c702e746f70 @TeleHelp

👍800

27 Aug 2026, 15:47 UTC≈55,300 views829 reactionsread 30 August 2026

Server: medium.telehelp.top Port: 443 Secret: eeea7500a9c0f0ea17067f675842aeb1cb6d656469756d2e74656c6568656c702e746f70 @TeleHelp

👍829

27 Aug 2026, 06:33 UTC≈60,900 views900 reactions1 Starread 30 August 2026

Server: elite.telehelp.top Port: 443 Secret: eece53761a75bac14ee003070656d8304664726976652e676f6f676c652e636f6d @TeleHelp

👍900

26 Aug 2026, 07:25 UTC≈74,400 views1,080 reactions3 Starsread 30 August 2026

Server: ultima.telehelp.top Port: 443 Secret: eedffa323b22e7ab155f9806c3c9629f8c756c74696d612e74656c6568656c702e746f70 @TeleHelp

👍1,080

25 Aug 2026, 15:25 UTC≈78,500 views535 reactions3 Starsread 30 August 2026

Друзья, небольшое напоминание от команды! Напоминаем: если хотите забыть про нестабильное соединение раз и навсегда — у нас есть для Вас личный приватный прокси. Только Ваш сервер, только Ваше соединение. Безлимитный трафик, максимальная скорость и полная стабильность — независимо от чего либо. Попробуйте — мы уверены, что вам понравится. Получить личный прокси: @TGProxyPayBot Спасибо, что с нами 🤝 @TeleHelp

👍535

25 Aug 2026, 11:16 UTC≈70,400 views1,010 reactions1 Starread 30 August 2026

Server: link.telehelp.top Port: 443 Secret: ee243af7382f8853a59265ac6dd3aa39a26c696e6b2e74656c6568656c702e746f70 @TeleHelp

👍1,010

25 Aug 2026, 06:31 UTC≈77,100 views997 reactionsread 30 August 2026

Server: boost.telehelp.top Port: 443 Secret: eed4f42b03cae4d1a0f2e2a51454a6e0d7626f6f73742e74656c6568656c702e746f70 @TeleHelp

👍997

24 Aug 2026, 14:17 UTC≈84,300 views1,020 reactions1 Starread 30 August 2026

Server: fleet.telehelp.top Port: 443 Secret: ee77bbf78a169e505b117bc2c1df39463d666c6565742e74656c6568656c702e746f70 @TeleHelp

👍1,020

24 Aug 2026, 08:36 UTC≈85,300 views1,020 reactions1 Starread 30 August 2026

Server: ultima.telehelp.top Port: 443 Secret: eedffa323b22e7ab155f9806c3c9629f8c756c74696d612e74656c6568656c702e746f70 @TeleHelp

👍1,020

23 Aug 2026, 09:39 UTC≈89,300 views1,010 reactions10 Starsread 30 August 2026

Server: link.telehelp.top Port: 443 Secret: ee243af7382f8853a59265ac6dd3aa39a26c696e6b2e74656c6568656c702e746f70 @TeleHelp

👍1,010

20 Aug 2026, 06:24 UTC≈131,000 views1,080 reactionsread 30 August 2026

Server: cdn.telehelp.top Port: 443 Secret: ee4f3308bc6f67badccc790bf30f15f3de63646e2e74656c6568656c702e746f70 @TeleHelp

👍1,080

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Citation-graph rank

Citation-graph rank — 281,172 of 1,626,884entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

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

“Telеgram Prоxy MTProto” (@ProxyFreeMTProto), 167,735 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/ProxyFreeMTProto.

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.