Telegram RegisterThe public register of Telegram

Channel

MTProto Proxies

@mtproto_mtproxy

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry

2,925subscribers

+0 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001268978748
TypeChannel
Username@mtproto_mtproxy
DescriptionCollection of MTProto Proxies for Telegram MTProto proxy bot @proxy_service_bot Create MTProto proxy @myMTProxy_bot
CreatedBetween 1 March 2018 and 5 June 2018— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live10 August 2026
Measurements held2
Confirmed unchanged2 times, most recently 10 August 2026
On Telegramt.me/mtproto_mtproxy

Growth

2,9256 Aug 2026, 17:16 — 2,925 subscribers7 Aug 2026, 13:53 — 2,925 subscribers6 Aug 2026, 17:167 Aug 2026, 13:53
2 measurements taken within a single day. 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 2,922–2,928 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 13:532,925no change
6 Aug 2026, 17:162,925first reading

Engagement

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

What this channel posts

Links
16

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

Recent posts

15 Oct 2021, 19:34 UTCviews —

The account of the user that owns this channel has been inactive for the last 1 month. If it remains inactive in the next 8 days, that account will self-destruct and this channel will no longer have an owner.

26 Jun 2018, 19:49 UTC≈139,000 viewsread 7 August 2026

New MTProto proxies 🚀. Issued randomly. Go to start 👉 @proxy_service_bot

21 Jun 2018, 16:07 UTCviews —

MTProto Proxies pinned «You can take MTProxy from @proxy_service_bot You can create MTProxy by @myMTProxy_bot Взять MTProxy вы можете у бота @proxy_service_bot Создать свой MTProxy вы можете у бота @myMTProxy_bot»

21 Jun 2018, 16:07 UTC≈128,000 viewsread 7 August 2026

You can take MTProxy from @proxy_service_bot You can create MTProxy by @myMTProxy_bot Взять MTProxy вы можете у бота @proxy_service_bot Создать свой MTProxy вы можете у бота @myMTProxy_bot

21 Jun 2018, 07:00 UTC≈125,000 viewsread 7 August 2026

____ MTProto Proxy by @myMTProxy_bot (sponsor @teleblog_eng) https://t.me/proxy?server=185.254.188.78&port=1754&secret=5ddee8e14d4583af36235d5d1c84afea Click on the link ⬆️

20 Jun 2018, 10:07 UTC≈79,600 viewsread 7 August 2026

____ MTProto Proxy by @myMTProxy_bot (sponsor @tyan_wine) https://t.me/proxy?server=179.43.147.205&port=5561&secret=dbb5b431ff020a749f0b1c0fbb8762a5 Click on the link ⬆️

19 Jun 2018, 19:06 UTC≈49,400 viewsread 7 August 2026

____ MTProto Proxy by @myMTProxy_bot (sponsor @MoscowSecrets) https://t.me/proxy?server=185.254.188.9&port=8885&secret=d44ab08f3ab8fb51ca738493b43de460 Click on the link ⬆️

19 Jun 2018, 19:05 UTC≈37,900 viewsread 7 August 2026

____ MTProto Proxy by @myMTProxy_bot (sponsor @dailysales) https://t.me/proxy?server=185.197.75.177&port=5332&secret=80a58db67dfe23050f2875547ff35bfe Click on the link ⬆️

19 Jun 2018, 19:04 UTC≈30,300 viewsread 7 August 2026

____ MTProto Proxy by @myMTProxy_bot (sponsor @sysoevfm) https://t.me/proxy?server=185.197.75.127&port=3511&secret=c0b178151885055e2289c65a985aa648 Click on the link ⬆️

19 Jun 2018, 19:04 UTC≈24,400 viewsread 7 August 2026

____ MTProto Proxy by @myMTProxy_bot (sponsor @Crypto_Soros) https://t.me/proxy?server=185.197.75.45&port=2311&secret=4f2891982e572cb8c36b60b490ea4e80 Click on the link ⬆️

19 Jun 2018, 19:03 UTC≈20,800 viewsread 7 August 2026

____ MTProto Proxy by @myMTProxy_bot (sponsor @extractTS) https://t.me/proxy?server=141.255.167.111&port=3511&secret=bec8edf692107a5bc5f0d7b8e89ddb1e Click on the link ⬆️

19 Jun 2018, 19:02 UTC≈18,700 viewsread 7 August 2026

____ MTProto Proxy by @myMTProxy_bot (sponsor @FittnesGirl) https://t.me/proxy?server=46.19.137.141&port=3124&secret=d84b64a7299058449a3ef5b52e409590 Click on the link ⬆️

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

Citation-graph rank

Citation-graph rank — 1,121,906 of 1,151,006entries 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 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“MTProto Proxies” (@mtproto_mtproxy), 2,925 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/mtproto_mtproxy.

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.