5 May 2025, 12:18 UTC≈1,410 views0 reactionsread 27 August 2026
❴Orv❴ • Country: France • IP: 77.221.153.93 • Port: 8443 proxy~config~bot~support
Channel
Orv Proxy
@Orv_Proxy
On this record: Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
301subscribers
-5 since we began measuring on 27 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002004073794 |
|---|---|
| Type | Channel |
| Username | @Orv_Proxy |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 27 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 12 September 2026 |
| On Telegram | t.me/Orv_Proxy |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Sept 2026, 08:20 | 301 | -4 |
| 28 Aug 2026, 04:23 | 305 | -1 |
| 27 Aug 2026, 08:30 | 306 | no change |
| 27 Aug 2026, 08:15 | 306 | first reading |
Engagement
20 posts held, back to 5 May 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 page of 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 5 May 2025. An engagement rate over an empty window would be a number about nothing.
Recent posts
5 May 2025, 11:37 UTC≈1,200 viewsread 27 August 2026
❴Orv❴ • Country: The Netherlands • IP: 9.9.9.9.lll-lll..etc • Port: 443 proxy~config~bot~support
5 May 2025, 11:20 UTC≈1,160 views0 reactionsread 27 August 2026
❴Orv❴ • Country: The Netherlands • IP: 195.62.32.218 • Port: 8443 proxy~config~bot~support
5 May 2025, 09:57 UTC976 viewsread 27 August 2026
❴Orv❴ • Country: Turkey • IP: 78.135.93.222 • Port: 443 proxy~config~bot~support
5 May 2025, 09:55 UTC724 viewsread 27 August 2026
❴Orv❴ • Country: Germany • IP: gerto.mumntum.ir • Port: 443 proxy~config~bot~support
5 May 2025, 09:55 UTC540 viewsread 27 August 2026
❴Orv❴ • Country: Germany • IP: gertree.mumntum..etc • Port: 2083 proxy~config~bot~support
5 May 2025, 09:52 UTC412 viewsread 27 August 2026
❴Orv❴ • Country: The Netherlands • IP: holto.tinkpad.ir • Port: 2046 proxy~config~bot~support
5 May 2025, 09:52 UTC358 viewsread 27 August 2026
❴Orv❴ • Country: Germany • IP: gerfor.sharhrnan.etc • Port: 2096 proxy~config~bot~support
5 May 2025, 09:52 UTC266 viewsread 27 August 2026
❴Orv❴ • Country: Germany • IP: gertoo.mumntum.i.etc • Port: 443 proxy~config~bot~support
5 May 2025, 09:49 UTC237 viewsread 27 August 2026
❴Orv❴ • Country: The Netherlands • IP: holtre.tinkpad.i.etc • Port: 2088 proxy~config~bot~support
5 May 2025, 09:49 UTC213 viewsread 27 August 2026
❴Orv❴ • Country: Germany • IP: geronee.mumntum..etc • Port: 2053 proxy~config~bot~support
5 May 2025, 09:49 UTC207 viewsread 27 August 2026
❴Orv❴ • Country: The Netherlands • IP: holtoo.tinkpad.i.etc • Port: 2046 proxy~config~bot~support
Showing the 12 most recent of 20 posts we hold for @Orv_Proxy. 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.
Mentions
Names
Channels on the register whose handles appear in this channel's posts.
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.
Appears in Telegram’s recommendations for other channels
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.
فیلترشکن نیم بها | Abc Cloud
@Abc_Cloud · 112,894
Telegram ranks this channel #40 of 41 here — alongside 40 others — read 27 August 2026
@Abc_Cloud · 112,894
Telegram ranks this channel #40 of 41 here — alongside 40 others — read 27 August 2026
ArashVPN
@arash_vpn · 65,520
Telegram ranks this channel #58 of 60 here — alongside 59 others — read 14 September 2026
@arash_vpn · 65,520
Telegram ranks this channel #58 of 60 here — alongside 59 others — read 14 September 2026
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 5 September 2026 — this entry's latest reading, not the date you are reading this.
“Orv Proxy” (@Orv_Proxy), 301 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/Orv_Proxy.
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.