2344 #HTTPS 2082 #Socks4 1517 #Socks5

Channel
Раздача прокси | HTTP / HTTPS / Socks 4 / Socks 5 proxies
@wproxies
On this record: Topic · Growth · Engagement · Posts · Cite this entry
2,267subscribers
+67 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001262552503 |
|---|---|
| Type | Channel |
| Username | @wproxies |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/wproxies |
Topic
Hacking & security — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 16 September 2026 and assigned it the closest of 31 fixed categories, at 69% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Oct 2026, 14:16 | 2,267 | +1 |
| 5 Oct 2026, 21:55 | 2,266 | +27 |
| 28 Sept 2026, 23:18 | 2,239 | +5 |
| 18 Sept 2026, 16:41 | 2,234 | -2 |
| 10 Sept 2026, 12:59 | 2,236 | -1 |
| 5 Sept 2026, 03:17 | 2,237 | +5 |
| 1 Sept 2026, 19:27 | 2,232 | +9 |
| 29 Aug 2026, 17:56 | 2,223 | +4 |
| 26 Aug 2026, 22:33 | 2,219 | +2 |
| 23 Aug 2026, 20:54 | 2,217 | -9 |
| 20 Aug 2026, 13:53 | 2,226 | -3 |
| 17 Aug 2026, 20:54 | 2,229 | +6 |
| 14 Aug 2026, 17:57 | 2,223 | +8 |
| 11 Aug 2026, 10:05 | 2,215 | +7 |
| 8 Aug 2026, 09:40 | 2,208 | +8 |
| 7 Aug 2026, 14:33 | 2,200 | no change |
| 7 Aug 2026, 13:02 | 2,200 | first reading |
Engagement
7 posts held, back to 6 August 2026 — 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 7 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
3111 #HTTPS 2636 #Socks4 2064 #Socks5
3485 #HTTPS 2747 #Socks4 2181 #Socks5
2741 #HTTPS 2547 #Socks4 1932 #Socks5
2721 #HTTPS 2547 #Socks4 1930 #Socks5
2969 #HTTPS 2550 #Socks4 1983 #Socks5
2853 #HTTPS 2596 #Socks4 1993 #Socks5
Showing the 7 most recent of 7 posts we hold for @wproxies. 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 12 October 2026 — this entry's latest reading, not the date you are reading this.
“Раздача прокси | HTTP / HTTPS / Socks 4 / Socks 5 proxies” (@wproxies), 2,267 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/wproxies.
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.