Telegram RegisterThe public register of Telegram
Telegram profile photo for Captain船长中国🇨🇳官方

Channel

Captain船长中国🇨🇳官方

@CZNB616

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

20,879subscribers

+89 since we began measuring on 14 November 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1004363276097
TypeChannel
Username@CZNB616
CreatedBetween 1 June 2026 and 31 October 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 November 2026
Last confirmed live17 November 2026
Measurements held2
Confirmed unchanged1 time, most recently 17 November 2026
On Telegramt.me/CZNB616

Growth

20,79020,87920,834.514 November 2026 — 20,790 subscribers17 November 2026 — 20,879 subscribers14 November 202617 November 2026
2 measurements spanning 3 days, net +89. 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 20,777–20,892 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Nov 2026, 01:5920,879+89
14 Nov 2026, 12:2220,790first reading

Engagement

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

ERR · 30 days
24.3%
avg views ÷ 20,879 subscribers
Avg views / post
5,070
19 posts measured
Reaction rate
1.73%
reactions ÷ views · ER floor
Posts in window
19
of 19 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 13 November 2026
Posts held19 (10 November 2026 – 13 November 2026)
Views total96,312
Reactions total1,665
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 00:28 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

1,665 reactions across 18 posts, in 31 distinct kinds. The most used accounts for 38.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍63538.1%
🤬24814.9%
😁1579.43%
😱1227.33%
🔥1116.67%
🎉824.92%
🤡784.68%
❤764.56%
🤣342.04%
👏261.56%
😍211.26%
🐳201.20%
💩171.02%
🥰70.42%
👎60.36%
🦄40.24%
🍌30.18%
🤷30.18%
🎃20.12%
🙈20.12%
11 further kinds110.661%

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

Measured over the 19 most recent posts we hold, published 10 November 2026 to 13 November 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

Telegram’s own ‘edited’ marker: 6 of 19 posts held from the last 30 days (31.6%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

13 Nov 2026, 11:24 UTC609 views22 reactionsread 17 November 2026

😂老外放话了 随便稳定等着吧 @zszs782 这也是我项目频道😏 为了让所有兄弟都能玩在给每一个兄弟适配 别着急

👍14🍌3🤷3❤1🦄1

Signed 老三(直面主题)

13 Nov 2026, 03:51 UTC≈4,020 views207 reactionsread 17 November 2026
Photo

✈️还是有兄弟不闪啊 那就把卡密给你们 DF629E54A62849050057A1CB 95E4B753 等着吧我给兄弟们憋一坨大的!😂

👍104🤡34🤬22😍21💩17❤5🎃1🤷‍♂1

Signed 老三(直面主题)

11 Nov 2026, 09:44 UTC≈6,630 views23 reactionsread 17 November 2026

4.0版本现在个别正常使用无闪退,个别闪退的等待更新5.0! 更新5.0团队正在加急制作中!感谢大家理解!😘

👍13👎4❤2🎃1🔥1🗿1😁1

Signed 老三(直面主题)

11 Nov 2026, 09:20 UTC≈4,610 views112 reactionsread 17 November 2026

还是有兄弟可以正常玩的 因为垃圾加密问题 个别人可能会闪退 已重写加密 !老外已经两天没睡觉了!让他这次加快更新速度!

👍104🥰5❤1🎄1🦄1

Signed 老三(直面主题)

11 Nov 2026, 09:09 UTC≈4,750 views7 reactionsread 17 November 2026

更新完毕!船长4.0版本已经更新! 自行查看频道置顶信息公益游玩! 反馈图联系 @Nian1960 双向联系 @CZNB7891bot

👎2⚡1❤1🤝1🥰1🆒1

Signed 老三(直面主题)

11 Nov 2026, 08:59 UTC≈4,260 views178 reactionsread 17 November 2026

说实话现在很多内核都还在更新当中 包括很多直装同行也在更新之中 那些已经更新的直装打着稳定的旗号给你们 那些用户也不怕全体回溯 内核都还不能保证百分百稳定 直装先保证百分百稳定了👨‍💻

👍74🤡44🤬42😁15❤1🥰1🙈1

Signed 老三(直面主题)

10 Nov 2026, 16:55 UTC≈3,280 views38 reactionsread 17 November 2026
Photo

Photo, posted without a caption

🎉11🔥8😁8❤5👍5💘1

10 Nov 2026, 16:55 UTC≈4,280 views36 reactionsread 17 November 2026
Photo

Photo, posted without a caption

😁10👍7🔥7❤6🎉5🦄1

10 Nov 2026, 16:55 UTC≈4,380 views82 reactionsread 17 November 2026
Photo

Photo, posted without a caption

😱42🔥38❤1👍1

10 Nov 2026, 16:55 UTC≈8,630 views723 reactionsread 17 November 2026

Captain船长中国🇨🇳官方频道 免费送 钱 活动如下!💵💵💵 📷打开快手软件 在搜索栏搜索: #直装 标题⚠️ 🤣选择最近一周内发布的作品 📷评论区评论一个图片 🔘附带文字:三角洲船长太好玩 (图片获取点我) 评论完截图保存!一个评论为0.1💸 🥰暂时限制每人30条 🥰领钱客服 @Nian1960 ⚠️作品必须是近期 一周内发布的! 1️⃣如果评论被我刷视频刷到我会私信你!奖励为18.8人民币! 2️⃣另外发船长作品的被我刷到也会奖励8.88人民币! 🌐活动真实有效!认准!!! 😇🙃😉@CZNB616

👍227🤬184😁90😱80🤣34👏25❤23🎉20

10 Nov 2026, 16:55 UTC≈4,070 views5 reactionsread 17 November 2026
Photo

Photo, posted without a caption

👍4🥴1

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

Names

Channels on the register whose handles appear in this channel's posts.

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

“Captain船长中国🇨🇳官方” (@CZNB616), 20,879 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/CZNB616.

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.