Telegram RegisterThe public register of Telegram
Telegram profile photo for Proxy MTProto | Прокси 24/7 | پروکسی

Channel

Proxy MTProto | Прокси 24/7 | پروکسی

@TProxyRU

Not marked by Telegram, checked 4 September 2026

On this record: Topic · Growth · Engagement · What this channel posts · View velocity · Stars · Posts · Citations · Cite this entry

1,529,300subscribers

+179,471 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among the largest entries.

Register entry

Telegram ID-1003825654813
TypeChannel
Username@TProxyRU
DescriptionПрокси всегда на связи ⚡ ADS: @Uoramir
CreatedBetween 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live18 October 2026
Measurements held41
Confirmed unchanged1 time, most recently 18 October 2026
On Telegramt.me/TProxyRU

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 62% 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

1,349,8291,665,1241,507,476.56 August 2026 — 1,349,829 subscribers7 August 2026 — 1,375,046 subscribers8 August 2026 — 1,381,170 subscribers9 August 2026 — 1,383,037 subscribers10 August 2026 — 1,383,829 subscribers11 August 2026 — 1,388,299 subscribers12 August 2026 — 1,390,938 subscribers13 August 2026 — 1,394,278 subscribers14 August 2026 — 1,392,922 subscribers16 August 2026 — 1,397,380 subscribers17 August 2026 — 1,401,281 subscribers18 August 2026 — 1,408,169 subscribers19 August 2026 — 1,418,352 subscribers20 August 2026 — 1,433,707 subscribers22 August 2026 — 1,441,768 subscribers24 August 2026 — 1,446,548 subscribers25 August 2026 — 1,448,665 subscribers26 August 2026 — 1,450,153 subscribers27 August 2026 — 1,452,384 subscribers28 August 2026 — 1,454,801 subscribers29 August 2026 — 1,462,159 subscribers30 August 2026 — 1,476,315 subscribers31 August 2026 — 1,485,292 subscribers1 September 2026 — 1,491,471 subscribers2 September 2026 — 1,501,265 subscribers3 September 2026 — 1,507,325 subscribers6 September 2026 — 1,520,685 subscribers9 September 2026 — 1,561,660 subscribers11 September 2026 — 1,602,830 subscribers13 September 2026 — 1,620,955 subscribers15 September 2026 — 1,640,176 subscribers17 September 2026 — 1,665,124 subscribers26 September 2026 — 1,625,258 subscribers4 October 2026 — 1,583,531 subscribers9 October 2026 — 1,565,684 subscribers13 October 2026 — 1,548,292 subscribers14 October 2026 — 1,543,573 subscribers15 October 2026 — 1,540,613 subscribers16 October 2026 — 1,536,318 subscribers17 October 2026 — 1,533,070 subscribers18 October 2026 — 1,529,300 subscribers1,529,3006 August 202618 October 2026
41 measurements spanning 73 days, net +179,471. 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 1,302,535–1,712,418 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 41
Measured (UTC)SubscribersChange
18 Oct 2026, 15:581,529,300-3,770
17 Oct 2026, 14:001,533,070-3,248
16 Oct 2026, 16:161,536,318-4,295
15 Oct 2026, 13:181,540,613-2,960
14 Oct 2026, 16:181,543,573-4,719
13 Oct 2026, 09:591,548,292-17,392
9 Oct 2026, 06:371,565,684-17,847
4 Oct 2026, 17:551,583,531-41,727
26 Sept 2026, 22:161,625,258-39,866
17 Sept 2026, 10:161,665,124+24,948
15 Sept 2026, 11:201,640,176+19,221
13 Sept 2026, 18:571,620,955+18,125
11 Sept 2026, 22:381,602,830+41,170
9 Sept 2026, 09:401,561,660+40,975
6 Sept 2026, 02:571,520,685+13,360
3 Sept 2026, 18:571,507,325+6,060
2 Sept 2026, 07:351,501,265+9,794
1 Sept 2026, 08:051,491,471+6,179
31 Aug 2026, 09:371,485,292+8,977
30 Aug 2026, 08:221,476,315first reading

Engagement

1,776 posts held, back to 5 August 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 156 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
5.38%
avg views ÷ 1,529,300 subscribers
Avg views / post
82,300
716 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
716
of 1,776 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 156 of 716 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 19 October 2026
Posts held1,776 (5 August 2026 – 19 October 2026)
Views total58,911,120
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken19 Oct 2026, 04:45 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
3

Lifetime counters from Telegram’s own channel header, read 19 October 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.

View velocity

How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.

Computed from 617 of this channel’s own posts over the last 30 days (18 of the 24-hour readings behind this are interpolated, not measured directly): across 589 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 3.9 hours of being posted; a typical post has already reached 28.2% of its 24-hour view count within the first hour, and 72.1% within the first six; the median 24-hour reach across those posts is 69,100 views — 4.52% of this channel’s own subscriber count (90th percentile 77,800).

8 most recently posted, with a view-velocity reading
PostReadingsLatest readingCurve24h reachHalf of last-observed views by
/441719 Oct 2026, 04:30 UTC116 minutes – 16 minutes old5,220 views ~no reaction readingno checkpoint reading yetnot yet at 24hnot measurable yet
/441618 Oct 2026, 20:28 UTC1622 minutes – 8.3 hours old37,800 views ~no reaction reading60 minutes: 11,700 → 3.0 hours: 17,900 → 6.0 hours: 25,000still climbing at last readingnot yet at 24h3.5 hoursprovisional — final view count still climbing
/441518 Oct 2026, 20:00 UTC1716 minutes – 8.8 hours old41,900 views ~no reaction reading60 minutes: 14,948 interp. → 3.0 hours: 22,696 interp. → 6.0 hours: 28,700still climbing at last readingnot yet at 24h2.2 hoursprovisional — final view count still climbing
/441418 Oct 2026, 19:30 UTC1815 minutes – 9.3 hours old44,800 views ~0 reactions60 minutes: 17,243 interp. → 3.0 hours: 27,121 interp. → 6.0 hours: 32,200still climbing at last readingnot yet at 24h1.6 hoursprovisional — final view count still climbing
/441318 Oct 2026, 19:00 UTC1910 minutes – 9.8 hours old45,400 views ~no reaction reading60 minutes: 19,114 interp. → 3.0 hours: 30,392 interp. → 6.0 hours: 34,700still climbing at last readingnot yet at 24h79 minutesprovisional — final view count still climbing
/441218 Oct 2026, 18:30 UTC206 minutes – 10 hours old47,500 views ~0 reactions60 minutes: 19,752 interp. → 3.0 hours: 33,700 → 6.0 hours: 38,000still climbing at last readingnot yet at 24h78 minutesprovisional — final view count still climbing
/441118 Oct 2026, 17:30 UTC2135 minutes – 11 hours old52,400 views ~no reaction reading60 minutes: 19,385 interp. → 3.0 hours: 38,518 interp. → 6.0 hours: 44,000still climbing at last readingnot yet at 24h90 minutesprovisional — final view count still climbing
/441018 Oct 2026, 16:30 UTC235 minutes – 12 hours old54,600 views ~0 reactions60 minutes: 18,923 interp. → 3.0 hours: 40,412 interp. → 6.0 hours: 48,200 → 12 hours: 53,500still climbing at last readingnot yet at 24h1.6 hoursprovisional — final view count still climbing

Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed views is the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.

Telegram Stars

Stars received
805
across the posts below
Posts paid on
186
of 1,000 we hold a reading for · 19%
Most on one post
55
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @TProxyRU. 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 7 September 2026 to 19 October 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

19 Oct 2026, 04:30 UTC≈5,220 viewsread 19 October 2026

Server: cdn.flowaccess.site Port: 443 Secret: dd1924acaec2bb63dac896a6d02a382f38 @TProxyRU

18 Oct 2026, 20:28 UTC≈37,800 viewsread 19 October 2026

Server: edge.flowstreamhub.site Port: 443 Secret: dd8960b9810070b6dea7e1f7e2f564b461 @TProxyRU

18 Oct 2026, 20:00 UTC≈41,900 viewsread 19 October 2026

Server: jhndoes.co.uk. Port: 8443 Secret: eeNEgYdJvXrFGRMCIMJdCQ @TProxyRU

18 Oct 2026, 19:30 UTC≈44,800 views0 reactions1 Starread 19 October 2026

Server: relay.surfvpn.app Port: 443 Secret: eedf44a4347c1eb8938c7e63340bd1ca4972656c61792e7375726676706e2e617070 @TProxyRU

18 Oct 2026, 19:00 UTC≈45,400 viewsread 19 October 2026

Server: support.infinityhalo.co.uk. Port: 8443 Secret: eeNEgYdJvXrFGRMCIMJdCQ @TProxyRU

18 Oct 2026, 18:30 UTC≈47,500 views0 reactions1 Starread 19 October 2026

Server: relay.surfvpn.app Port: 443 Secret: eedf44a4347c1eb8938c7e63340bd1ca4972656c61792e7375726676706e2e617070 @TProxyRU

18 Oct 2026, 17:30 UTC≈52,400 viewsread 19 October 2026

Server: med-help-org.duckdns.org Port: 443 Secret: 77c1c3c07443157cfdd7cc026c405316 @TProxyRU

18 Oct 2026, 16:30 UTC≈54,600 views0 reactions1 Starread 19 October 2026

Server: tg.surfvpn.info Port: 443 Secret: eedf44a4347c1eb8938c7e63340bd1ca4972656c61792e7375726676706e2e617070 @TProxyRU

18 Oct 2026, 15:30 UTC≈56,700 viewsread 19 October 2026

Server: Suodbo.co.uk. Port: 443 Secret: eef0eeb0bd9adc4fd4a93994ee3b2a216b63646e2e79656b74616e65742e636f6d @TProxyRU

18 Oct 2026, 15:00 UTC≈56,000 viewsread 19 October 2026

Server: fbv9c.antitspu.com Port: 443 Secret: dd8d05cf0474c92f5951fb646f04621d09 @TProxyRU

18 Oct 2026, 14:30 UTC≈55,700 viewsread 19 October 2026

Server: web.arixo.shop Port: 443 Secret: dd27e57f496bbf279605f0198ea6d26067 🇷🇺 @TProxyRU

18 Oct 2026, 14:00 UTC≈55,200 viewsread 19 October 2026

Server: kak.hotstbvs.ru Port: 443 Secret: 19642a8b48eff48766d6f7f240209026 @TProxyRU

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

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 13 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.

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

“Proxy MTProto | Прокси 24/7 | پروکسی” (@TProxyRU), 1,529,300 subscribers as measured 18 October 2026. Telegram Register, tgregister.com/channel/TProxyRU.

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.