Channel
@vj333
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
8,372subscribers
-1,803 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001932631063 |
|---|---|
| Type | Channel |
| Usernames | @vj333 @zhense |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/vj333 |
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 11 September 2026 and assigned it the closest of 31 fixed categories, at 50% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 17:55 | 8,372 | -172 |
| 14 Sept 2026, 06:57 | 8,544 | -271 |
| 10 Sept 2026, 09:55 | 8,815 | -139 |
| 5 Sept 2026, 06:38 | 8,954 | -63 |
| 1 Sept 2026, 20:06 | 9,017 | -79 |
| 30 Aug 2026, 02:16 | 9,096 | -198 |
| 27 Aug 2026, 12:35 | 9,294 | -75 |
| 24 Aug 2026, 04:54 | 9,369 | -208 |
| 20 Aug 2026, 10:23 | 9,577 | -104 |
| 17 Aug 2026, 17:55 | 9,681 | -259 |
| 14 Aug 2026, 14:05 | 9,940 | -81 |
| 13 Aug 2026, 05:07 | 10,021 | -13 |
| 12 Aug 2026, 05:18 | 10,034 | -19 |
| 11 Aug 2026, 06:24 | 10,053 | -60 |
| 10 Aug 2026, 07:40 | 10,113 | -62 |
| 9 Aug 2026, 10:16 | 10,175 | first reading |
25 posts held, back to 5 July 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 27 pages 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 25 posts for this entry, the most recent from 27 August 2026. An engagement rate over an empty window would be a number about nothing.
51 reactions across 13 posts, in 2 distinct kinds. The most used accounts for 64.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 33 | 64.7% | |
| 👍 | 18 | 35.3% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 16 of the 25 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 51 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 25 most recent posts we hold, published 5 July 2026 to 27 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
🔤🔤🔤🔣🔣🔣 🇸🇬 新加坡（Singapore） IPV6内置代理分部 🧩https://t.me/proxy?server=2407:d140:1:100:9000:9000:20db:c9d7&port=11854&secret=dd621418961f9f616470fdff00dd1e1f73 🧩https://t.me/proxy?server=2407:d140:1:100:9000:9000:20db:c9d7&port=11854&secret=dd621418961f9f616470fdff00dd1e1f73 🧩https://t.me/proxy?server=2407:d140:1:100:9000:9000:20db:c9d7&port=11854&secret=dd621418961f9f616470fdff00dd1e1f73 近期网络通报严重，请使用ipv6线路来保障连接 更多线路 包含了世界各地…
👍3
🔤🔤🔤🔣🔣🔣 🇺🇸 美国亚特兰大 IPV4内置代理分布 🧩https://t.me/proxy?server=84.75.203.234&port=47649&secret=fbab1231e1f4969f7ae184c4337ce8e0 🧩https://t.me/proxy?server=84.75.203.234&port=47649&secret=fbab1231e1f4969f7ae184c4337ce8e0 🧩https://t.me/proxy?server=84.75.203.234&port=47649&secret=fbab1231e1f4969f7ae184c4337ce8e0 IPV6内置代理分部 🧩https://t.me/proxy?server=2602:fa4f:802:485c:a4a4:44ed:446c:1401&port=27865&secret=dd0e3cc675ef8829d36c5…
❤4
针对部分群友反映的流量被重置及大量消耗问题，现作出如下说明：系统会记录用户过往使用本代理服务所产生的数据消耗。经核查，凡服务有效期未届满且流量未超限的用户，均不予恢复流量；仅针对已超使用量但服务期限仍在有效期内的用户，系统将执行重置并补足流量。需要强调的是，本免费代理服务旨在解决用户的紧急需求，无法提供与付费代理同等水平的维护与售后服务。作为公益项目，我们已多次重申此原则。
❤2👍1
在巡查过程中，发现个别用户利用节点服务器进行倒卖活动，其在线设备数量高达64台，此举严重损害了其他用户的利益。我们致力于为用户提供优质的互联网服务，为此现做出以下调整： 第一，将在线设备数量上限调整为2台。 第二，重置所有用户的套餐流量，恢复至初始状态（对于剩余有效期的用户，已使用的流量将被清零）。 第三，如有其他问题，请通过设立的问题反馈组进行反馈，工作人员将在空闲时间查看并予以说明。 问题反馈群🔣🔣🔣https://t.me/+wahWfIOa3sdhOTRk 🔡🔡🔡
❤4
🔤🔤🔤🔣🔣🔣 🇳🇱 荷兰阿姆斯特丹 IPV4内置代理分布 🧩https://t.me/proxy?server=tw01.mioc.top&port=13376&secret=dd91c7fecdf5805a482ea70043dede1e5b 🧩https://t.me/proxy?server=tw01.mioc.top&port=13376&secret=dd91c7fecdf5805a482ea70043dede1e5b 🧩https://t.me/proxy?server=tw01.mioc.top&port=13376&secret=dd91c7fecdf5805a482ea70043dede1e5b IPV6内置代理分部 🧩https://t.me/proxy?server=2a06:f901:1:100::261&port=26464&secret=dd91c7fecdf5805a482ea70043dede1e…
❤1
🔤🔤🔤🔣🔣🔣 🇳🇱 荷兰阿姆斯特丹 IPV4内置代理分布 🧩https://t.me/proxy?server=tw01.mioc.top&port=13376&secret=dd91c7fecdf5805a482ea70043dede1e5b 🧩https://t.me/proxy?server=tw01.mioc.top&port=13376&secret=dd91c7fecdf5805a482ea70043dede1e5b 🧩https://t.me/proxy?server=tw01.mioc.top&port=13376&secret=dd91c7fecdf5805a482ea70043dede1e5b IPV6内置代理分部 🧩https://t.me/proxy?server=2a06:f901:1:100::261&port=26464&secret=dd91c7fecdf5805a482ea70043dede1e…
👍4❤3
🔤🔤🔤🔣🔣🔣 🇺🇸 美国亚特兰大 IPV4内置代理分布 🧩https://t.me/proxy?server=84.75.203.234&port=47649&secret=fbab1231e1f4969f7ae184c4337ce8e0 🧩https://t.me/proxy?server=84.75.203.234&port=47649&secret=fbab1231e1f4969f7ae184c4337ce8e0 🧩https://t.me/proxy?server=84.75.203.234&port=47649&secret=fbab1231e1f4969f7ae184c4337ce8e0 IPV6内置代理分部 🧩https://t.me/proxy?server=2602:fa4f:802:485c:a4a4:44ed:446c:1401&port=27865&secret=dd0e3cc675ef8829d36c5…
👍2
🔤🔤🔤🔣🔣🔣 🇯🇵 日本东京（Japan Tokyo） IPV4内置代理分布 🧩https://t.me/proxy?server=84.75.203.234&port=47649&secret=fbab1231e1f4969f7ae184c4337ce8e0 🧩https://t.me/proxy?server=84.75.203.234&port=47649&secret=fbab1231e1f4969f7ae184c4337ce8e0 🧩https://t.me/proxy?server=84.75.203.234&port=47649&secret=fbab1231e1f4969f7ae184c4337ce8e0 IPV6内置代理分部 🧩https://t.me/proxy?server=2602:f3f2:c4:cf66:b936:b592:6d99:d33d&port=55995&secret=fbab1231e1f…
机器人的流量不会用的可以通过机器人【查看教程】，该教程频道有相关问题介绍，若有其他问题可以通过交流群反馈问题需求。 流量机器人 @AH66Bot 流量签到群 @nwsss 内部交流群 @内部群 教程频道 @E1666
最新搜索群 @xisou 广告投放 @CV222
🔤🔤🔤🔣🔣🔣 🇯🇵 日本东京（Japan Tokyo） IPV4内置代理分布 🧩https://t.me/proxy?server=84.75.203.234&port=47649&secret=fbab1231e1f4969f7ae184c4337ce8e0 🧩https://t.me/proxy?server=84.75.203.234&port=47649&secret=fbab1231e1f4969f7ae184c4337ce8e0 🧩https://t.me/proxy?server=84.75.203.234&port=47649&secret=fbab1231e1f4969f7ae184c4337ce8e0 IPV6内置代理分部 🧩https://t.me/proxy?server=2602:f3f2:c4:cf66:b936:b592:6d99:d33d&port=55995&secret=fbab1231e1f…
🔤🔤🔤🔣🔣🔣 🇸🇬 新加坡（Singapore） IPV4内置代理分布 🧩https://t.me/proxy?server=84.75.203.234&port=31665&secret=dd5948fed33ebccf03a1b274e01938d325 🧩https://t.me/proxy?server=84.75.203.234&port=31665&secret=dd5948fed33ebccf03a1b274e01938d325 🧩https://t.me/proxy?server=84.75.203.234&port=31665&secret=dd5948fed33ebccf03a1b274e01938d325 IPV6内置代理分部 🧩https://t.me/proxy?server=2605:e440:b::22f&port=19985&secret=dd5948fed33ebccf03a1b274e0193…
Showing the 12 most recent of 25 posts we hold for @vj333. 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.
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.
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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“高速代理VPN丨加速器免费分享” (@vj333), 8,372 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/vj333.
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.