Telegram RegisterThe public register of Telegram
Telegram profile photo for 众鑫出货通知

Channel

众鑫出货通知

@zhongxin8888

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

252subscribers

+4 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-1001884980241
TypeChannel
Username@zhongxin8888
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live1 November 2026
Measurements held7
Confirmed unchanged2 times, most recently 1 November 2026
On Telegramt.me/zhongxin8888

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 23 September 2026 and assigned it the closest of 31 fixed categories, at 85% 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 the other topics.

Growth

2482542517 August 2026 — 248 subscribers8 August 2026 — 248 subscribers16 August 2026 — 250 subscribers10 September 2026 — 249 subscribers26 September 2026 — 253 subscribers10 October 2026 — 254 subscribers25 October 2026 — 252 subscribers2527 August 202625 October 2026
7 measurements spanning 78 days, net +4. 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 247–255 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Oct 2026, 00:27252-2
10 Oct 2026, 16:37254+1
26 Sept 2026, 22:16253+4
10 Sept 2026, 18:01249-1
16 Aug 2026, 16:56250+2
8 Aug 2026, 09:33248no change
7 Aug 2026, 14:41248first reading

Engagement

20 posts held, back to 16 November 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 20 posts for this entry, the most recent from 6 August 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 2 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 1 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 16 November 2025 to 6 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

6 Aug 2026, 11:15 UTC86 viewsread 8 August 2026
Photo

23年加工的 正反不冻结 包支付限制号 几百个 38u 需要滴滴

30 Jun 2026, 11:06 UTC378 viewsread 8 August 2026
Photo

国内 2-3 月 老年 18 位支付带正反现货 200+🉑62🉑爱思

21 Jun 2026, 06:09 UTC458 viewsread 8 August 2026

未成年实名支付 62 限制号 19 年实名大量有需要 DDDD

7 Jun 2026, 12:55 UTC656 viewsread 8 August 2026

📱📱📱📱📱📱📱 广东二月冻结 广东二月单视频号实名 @zx8898

7 Jun 2026, 12:52 UTC654 viewsread 8 August 2026
Photo

国卡钉钉实名半年 5U 可提供 Ai 视频,包秒 @zx8898

7 Jun 2026, 12:48 UTC507 viewsread 8 August 2026
Photo

国卡实名灵魂 3 月 可挑男女年龄 15U 不包秒死,设备刷干净,国内网上,无秒死 @zx8898

17 May 2026, 08:48 UTC535 viewsread 8 August 2026

国内手机限制号,老外手持护照10万额度,包收包付,带资料62 -23U

8 May 2026, 06:22 UTC651 views0 reactionsread 8 August 2026

飞机信息推送不提醒问题 换个联通香港卡即可解决

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

“众鑫出货通知” (@zhongxin8888), 252 subscribers as measured 25 October 2026. Telegram Register, tgregister.com/channel/zhongxin8888.

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.