Telegram RegisterThe public register of Telegram
Telegram profile photo for 海南晨钟报告

Channel

海南晨钟报告

@HNCZBG

2 usernames

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry

8,698subscribers

+769 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1002010600117
TypeChannel
Usernames@hainanbang @HNCZBG
Description海口晨钟交流: @HNCZMG 海口晨钟榜单: @HNCZBD02 海南晨钟报告: @Hainanbang 海南晨钟雷报: @HN_leibao 上榜/投稿: @HNrenzhengBot
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live14 November 2026
Measurements held51
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/HNCZBG

Topic

Adult — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 59% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@HNCZBG/2183 · this entry7 Aug 2026, 16:54 UTC@sunlkaa/837 Aug 2026, 16:56 UTC1.002 minutes
@HNCZBG/2186 · this entry8 Aug 2026, 07:53 UTC@sunlkaa/848 Aug 2026, 07:55 UTC1.002 minutes
@HNCZBG/2193 · this entry9 Aug 2026, 00:58 UTC@sunlkaa/859 Aug 2026, 02:30 UTC1.001.5 hours
@HNCZBG/2195 · this entry9 Aug 2026, 03:08 UTC@sunlkaa/869 Aug 2026, 03:10 UTC1.002 minutes
@HNCZBG/2196 · this entry9 Aug 2026, 03:18 UTC@sunlkaa/879 Aug 2026, 05:14 UTC1.001.9 hours
@HNCZBG/2221 · this entry14 Aug 2026, 00:28 UTC@sunlkaa/9514 Aug 2026, 08:33 UTC1.008.1 hours
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@sunlkaa6 (6/6 hand-verifiable sample passed)1.0047 minutesthis entry (6–0)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 211 comparable posts for this entry, running 3 August 2026 to 17 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 2 channels, the one whose matching posts we hold earliest is @HNCZBG — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 17 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

7,9298,6988,313.58 August 2026 — 7,929 subscribers8 August 2026 — 7,929 subscribers8 August 2026 — 7,937 subscribers9 August 2026 — 7,938 subscribers11 August 2026 — 7,949 subscribers11 August 2026 — 7,949 subscribers14 August 2026 — 7,970 subscribers15 August 2026 — 7,975 subscribers18 August 2026 — 7,975 subscribers19 August 2026 — 7,981 subscribers21 August 2026 — 8,009 subscribers22 August 2026 — 8,014 subscribers25 August 2026 — 8,029 subscribers25 August 2026 — 8,029 subscribers28 August 2026 — 8,057 subscribers28 August 2026 — 8,061 subscribers30 August 2026 — 8,081 subscribers30 August 2026 — 8,080 subscribers3 September 2026 — 8,123 subscribers3 September 2026 — 8,126 subscribers8 September 2026 — 8,150 subscribers8 September 2026 — 8,153 subscribers11 September 2026 — 8,182 subscribers12 September 2026 — 8,186 subscribers15 September 2026 — 8,210 subscribers16 September 2026 — 8,215 subscribers28 September 2026 — 8,313 subscribers2 October 2026 — 8,339 subscribers5 October 2026 — 8,377 subscribers8 October 2026 — 8,388 subscribers12 October 2026 — 8,426 subscribers13 October 2026 — 8,436 subscribers16 October 2026 — 8,457 subscribers16 October 2026 — 8,458 subscribers19 October 2026 — 8,483 subscribers19 October 2026 — 8,487 subscribers22 October 2026 — 8,509 subscribers22 October 2026 — 8,520 subscribers25 October 2026 — 8,531 subscribers26 October 2026 — 8,532 subscribers28 October 2026 — 8,559 subscribers29 October 2026 — 8,560 subscribers31 October 2026 — 8,573 subscribers1 November 2026 — 8,573 subscribers3 November 2026 — 8,583 subscribers6 November 2026 — 8,605 subscribers6 November 2026 — 8,605 subscribers9 November 2026 — 8,644 subscribers9 November 2026 — 8,644 subscribers14 November 2026 — 8,696 subscribers14 November 2026 — 8,698 subscribers8 August 202614 November 2026
51 measurements spanning 99 days, net +769. 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 7,814–8,813 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 51
Measured (UTC)SubscribersChange
14 Nov 2026, 19:478,698+2
14 Nov 2026, 08:188,696+52
9 Nov 2026, 18:498,644no change
9 Nov 2026, 13:068,644+39
6 Nov 2026, 09:018,605no change
6 Nov 2026, 08:378,605+22
3 Nov 2026, 09:028,583+10
1 Nov 2026, 03:508,573no change
31 Oct 2026, 17:578,573+13
29 Oct 2026, 01:498,560+1
28 Oct 2026, 19:198,559+27
26 Oct 2026, 04:108,532+1
25 Oct 2026, 13:578,531+11
22 Oct 2026, 22:508,520+11
22 Oct 2026, 04:588,509+22
19 Oct 2026, 15:588,487+4
19 Oct 2026, 07:368,483+25
16 Oct 2026, 19:388,458+1
16 Oct 2026, 00:378,457+21
13 Oct 2026, 19:108,436first reading

Engagement

220 posts held, back to 3 August 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 47 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
8.51%
avg views ÷ 8,698 subscribers
Avg views / post
740
93 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
93
of 220 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 17 November 2026
Posts held220 (3 August 2026 – 17 November 2026)
Views total68,830
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 13:48 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.

What this channel posts

Photos
≈16
Videos
≈3
Links
≈2,530

Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Recent posts

Telegram’s own ‘edited’ marker: 3 of 93 posts held from the last 30 days (3.23%) 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).

17 Nov 2026, 12:47 UTC110 viewsread 17 November 2026

出击报告 (https://t.me/Hainanbang) 验证留名:主打一个舔 上课时间:11.17 老师花名:#思佳 位置坐标:#琼山区 上课花费:1100 颜值身材:9.0 服务内容:95+98 推荐程度:98 出击体验:群里榜上随便刷到的,看好评已经挺多,看着是御姐就直接私信了。约好时间,到地方后遥控上楼,整栋楼安保做得挺到位,心里一下子就踏实了。 进门抽了根烟,交完水费就开始一起洗澡。热水冲着,她突然伸手下来轻轻握住,酥酥麻麻的感觉从下面一路窜上来,小兄弟当场就礼貌地抬起头回应了。洗着洗着被她小小的嘴巴一口裹住,温热又湿软,节奏不急不慢,舒服得我差点直接缴械。 擦干身上床,她先用手指慢慢摸过全身,皮肤被她摸得一阵一阵发紧。从吻开始,舌头软软的缠着,呼吸都乱了。口活真的很会,含得深、吸得稳,几次都快把持不住。她主动骑上来开局,腰扭得又软又有力,后面换侧入、后入,每换一个姿势都配合得很好。后入的时候尤其爽,撞得又深又稳,…

17 Nov 2026, 12:45 UTC114 viewsread 17 November 2026

出击报告 (https://t.me/Hainanbang)验证留名:SST 上课时间:11.17 老师花名:白洁 位置坐标:琼山 上课花费:1000 颜值身材:10分 服务内容:福利课 出击体验:推开房门,扑面而来是属于老师独有的柔和气息。房间不算奢华,但干净又温馨。交了水费,迅速洗完,躺在床上老师开始用朱唇给我服务,每一次游走都带着靡靡之音,让我心猿意马。接着老师口含我那神器,你来我往互相配合,唇棒急促交错,呼吸沉沉起伏。眼神迷离而又专注,浑身透着鲜活妩媚的劲儿。然后开始女上进入,彼此互相蠕动,不断刺激我的神经,差点交代。马上叫停,翻身上马,身体不断迸发力量,每一次发力都格外畅快淋漓,两个人都沉浸在交合的快乐里。我全力带她加快节奏,老师叫声在耳边此起彼伏,不行了,拼尽全力一泻千里,胸腔大口吞吐着空气,浑身血液都在沸腾。快乐的时间总是过得很快,洗完澡出来,拥抱道别,明明只是短暂的鱼水之欢,心底却漫上来浓浓的不舍。看着她转身曼妙…

17 Nov 2026, 11:58 UTC158 viewsread 17 November 2026

出击报告 (https://t.me/Hainanbang) 验证留名:二狗 王 上课时间:2026.11.17 老师花名:#李晨溪 位置坐标:#三亚天涯 上课花费:p700 颜值身材:10分满分,肤白貌美 服务内容:见课表 出击体验:看到新老师符合自己审美,第一时间预约,课时安全,环境良好,见到老师眼前一亮,身材哇塞,🐻目测有天然d,大长腿,人照对版,先洗澡,有水中萧,洗完急不可耐进入正题,妹妹粉嫩无异味,表情自然投入,水多,各种姿势任摆,带好雨衣123,五分钟不到就被秒了,兄弟们,可以冲。 优点缺点:天然🐻,皮肤白,身材好,漂亮。 推荐程度:十分推荐 联系方式:@chenxi0112 1,需要狼友提交报告 2,需要预约记录 3,需要付款记录,线上支付不需要拍照

17 Nov 2026, 09:53 UTC219 viewsread 17 November 2026

出击报告 (https://t.me/Hainanbang) 验证留名:噜 上课时间:11.17 老师花名:#木子李 位置坐标:#琼山 上课花费:20 颜值身材:sexy 服务内容:见课表 出击体验:休息一晚,今天包时继续和李姐亲亲抱抱举高高。过程不表了,总之和李姐在一块很放松,三个小时很快就过去了,真的一滴都没有了。等cd好了再来抱李姐。 优点缺点:人美活泼态度好 推荐程度:5⭐ 联系方式:@x_0815

17 Nov 2026, 08:26 UTC264 viewsread 17 November 2026

出击报告 (https://t.me/Hainanbang) 验证留名:大白兔 上课时间:11.17 老师花名:白洁 位置坐标:琼山 上课花费:700 颜值身材:10分 服务内容:课表 出击体验:老师长相甜美,人照九成 笑起来很好看。人比照片美,不上相聊了一会就去洗澡,很舒服,妹妹口活还是可以的,不叫不停,差点喷出来,可不能交待在这,岂不是亏了 😂 来到床上,她的小手在我的身上游走把人撩的一愣一愣的摸着妹妹的小 🐻非常的挺拔柔软,看着妹妹美丽的样子立马叫妹妹带套进去,没想到里面那么紧,紧致又润超有感觉,我立马搂着妹妹加快了速度,随后他的喘息声也越来越大,让人听着受不了,中间换了几个动作,妹妹也很配合全程不催反馈感足,最后后入交待了,很爽的一次 cj 推荐程度:十分推荐 联系方式:@baijie356 1,需要狼友提交报告 2,需要预约记录 3,需要付款记录,线上支付不需要拍照

17 Nov 2026, 08:26 UTC238 viewsread 17 November 2026

出击报告 (https://t.me/Hainanbang) 验证留名:匿名 上课时间:26-11-15 老师花名:#露思 位置坐标:#美兰区 上课花费:30包时 颜值身材:10 服务内容:课表有 出击体验:等了很久的老师,终于给我约到包时了,服务细致,本人很好看,身材好,也十分健谈,包推荐的 优点缺点:非常好 推荐程度:五颗星 联系方式:@Lusi75999 1,需要狼友提交报告 2,需要预约记录 3,需要付款记录,线上支付不需要拍照

17 Nov 2026, 08:21 UTC241 viewsread 17 November 2026

出击报告 (https://t.me/Hainanbang) 验证留名:想妹妹 上课时间:11.17 老师花名:#思佳 位置坐标:#琼山区 上课花费:1000 颜值身材:9.0 服务内容:包时1h 推荐程度:9.7 出击体验:一见面就爱了,跟频道照片一样,带些御姐范儿,气质十足,是我喜欢的类型。教室也是整洁温馨,像回家的感觉。聊聊天然后差不多了进入正题,脱光光进到浴室,看到老师胸前的两个大🐻就按耐不住了,手感超好,很柔软,陪浴洗的很仔细,水中啸、胸推也有安排上,超爽的。前戏已经给拉满了,擦干后进入小房间,课表服务都有,老师做的很认真,口活也很好,一点齿感没有,很润,我直接按捺不住戴上t开始冲刺,刚进去很紧很润,包裹感很强,全程老师都很投入,跟女朋友一样,能感觉到思佳老师也是真正在享受爱爱的感觉,最后也是直接发射,总得来说老师身材,颜值,性格,服务态度都很好,推荐! 联系方式:@sijia523 1,需要狼友提交报告 2,需要预约…

17 Nov 2026, 06:01 UTC289 viewsread 17 November 2026

出击报告 (https://t.me/Hainanbang) 验证留名:您好 上课时间:11.17 老师花名:#果冻橙 位置坐标:#龙华区 上课花费:7 颜值身材:前凸后翘很大 服务内容:服务课表都有,特色水床服务细致 出击体验:前几天心痒痒,一直想约老师体验新服务,今天约了老师头课,皮肤很好,光滑细致,身材前凸后翘,特别推荐体验特色服务,一开始沐浴盐,有着淡淡薰衣草香这点好评,接着牛奶沐浴露,过程太爽了,依次按照课表服务,后面懂得都懂,真心推荐。课室氛围很好,全程很自然舒服,没有敷衍,配合很好,情绪价值给得很到位,推荐兄弟们都来。 推荐程度:10 联系方式:@anhao969 1,需要狼友提交报告 2,需要预约记录 3,需要付款记录,线上支付不需要拍照

17 Nov 2026, 05:59 UTC274 viewsread 17 November 2026

出击报告 (https://t.me/Hainanbang) 验证留名:尴尬哥 上课时间:11.17 老师花名:白洁 位置坐标:琼山 上课花费:1000 颜值身材:10分 服务内容:福利一小时 出击体验、】提前联系好时间,老师遥控上楼的,进屋先寒暄了几句,人挺随和,没有尴尬也不冷场。房间挺暖,洗漱配套用品很齐全,帮洗也很认真。房间里jk服装琳琅满目,还可以自由搭配,选好躺在床上,开始十指弹琴,三点蛇游,小🐍舔🥚,舔的实属舒服,见状态差不多了,就带上雨伞,老师先是开始女上,接下来开始传教士,交锋几轮后顺利交货, 推荐程度:十分推荐 联系方式:@baijie356 1,需要狼友提交报告 2,需要预约记录 3,需要付款记录,线上支付不需要拍照

17 Nov 2026, 00:59 UTC389 viewsread 17 November 2026

出击报告 (https://t.me/Hainanbang) 验证留名:iu 上课时间:11.17 老师花名:楚一璇 位置坐标:龙华 上课花费:10 颜值身材:棒 服务内容:课表服务上 出击体验:见到老师人照一致,很漂亮说话很温柔,长相身材一级棒,太主动了,帮我脱衣洗鸳鸯浴,洗的很细致,还用胸猛猛蹭,水中萧,舔奶头全都来。我差点就在浴室犯罪,洗的全身很干净,很舒服。上床等候老师,老师换好黑丝装备就来给我服务了,我摸着胸手感很好,老师从上舔到下,深喉一绝,口很给力差点忍不住了,赶快带上小雨伞开干,身材颜值服务都没得说,性格还很好,很满意的体验,下次再来。 优点缺点:🈚️ 推荐程度:十分推荐 联系方式:@chuyixuanoo 1,需要狼友提交报告 2,需要预约记录 3,需要付款记录,线上支付不需要拍照

17 Nov 2026, 00:59 UTC356 viewsread 17 November 2026

出击报告 (https://t.me/Hainanbang) 验证留名:kk 上课时间:11、16 老师花名:#娜比 位置坐标:#龙华区 上课花费:10p 颜值身材:人照合一 服务内容:服务课表上的 出击体验:全身紧致,无赘肉,身高比列好搞完感觉自己年轻很多,口活好,舒服一炮来了绝对不后悔 优点缺点:没有 推荐程度:10 联系方式:@nabifff 1,需要狼友提交报告 2,需要预约记录 3,需要付款记录,线上支付不需要拍照

17 Nov 2026, 00:58 UTC356 viewsread 17 November 2026

出击报告 (https://t.me/Hainanbang) 验证留名:你好 上课时间:11.17 老师花名:#奶桃桃 位置坐标:#龙华区海口 上课花费:10 颜值身材:标准 服务内容: 课表有的 出击体验:今天约了老师头课人照一致,尤其是皮肤很白嫩,手感特别好,身材就更不用说了,比例很好,要胸有胸,臀也翘,后入妥妥的,有臀浪,视觉效果很好… ⭐️整体的感觉很不错,老师人也很温柔热情。从进门就开始主动营造氛围,前戏做得细腻体贴,服务节奏把握得很好,技术稳定且有温度,全程比较自然舒服,没有敷衍或尴尬的地方,属于让人比较放松且满意的类型。服务好,态度好,身材棒,颜值不错 十分推荐给兄弟们。 态度好, 推荐程度:10 联系方式:@naitaotaoa 1,需要狼友提交报告 2,需要预约记录 3,需要付款记录,线上支付不需要拍照

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

Posts edited after publishing

@HNCZBG edited 3 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
16 November 2026
Most recent edit
16 November 2026

Posts recorded as deleted after publishing

We recorded 2 posts on @HNCZBG as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
19 August 2026
Most recent seen missing
22 August 2026
Median time before seen missing
4 days
Seen missing in the last 30 days
0

Mentions

Named by 21 registered channels — 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.

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

“海南晨钟报告” (@HNCZBG), 8,698 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/HNCZBG.

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.