Channel
@MTPUpdate
On this record: Growth · Engagement · Posts · Cite this entry
429subscribers
-3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001586895363 |
|---|---|
| Type | Channel |
| Username | @MTPUpdate |
| Created | Between 1 August 2021 and 19 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 23 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 23 August 2026 |
| On Telegram | t.me/MTPUpdate |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 23 Aug 2026, 00:39 | 429 | -4 |
| 15 Aug 2026, 17:17 | 433 | +1 |
| 7 Aug 2026, 23:38 | 432 | no change |
| 7 Aug 2026, 00:47 | 432 | first reading |
20 posts held, back to 19 February 2023 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 19 February 2023. An engagement rate over an empty window would be a number about nothing.
——————————————— The Best MTProto Proxies ——————————————— Server: 3.***.*.190 Port: 443 Secret:** eec222a2b2f2211ac1ff8465eef8e625e46d792e736861706172616b2e6972 ——————————————— The Best Proxy Channel ———————————————
——————————————— The Best MTProto Proxies ——————————————— Server: 35.***.*.181 Port: 443 Secret:** eec222a2b2f2211ac1ff8465eef8e625e46d792e736861706172616b2e6972 ——————————————— The Best Proxy Channel ———————————————
——————————————— The Best MTProto Proxies ——————————————— Server: 3.***.*.169 Port: 443 Secret:** eec222a2b2f2211ac1ff8465eef8e625e46d792e736861706172616b2e6972 ——————————————— The Best Proxy Channel ———————————————
——————————————— The Best MTProto Proxies ——————————————— Server: 34.***.*.165 Port: 443 Secret:** eec222a2b2f2211ac1ff8465eef8e625e46d792e736861706172616b2e6972 ——————————————— The Best Proxy Channel ———————————————
——————————————— The Best MTProto Proxies ——————————————— Server: 54.***.*.237 Port: 443 Secret:** eec222a2b2f2211ac1ff8465eef8e625e46d792e736861706172616b2e6972 ——————————————— The Best Proxy Channel ———————————————
——————————————— The Best MTProto Proxies ——————————————— Server: 3.***.*.169 Port: 443 Secret:** eec222a2b2f2211ac1ff8465eef8e625e46d792e736861706172616b2e6972 ——————————————— The Best Proxy Channel ———————————————
——————————————— The Best MTProto Proxies ——————————————— Server: 35.***.*.170 Port: 443 Secret:** eec222a2b2f2211ac1ff8465eef8e625e46d792e736861706172616b2e6972 ——————————————— The Best Proxy Channel ———————————————
——————————————— The Best MTProto Proxies ——————————————— Server: 54.***.*.199 Port: 443 Secret:** eec222a2b2f2211ac1ff8465eef8e625e46d792e736861706172616b2e6972 ——————————————— The Best Proxy Channel ———————————————
——————————————— The Best MTProto Proxies ——————————————— Server: 100.***.*.228 Port: 443 Secret:** eec222a2b2f2211ac1ff8465eef8e625e46d792e736861706172616b2e6972 ——————————————— The Best Proxy Channel ———————————————
——————————————— The Best MTProto Proxies ——————————————— Server: 3.***.*.161 Port: 443 Secret:** eec222a2b2f2211ac1ff8465eef8e625e46d792e736861706172616b2e6972 ——————————————— The Best Proxy Channel ———————————————
——————————————— The Best MTProto Proxies ——————————————— Server: 34.***.*.112 Port: 443 Secret:** eec222a2b2f2211ac1ff8465eef8e625e46d792e736861706172616b2e6972 ——————————————— The Best Proxy Channel ———————————————
——————————————— The Best MTProto Proxies ——————————————— Server: 18.***.*.255 Port: 443 Secret:** eec222a2b2f2211ac1ff8465eef8e625e46d792e736861706172616b2e6972 ——————————————— The Best Proxy Channel ———————————————
Showing the 12 most recent of 20 posts we hold for @MTPUpdate. 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.
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 23 August 2026 — this entry's latest reading, not the date you are reading this.
“MTProxy Update” (@MTPUpdate), 429 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/MTPUpdate.
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.