Telegram RegisterThe public register of Telegram
Telegram profile photo for DriftVPN

Channel

DriftVPN

@driftvpn_official

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

1,975subscribers

+356 since we began measuring on 28 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1003913250283
TypeChannel
Username@driftvpn_official
CreatedBetween 1 April 2026 and 17 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded28 August 2026
Last confirmed live16 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/driftvpn_official

Topic

Technology — 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

1,6191,9751,79728 August 2026 — 1,619 subscribers28 August 2026 — 1,624 subscribers31 August 2026 — 1,684 subscribers3 September 2026 — 1,730 subscribers8 September 2026 — 1,831 subscribers12 September 2026 — 1,917 subscribers16 September 2026 — 1,975 subscribers28 August 202616 September 2026
7 measurements spanning 19 days, net +356. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,566–2,028 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 05:181,975+58
12 Sept 2026, 22:201,917+86
8 Sept 2026, 20:391,831+101
3 Sept 2026, 22:201,730+46
31 Aug 2026, 13:121,684+60
28 Aug 2026, 11:521,624+5
28 Aug 2026, 05:451,619first reading

Engagement

20 posts held, back to 17 June 2026the 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.

ERR · 30 days
17.8%
avg views ÷ 1,975 subscribers
Avg views / post
351
7 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
7
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 26 August 2026
Posts held20 (17 June 202626 August 2026)
Views total2,455
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 05:45 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

13 reactions across 6 posts, in 2 distinct kinds. The most used accounts for 92.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1292.3%
👍17.69%

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 6 of the 20 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 13 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 17 June 2026 to 26 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.

Recent posts

26 Aug 2026, 23:01 UTC222 viewsread 28 August 2026

macOS 1.3.7 已经审核通过,请前去苹果商店更新

25 Aug 2026, 16:52 UTC418 viewsread 28 August 2026

Windows 1.3.4 → 1.3.7 更新说明: 升级 Windows 网络 SDK,提升连接稳定性。 修复切换节点后被误判为断开的问题。 SDK 调用改为异步执行,减少界面卡顿。 启动及连接前自动清理残留系统代理、PAC 和路由。 优化连接异常后的网络环境恢复。

25 Aug 2026, 16:52 UTC384 viewsread 28 August 2026

win 最新 测试版本,欢迎大家测试,如有问题,欢迎发工单反馈

21 Aug 2026, 06:48 UTC760 viewsread 28 August 2026

1.3.3版本 macOS 已上线苹果商店 1,支持 UDP 转发,改善 Telegram、Discord 视频通话 2,优化节点页面,选择节点更方便 3,新增流量包购买入口 4,分流模式即时生效 5,登录流程简化 6,支持节点热切换 7,新增查看当前在线设备页面 8,全面优化sdk更快更稳

20 Aug 2026, 09:33 UTC855 viewsread 28 August 2026

轻舟VPN iOS 1.3.2 正式上线!🎉 本次更新: ✅ 支持 UDP 转发,改善 Telegram、Discord 视频通话 ✅ 优化节点页面,选择节点更方便 ✅ 新增流量包购买入口 ✅ 分流模式即时生效 ✅ 登录流程简化 ✅ 支持节点热切换 请前去官网获取 http://qz.run https://apps.apple.com/gb/app/driftvpn-fast-secure-vpn/id6745591588 现在前往 App Store 更新体验。 轻舟VPN|快得很稳定

6 Aug 2026, 12:30 UTCviews —

Driftvpn pinned «💳 轻舟VPN现已支持银联支付! 现在可以直接使用带有银联标识的银行卡购买套餐,付款更加方便。 登录官网选择套餐,在付款页面选择「银联支付(UnionPay)」即可。»

6 Aug 2026, 10:33 UTC≈1,890 viewsread 28 August 2026

💳 轻舟VPN现已支持银联支付! 现在可以直接使用带有银联标识的银行卡购买套餐,付款更加方便。 登录官网选择套餐,在付款页面选择「银联支付(UnionPay)」即可。

31 Jul 2026, 10:11 UTC≈2,020 views2 reactionsread 28 August 2026

📲 轻舟VPN 官方客户端下载 请根据您的设备,点击下方链接下载: 🍎 iPhone / iPad https://apps.apple.com/us/app/driftvpn-fast-secure-vpn/id6745591588 🤖 Android https://qz.run 💻 Windows / macOS https://qz.run 首次使用:下载安装 → 注册或登录账号 → 选择线路连接。 ⚠️ 请仅通过本频道或官方网站下载客户端,谨防非官方安装包。 官方网站:https://qz.run

1👍1

Showing the 12 most recent of 20 posts we hold for @driftvpn_official. 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

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.

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.

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 16 September 2026 — this entry's latest reading, not the date you are reading this.

“DriftVPN” (@driftvpn_official), 1,975 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/driftvpn_official.

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.