Telegram RegisterThe public register of Telegram
Telegram profile photo for 全球精品数据@SJVIP666

Channel

全球精品数据@SJVIP666

@linliu66666

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

538subscribers

-40 since we began measuring on 10 September 2026

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

Register entry

Telegram ID-1002060177181
TypeChannel
Username@linliu66666
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 September 2026
Last confirmed live26 September 2026
Measurements held3
Confirmed unchanged1 time, most recently 26 September 2026
On Telegramt.me/linliu66666

Topic

Hacking & security — 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 27 September 2026 and assigned it the closest of 31 fixed categories, at 73% 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

53857855810 September 2026 — 578 subscribers11 September 2026 — 574 subscribers26 September 2026 — 538 subscribers10 September 202626 September 2026
3 measurements spanning 17 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 532–584 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
26 Sept 2026, 23:18538-36
11 Sept 2026, 22:38574-4
10 Sept 2026, 07:22578first reading

Engagement

20 posts held, back to 6 June 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 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
6.32%
avg views ÷ 538 subscribers
Avg views / post
34.0
1 post measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
1
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 7 September 2026
Posts held20 (6 June 2026 – 7 September 2026)
Views total34
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Sept 2026, 07:22 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

3 reactions across 3 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍3100.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 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 3 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 6 June 2026 to 7 September 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

7 Sept 2026, 16:59 UTC34 viewsread 10 September 2026

数据只占效果的50%。跟文案。源码。落地。时间。项目都有关系。 数据商核心提供的是一种技术通路:效果最终还是把握在老板自己手中:做好数据渠道的本分就是 1:不掺水 2:不倒卖 3:根据客户反馈进行改进优化;你需要找到的其实不是“效果商“而是一个稳定不乱来的供应商! 常见的在跑的有客户若有反馈我们会提供大概数值参考!但那是别人做的,不一定你做就一样的效果~望各位老板周知:

30 Aug 2026, 09:32 UTC55 viewsread 10 September 2026
Photo

伊拉克最大的金融交易网站 内含中东 欧美多个国家 @SJVIP666

16 Aug 2026, 11:01 UTC80 viewsread 10 September 2026
Photo

盗版零六六 请注意识别 本人唯一账号 @SJVIP666

26 Jun 2026, 15:30 UTC175 viewsread 10 September 2026
Photo

请各位老板 警惕高仿 最近这种狗鸡巴特别多

25 Jun 2026, 10:27 UTC116 viewsread 10 September 2026
Photo

墨西哥tg纯料 好料子不问来路 纯纯的料子不问出处 @SJVIP666

Showing the 12 most recent of 20 posts we hold for @linliu66666. 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 26 September 2026 — this entry's latest reading, not the date you are reading this.

“全球精品数据@SJVIP666” (@linliu66666), 538 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/linliu66666.

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.