Channel
@qijiavpn
On this record: Growth · Engagement · Posts · Citations · Cite this entry
364subscribers
+3 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003867654136 |
|---|---|
| Type | Channel |
| Username | @qijiavpn |
| Created | 15 July 2026 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/qijiavpn |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 08:16 | 364 | +3 |
| 12 Aug 2026, 11:31 | 361 | first reading |
4 posts held, back to 15 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 1 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 4 August 2026 |
|---|---|
| Posts held | 4 (15 July 2026 – 4 August 2026) |
| Views total | 700 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 11:31 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.
尊敬的 7Jia 用户： 近期，我们的系统遭遇了多重 CC 攻击、DDoS 攻击以及官网注入等严重安全威胁。在此期间，技术团队全力保障网络安全，确保了所有在用节点的用户的全节点始终保持安全、稳定的运行状态。 在此之间我们节点一直全时候可用 目前，我们已全面升级并重构了官网系统。为保证您后续的正常使用，请仔细阅读以下事项： 一、 订阅更新提醒（请尽快操作） 请前往最新官网 重新导入新订阅，或在您的客户端中尝试 更新订阅。 我们将于 8 月 7 日 正式关闭事件保障期间所使用的临时节点。请务必在此日期前完成订阅更新，以免影响使用。 二、 流量与补偿说明 流量免扣费：在此次攻击事件发生期间，所有节点产生的消耗均未计入计费流量。 补偿方案：针对本次事件给您带来的不便，我们稍后将统一推出赔付方案，具体细节请关注后续通知。 感谢广大用户对 7Jia 的理解、信任与支持！我们将持续优化防护能力，为您提供更优质服务。 7Jia 团队 【进…
赔付工作已经将近收尾，感谢大家的理解与支持。 目前三个客服循环值班，只为一直为您保证可用性。 技术全天巡查解锁，实时保障网络稳定。 12 元 300G，折合每 100G 仅需 4 元，超高性价比。 我们将全心全意给您制作最靠谱、安全的体验。 【进入群组】 【跳转官网】
7Jia 节点服务 · 官方声明 品牌承诺： 在 7Jia，我们始终认为：优质的服务与极致的效率，远比虚高宣传更有价值。 我们不玩套路，不做一锤子买卖。用最实在的态度，做最在意你使用体验的网络连接伙伴。 核心优势： 最在意用户的机场 始终站在使用者角度思考，重视每一条用户反馈。责任有担当，服务有始有终，用心守护每一次连接。 极速响应的售后服务 专属客服在线守护，拒绝冰冷的机器推诿。无论是节点排障还是使用配置，第一时间响应并处理，彻底告别找不到人的焦虑。 官方通道 全部免翻官网直达 https://qijia.qhrgobull.fun/ Telegram 官方群组 https://t.me/qijiaqunzu
Channel created
Showing the 4 most recent of 4 posts we hold for @qijiavpn. 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.
Citation-graph rank — 1,125,594 of 1,480,975entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“7Jia通知” (@qijiavpn), 364 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/qijiavpn.
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.