Telegram RegisterThe public register of Telegram
Telegram profile photo for 零际云

Channel

零际云

@lingjivpn

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

599subscribers

-40 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003564775786
TypeChannel
Username@lingjivpn
Created31 December 2025 — measured — dated from the channel’s first post
First recorded8 August 2026
Last confirmed live8 October 2026
Measurements held8
Confirmed unchanged1 time, most recently 8 October 2026
On Telegramt.me/lingjivpn

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 20 September 2026 and assigned it the closest of 31 fixed categories, at 71% 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

5996396197 August 2026 — 639 subscribers8 August 2026 — 639 subscribers16 August 2026 — 637 subscribers25 August 2026 — 630 subscribers1 September 2026 — 625 subscribers10 September 2026 — 618 subscribers28 September 2026 — 603 subscribers8 October 2026 — 599 subscribers7 August 20268 October 2026
8 measurements spanning 61 days, net -40. 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 593–645 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Oct 2026, 02:55599-4
28 Sept 2026, 14:21603-15
10 Sept 2026, 21:01618-7
1 Sept 2026, 19:15625-5
25 Aug 2026, 00:47630-7
16 Aug 2026, 17:23637-2
8 Aug 2026, 02:48639no change
7 Aug 2026, 18:13639first reading

Engagement

10 posts held, back to 31 December 2025 — 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 10 posts for this entry, the most recent from 5 March 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1100.0%

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

Measured over the 10 most recent posts we hold, published 31 December 2025 to 5 March 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

5 Mar 2026, 04:31 UTC893 viewsread 8 August 2026

已加入免翻官网:https://start.zeroedge.co/ 订阅地址已更新,请各位用户前往官网获取,旧订阅地址依然可用

22 Feb 2026, 11:45 UTC≈1,050 views1 reactionsread 8 August 2026

网站全面升级,现在界面更好看了

❤1

17 Feb 2026, 10:35 UTC≈1,090 viewsread 8 August 2026

试用觉得本机场好用的话不妨支持一下我们,现在入手性价比最高哦!

14 Feb 2026, 16:48 UTC≈1,050 viewsread 8 August 2026

新春活动已开启,届时使用优惠码可享新春专享活动,前8名购买季付及以上订阅的用户可以凭订单号在工单处兑换后7位同字母trx钱包靓号

14 Feb 2026, 04:17 UTC942 views0 reactionsread 8 August 2026
Photo

零际ZeroEdge新春特惠 活动时间:2026年2月15日-2026年2月21日 年付6折优惠券:happy-new-year-40% 季付7折优惠券:happy-new-year-30% 一次性流量套餐优惠券:happy-new-year-25% 月付8折优惠券:lingji-8 活动期间购买订阅可有机会获得7位trx靓号一个哦! 每个优惠码每人仅可使用一次

10 Jan 2026, 17:54 UTC≈1,880 views0 reactionsread 8 August 2026
Photo

零际云开业福利 注册试用100G/30天 进群领取试用码 全场8折优惠券

Showing the 10 most recent of 10 posts we hold for @lingjivpn. 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 8 October 2026 — this entry's latest reading, not the date you are reading this.

“零际云” (@lingjivpn), 599 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/lingjivpn.

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.