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

Channel

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

@TProxyRU

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

1,462,159subscribers

+112,330 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 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live29 August 2026
Measurements held21
Confirmed unchanged1 time, most recently 29 August 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,462,1591,405,9946 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 subscribers6 August 202629 August 2026
21 measurements spanning 23 days, net +112,330. 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,332,980–1,479,009 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 21
Measured (UTC)SubscribersChange
29 Aug 2026, 06:251,462,159+7,358
28 Aug 2026, 05:481,454,801+2,417
27 Aug 2026, 05:241,452,384+2,231
26 Aug 2026, 07:131,450,153+1,488
25 Aug 2026, 05:391,448,665+2,117
24 Aug 2026, 02:341,446,548+4,780
22 Aug 2026, 08:351,441,768+8,061
20 Aug 2026, 22:041,433,707+15,355
19 Aug 2026, 19:551,418,352+10,183
18 Aug 2026, 19:371,408,169+6,888
17 Aug 2026, 18:051,401,281+3,901
16 Aug 2026, 15:461,397,380+4,458
14 Aug 2026, 21:041,392,922-1,356
13 Aug 2026, 13:171,394,278+3,340
12 Aug 2026, 11:061,390,938+2,639
11 Aug 2026, 08:431,388,299+4,470
10 Aug 2026, 09:351,383,829+792
9 Aug 2026, 10:011,383,037+1,867
8 Aug 2026, 08:111,381,170+6,124
7 Aug 2026, 07:521,375,046first reading

Engagement

592 posts held, back to 5 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 52 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
7.83%
avg views ÷ 1,462,159 subscribers
Avg views / post
114,000
592 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
592
of 592 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 87 of 592 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 30 August 2026
Posts held592 (5 August 202630 August 2026)
Views total67,770,940
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken30 Aug 2026, 04:54 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

Lifetime counters from Telegram’s own channel header, read 29 August 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 567 of this channel’s own posts over the last 30 days (9 of the 24-hour readings behind this are interpolated, not measured directly): across 545of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 4.3 hours of being posted; a typical post has already reached 26.1% of its 24-hour view count within the first hour, and 69.9% within the first six; the median 24-hour reach across those posts is 92,000 views6.29% of this channel’s own subscriber count (90th percentile 111,000).

8 most recently posted, with a view-velocity reading
PostReadingsLatest readingCurve24h reachHalf of last-observed views by
/320830 Aug 2026, 04:30 UTC124 minutes24 minutes old6,240 views ~no reaction readingno checkpoint reading yetnot yet at 24hnot measurable yet
/320729 Aug 2026, 20:28 UTC178 minutes8.4 hours old51,500 views ~0 reactions60 minutes: 17,211 interp.3.0 hours: 30,0006.0 hours: 39,600still climbing at last readingnot yet at 24h2.1 hoursprovisional — final view count still climbing
/320629 Aug 2026, 19:30 UTC192 minutes9.4 hours old61,800 views ~0 reactions60 minutes: 20,095 interp.3.0 hours: 38,268 interp.6.0 hours: 48,600still climbing at last readingnot yet at 24h1.9 hoursprovisional — final view count still climbing
/320529 Aug 2026, 19:00 UTC1932 minutes9.9 hours old63,700 views ~no reaction reading60 minutes: 22,2003.0 hours: 40,749 interp.6.0 hours: 51,200still climbing at last readingnot yet at 24h1.8 hoursprovisional — final view count still climbing
/320429 Aug 2026, 18:30 UTC2027 minutes10 hours old63,000 views ~no reaction reading60 minutes: 23,1003.0 hours: 41,488 interp.6.0 hours: 51,400still climbing at last readingnot yet at 24h1.7 hoursprovisional — final view count still climbing
/320329 Aug 2026, 17:30 UTC2226 minutes11 hours old66,600 views ~no reaction reading60 minutes: 21,221 interp.3.0 hours: 44,7006.0 hours: 55,50012 hours: 66,600still climbing at last readingnot yet at 24h1.8 hoursprovisional — final view count still climbing
/320229 Aug 2026, 16:30 UTC2327 minutes12 hours old64,200 views ~no reaction reading60 minutes: 20,350 interp.3.0 hours: 45,2006.0 hours: 55,80012 hours: 62,900still climbing at last readingnot yet at 24h1.8 hoursprovisional — final view count still climbing
/320129 Aug 2026, 15:30 UTC2422 minutes13 hours old65,100 views ~no reaction reading60 minutes: 19,342 interp.3.0 hours: 43,2006.0 hours: 58,40012 hours: 63,400still climbing at last readingnot yet at 24h2.0 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 viewsis 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
378
across the posts below
Posts paid on
65
of 592 we hold a reading for · 11%
Most on one post
56
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 592 most recent posts we hold for this entry, published 5 August 2026 to 30 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

30 Aug 2026, 04:30 UTC≈6,240 viewsread 30 August 2026

Server: travokur.su Port: 443 Secret: ee48b53faf26aaa233c69bb645954c9a3f747261766f6b75722e7375 @TProxyRU

29 Aug 2026, 20:28 UTC≈51,500 views0 reactionsread 30 August 2026

Server: 51.250.81.95 Port: 443 Secret: eeca9d1ff80c1c1758dc115b7b9a90b7a76d6564626c6f636b2e666974 @TProxyRU

29 Aug 2026, 19:30 UTC≈61,800 views0 reactionsread 30 August 2026

Server: grid.lovely.lat Port: 443 Secret: eeec835a34516912f161a0073339be3c64677269642e6c6f76656c792e6c6174 @TProxyRU

29 Aug 2026, 19:00 UTC≈63,700 viewsread 30 August 2026

Server: beest-sellerst.co.uk. Port: 443 Secret: eef0eeb0bd9adc4fd4a93994ee3b2a216b63646e2e79656b74616e65742e636f6d 🇷🇺 @TProxyRU

29 Aug 2026, 18:30 UTC≈63,000 viewsread 30 August 2026

Server: ardesvpn1.ru Port: 8443 Secret: ee05cf8e164f926f4a664b2404d276a1d6617264657376706e312e7275 @TProxyRU

29 Aug 2026, 17:30 UTC≈66,600 viewsread 30 August 2026

Server: forever.startnetwork.shop Port: 443 Secret: dd0ef5f4a09c2e33527338e9184a9a6178 @TProxyRU

29 Aug 2026, 16:30 UTC≈64,200 viewsread 30 August 2026

Server: api2.kvakzon.top Port: 443 Secret: eef6cce71eb4d775d3d908fef1301395b5617069322e6b76616b7a6f6e2e746f70 @TProxyRU

29 Aug 2026, 15:30 UTC≈65,100 viewsread 30 August 2026

Server: 51.250.81.95 Port: 443 Secret: eeca9d1ff80c1c1758dc115b7b9a90b7a76d6564626c6f636b2e666974 @TProxyRU

29 Aug 2026, 14:30 UTC≈67,000 viewsread 30 August 2026

Server: telegram.vechnostnet.study Port: 443 Secret: dda8736bb4a03afabc3ebf6b8565400dfc @TProxyRU

29 Aug 2026, 13:30 UTC≈69,400 viewsread 30 August 2026

Server: lazeyka-29.getvelora.space Port: 443 Secret: ee41b9fb69fc7c451449031106d3dd516c6f7a6f6e2e7275 @TProxyRU

29 Aug 2026, 12:30 UTC≈70,400 viewsread 30 August 2026

Server: proxy.lodkirmm.ru Port: 8443 Secret: ee16309abd572d284b309ef26bd7a3f68570726f78792e6c6f646b69726d6d2e7275 @TProxyRU

29 Aug 2026, 12:06 UTC≈67,900 views0 reactions2 Starsread 30 August 2026

Server: Hel-hi.co.uk. Port: 443 Secret: eef0eeb0bd9adc4fd4a93994ee3b2a216b63646e2e79656b74616e65742e636f6d 🇷🇺 @TProxyRU

Showing the 12 most recent of 592 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.

Citation-graph rank

Citation-graph rank — 358,330 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.

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

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

“Proxy MTProto | Прокси 24/7 | پروکسی” (@TProxyRU), 1,462,159 subscribers as measured 29 August 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.