Channel
RubikVpn|روبیک وی پی ان
@vpnrubik
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
9,764subscribers
-474 since we began measuring on 2 September 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001882031225 |
|---|---|
| Type | Channel |
| Username | @vpnrubik |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 2 September 2026 |
| Last confirmed live | 30 October 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 1 time, most recently 30 October 2026 |
| On Telegram | t.me/vpnrubik |
Topic
Other / unclassifiable — 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 92% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Oct 2026, 17:10 | 9,764 | -25 |
| 27 Oct 2026, 08:21 | 9,789 | -12 |
| 24 Oct 2026, 07:17 | 9,801 | -24 |
| 20 Oct 2026, 20:56 | 9,825 | -20 |
| 17 Oct 2026, 23:36 | 9,845 | -19 |
| 15 Oct 2026, 02:28 | 9,864 | -16 |
| 11 Oct 2026, 21:20 | 9,880 | -41 |
| 5 Oct 2026, 00:38 | 9,921 | -73 |
| 25 Sept 2026, 13:37 | 9,994 | -57 |
| 19 Sept 2026, 03:38 | 10,051 | -22 |
| 16 Sept 2026, 14:41 | 10,073 | -53 |
| 14 Sept 2026, 19:00 | 10,126 | -16 |
| 13 Sept 2026, 07:42 | 10,142 | -14 |
| 11 Sept 2026, 14:00 | 10,156 | -18 |
| 8 Sept 2026, 19:18 | 10,174 | -34 |
| 5 Sept 2026, 14:19 | 10,208 | -22 |
| 3 Sept 2026, 16:18 | 10,230 | -8 |
| 2 Sept 2026, 12:39 | 10,238 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind 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.
@v2rayargon · 19,269
Telegram ranks this channel #16 of 71 here — alongside 70 others — read 2 October 2026
@NETMelliAnti · 33,750
Telegram ranks this channel #19 of 39 here — alongside 38 others — read 2 September 2026
@V2rayi_net · 18,507
Telegram ranks this channel #27 of 37 here — alongside 36 others — read 5 October 2026
@v2ray_83 · 22,868
Telegram ranks this channel #34 of 35 here — alongside 34 others — read 18 September 2026
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.
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 30 October 2026 — this entry's latest reading, not the date you are reading this.
“RubikVpn|روبیک وی پی ان” (@vpnrubik), 9,764 subscribers as measured 30 October 2026. Telegram Register, tgregister.com/channel/vpnrubik.
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.