Channel
@opsproxy
On this record: Growth · Engagement · What this channel posts · Posts · Telegram's recommendations · Cite this entry
3,638subscribers
-2 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002233165133 |
|---|---|
| Type | Channel |
| Username | @opsproxy |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/opsproxy |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 19:08 | 3,638 | -2 |
| 11 Aug 2026, 19:01 | 3,640 | first reading |
20 posts held, back to 20 January 2025 — 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 27 January 2026. An engagement rate over an empty window would be a number about nothing.
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.
vless://7e58699f-1d5d-4f6b-b181-cb74f0ad9509@172.64.152.23:443?path=%2F&security=tls&encryption=none&host=FvQy2FtKx8.SmArTtEcHzAaL.iNfO&type=ws&sni=FvQy2FtKx8.SmArTtEcHzAaL.iNfO#%40opsproxy%20%2311%23 vless://7e58699f-1d5d-4f6b-b181-cb74f0ad9509@172.64.152.23:443?path=%2F&security=tls&encryption=none&host=S56kTlFyZn.SmArTtEcHzAaL.iNfO&type=ws&sni=S56kTlFyZn.SmArTtEcHzAaL.iNfO#%40opsproxy%20*3* vless://7e58699f-…
Signed ☝️_𝐒𝐚𝐣𝐣𝐚𝐝
پروکسیا وصلن همشون همراه اول بهتر جواب میده پروکسی | پروکسی | پروکسی پروکسی | پروکسی | پروکسی پروکسی | پروکسی | پروکسی
Signed ☝️_𝐒𝐚𝐣𝐣𝐚𝐝
تمام نت ها | تمامی نت ها تمامی نت ها ایرانسل | ایرانسل | ایرانسل | ایرانسل همراه | همراه | همراه | همراه رایتل | رایتل | رایتل
Signed ☝️_𝐒𝐚𝐣𝐣𝐚𝐝
تست کنید ایرانسل وصله vless://c243a123-c6ca-4115-a955-3ddce53e257d@8.6.112.0:443?encryption=none&security=tls&sni=fuchsia.qzz.io&insecure=0&allowInsecure=0&type=ws&host=fuchsia.qzz.io&path=%2F188.132.192.194%3D2053#@opsproxy vless://6131ec27-8eed-4af9-9f8e-a0629775f6d6@162.159.152.4:443?path=%2F65.109.211.85%3D2053&security=tls&encryption=none&host=floralwhite.qzz.io&type=ws&sni=floralwhite.qzz.io#@opsproxy vless:…
Signed ☝️_𝐒𝐚𝐣𝐣𝐚𝐝
ایرانسل
Signed ☝️_𝐒𝐚𝐣𝐣𝐚𝐝
vless://f2aa0f74-e70c-4811-b2b2-2ced9a11adce@8.6.112.0:443?path=%2F193.23.197.183%3D443&security=tls&encryption=none&host=vermilion.qzz.io&fp=chrome&type=ws&sni=vermilion.qzz.io#@opsproxy vless://9074dcfa-dc3d-4922-9df5-5bda8c5c2999@top.imlast2.com:443?path=eyJqdW5rIjoiNHd0UE9oNTRBIiwicHJvdG9jb2wiOiJ2bCIsIm1vZGUiOiJwcm94eWlwIiwicGFuZWxJUHMiOltdfQ%3D%3D%3Fed%3D2560&security=tls&alpn=h3%2Ch2%2Chttp%2F1.1&encryption=no…
Signed ☝️_𝐒𝐚𝐣𝐣𝐚𝐝
Video, posted without a caption
Signed ☝️_𝐒𝐚𝐣𝐣𝐚𝐝
همراه
Signed سجاد
https://t.me/proxy?server=62.60.178.94&port=9741&secret=ee0000f00f0f775555fffffff5006e2e696d656469612e737465616d706f77657265642e636f6d https://t.me/proxy?server=62.60.178.96&port=9741&secret=ee0000f00f0f775555fffffff5006e2e696d656469612e737465616d706f77657265642e636f6d https://t.me/proxy?server=62.60.178.89&port=9741&secret=ee0000f00f0f775555fffffff5006e2e696d656469612e737465616d706f77657265642e636f6d https://t.me…
Signed سجاد
همراه اول وصله
Signed سجاد
https://t.me/proxy?server=62.60.177.70&port=343&secret=FgMBAgABAAfwAwOG4kw63QAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA https://t.me/proxy?server=62.60.177.71&port=343&secret=FgMBAgABAAfwAwOG4kw63QAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA https://t.me/proxy?server=62.60.177.150&port=9741&secret=ee0000f00f0f775555fffffff5006e2e696d656469612e737465616d706f77657265642e636f6d https://t.me/proxy?server=62.60.177.73&port=343&secret=FgMBAg…
Signed سجاد
پروکسی | پروکسی | پروکسی پروکسی | پروکسی | پروکسی پروکسی | پروکسی | پروکسی پروکسی | پروکسی | پروکسی
Signed ☝️_𝐒𝐚𝐣𝐣𝐚𝐝
Showing the 12 most recent of 20 posts we hold for @opsproxy. 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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“اوپس پروکسی | پروکسی | ایران پروکسی | فیلتر شکن | OPSPROXY | IRAN PROXY | اوپس پروکسی” (@opsproxy), 3,638 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/opsproxy.
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.