Telegram RegisterThe public register of Telegram
Telegram profile photo for پروكسي تلگرام / MTProto Proxies

Channel

پروكسي تلگرام / MTProto Proxies

@mtpproxies_telegram

On this record: Growth · Engagement · What this channel posts · Posts · Cite this entry

3,407subscribers

+6 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001296785211
TypeChannel
Username@mtpproxies_telegram
CreatedBetween 1 March 2018 and 20 October 2018— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live25 August 2026
Measurements held7
Confirmed unchanged2 times, most recently 25 August 2026
On Telegramt.me/mtpproxies_telegram

Growth

3,4013,4073,4046 August 2026 — 3,401 subscribers6 August 2026 — 3,401 subscribers9 August 2026 — 3,403 subscribers12 August 2026 — 3,402 subscribers16 August 2026 — 3,403 subscribers18 August 2026 — 3,401 subscribers22 August 2026 — 3,407 subscribers6 August 202622 August 2026
7 measurements spanning 16 days, net +6. 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 3,400–3,408 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 13:223,407+6
18 Aug 2026, 18:253,401-2
16 Aug 2026, 02:483,403+1
12 Aug 2026, 13:583,402-1
9 Aug 2026, 07:123,403+2
6 Aug 2026, 09:453,401no change
6 Aug 2026, 05:463,401first reading

Engagement

19 posts held, back to 20 October 2018the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pagesof 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 19 posts for this entry, the most recent from 2 February 2019. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
42s
Average length
42s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Recent posts

2 Feb 2019, 19:32 UTC≈51,900 viewsread 7 August 2026

https://t.me/proxy?server=imtproto.ddnsfree.com&port=2&secret=dd8b2394ad2ecef7e607d5f52b31a45768

27 Nov 2018, 18:59 UTC≈53,900 viewsread 7 August 2026

هميشه پروكسي هارو تست ميكنم ميزارم كه سرعت دانلودشون خوب باشه...

27 Nov 2018, 18:58 UTC≈53,800 viewsread 7 August 2026

https://t.me/proxy?server=81.4.122.218&port=2018&secret=dd56297f314a5b51b18ac0a8119da99265&@mtpproxies_telegram ‎بر روي لينك بالا كليك نماييد تا پروكسي براي شما فعال شود @mtpproxies_telegram

27 Nov 2018, 18:56 UTC≈41,200 viewsread 7 August 2026

https://t.me/proxy?server=159.69.189.238&port=80&secret=ddeee5a162b6783ce9952abd8a5c733ba3&@mtpproxies_telegram ‎بر روي لينك بالا كليك نماييد تا پروكسي براي شما فعال شود @mtpproxies_telegram

27 Nov 2018, 18:55 UTC≈35,500 viewsread 7 August 2026

https://t.me/proxy?server=7Stars.Digitalresistance.webredirect.org&port=1080&secret=f207f3a3ffd77b5b2ab874709d461e61&@mtpproxies_telegram ‎بر روي لينك بالا كليك نماييد تا پروكسي براي شما فعال شود @mtpproxies_telegram

27 Nov 2018, 18:49 UTC≈29,800 viewsread 7 August 2026

https://t.me/proxy?server=Danestani.mywire.org&port=1088&secret=dd00000000000000000000000000000000&@mtpproxies_telegram ‎بر روي لينك بالا كليك نماييد تا پروكسي براي شما فعال شود @mtpproxies_telegram

12 Nov 2018, 04:52 UTC≈29,500 viewsread 7 August 2026

https://t.me/proxy?server=194.99.23.246&port=443&secret=dd15aa74cc8d47d315e8eb584672e7beef&@mtpproxies_telegram ‎بر روي لينك بالا كليك نماييد تا پروكسي براي شما فعال شود @mtpproxies_telegram

6 Nov 2018, 10:43 UTC≈7,300 viewsread 7 August 2026

https://t.me/proxy?server=fast.mypi.co&port=433&secret=dde94eaeb3eab7e27960df8a68c1a2c7&@mtpproxies_telegram ‎بر روي لينك بالا كليك نماييد تا پروكسي براي شما فعال شود @mtpproxies_telegram

6 Nov 2018, 10:43 UTC≈6,040 viewsread 7 August 2026

https://t.me/proxy?server=mt-movafaghiyat.ml&port=8443&secret=d41d8cd98f08b204e9809998ecf9427c&@mtpproxies_telegram ‎بر روي لينك بالا كليك نماييد تا پروكسي براي شما فعال شود @mtpproxies_telegram

6 Nov 2018, 10:42 UTC≈15,300 viewsread 7 August 2026

https://t.me/proxy?server=ptc-channel-1.drproxy.club&port=1040&secret=dd8cd5ba18f66298152837413483cc23be&@mtpproxies_telegram ‎بر روي لينك بالا كليك نماييد تا پروكسي براي شما فعال شود @mtpproxies_telegram

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

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

“پروكسي تلگرام / MTProto Proxies” (@mtpproxies_telegram), 3,407 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/mtpproxies_telegram.

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.