Telegram RegisterThe public register of Telegram
Telegram profile photo for 深圳晨钟暮鼓(优惠及地址汇总)

Channel

深圳晨钟暮鼓(优惠及地址汇总)

@czmgby

2 usernames

On this record: Topic · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry

8,826subscribers

-340 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002327049228
TypeChannel
Usernames@czmgby @czyhquan
Created6 March 2025measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live19 September 2026
Measurements held27
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/czmgby

Topic

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

8,8269,1688,9977 August 2026 — 9,166 subscribers7 August 2026 — 9,168 subscribers8 August 2026 — 9,165 subscribers10 August 2026 — 9,154 subscribers11 August 2026 — 9,147 subscribers14 August 2026 — 9,133 subscribers15 August 2026 — 9,106 subscribers17 August 2026 — 9,084 subscribers18 August 2026 — 9,081 subscribers20 August 2026 — 9,063 subscribers21 August 2026 — 9,062 subscribers23 August 2026 — 9,026 subscribers24 August 2026 — 9,011 subscribers26 August 2026 — 9,005 subscribers27 August 2026 — 9,002 subscribers29 August 2026 — 8,976 subscribers29 August 2026 — 8,978 subscribers1 September 2026 — 8,977 subscribers2 September 2026 — 8,974 subscribers4 September 2026 — 8,958 subscribers5 September 2026 — 8,954 subscribers10 September 2026 — 8,897 subscribers11 September 2026 — 8,886 subscribers13 September 2026 — 8,854 subscribers14 September 2026 — 8,848 subscribers18 September 2026 — 8,828 subscribers19 September 2026 — 8,826 subscribers7 August 202619 September 2026
27 measurements spanning 43 days, net -340. 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 8,775–9,219 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
19 Sept 2026, 10:598,826-2
18 Sept 2026, 10:018,828-20
14 Sept 2026, 17:188,848-6
13 Sept 2026, 21:218,854-32
11 Sept 2026, 02:218,886-11
10 Sept 2026, 06:558,897-57
5 Sept 2026, 23:188,954-4
4 Sept 2026, 14:148,958-16
2 Sept 2026, 00:158,974-3
1 Sept 2026, 07:448,977-1
29 Aug 2026, 21:078,978+2
29 Aug 2026, 10:148,976-26
27 Aug 2026, 07:269,002-3
26 Aug 2026, 13:219,005-6
24 Aug 2026, 15:429,011-15
23 Aug 2026, 10:279,026-36
21 Aug 2026, 06:059,062-1
20 Aug 2026, 07:429,063-18
18 Aug 2026, 05:129,081-3
17 Aug 2026, 12:179,084first reading

Engagement

15 posts held, back to 6 March 2025the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 31 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
2.38%
avg views ÷ 8,826 subscribers
Avg views / post
210
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 15 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 26 August 2026
Posts held15 (6 March 202526 August 2026)
Views total210
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 15:40 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

18 reactions across 4 posts, in 5 distinct kinds. The most used accounts for 38.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
738.9%
👍422.2%
👎316.7%
💩316.7%
🔥15.56%

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

Measured over the 15 most recent posts we hold, published 6 March 2025 to 26 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

26 Aug 2026, 11:08 UTC210 viewsread 28 August 2026

@dd1234445 300通用券,先到先得,需写报告,直接联系老师说晨钟暮鼓看到的即可

8 Aug 2026, 09:45 UTC≈1,180 viewsread 28 August 2026

@dd1234445 半价券,需要写工兵报告,老师要求今晚出击,有需要的私聊兑奖机器人即可 @MuChenChannel_bot 已兑

1 Aug 2026, 12:00 UTC≈1,630 viewsread 28 August 2026

抽奖@zz52178 龙华妞妞半价券(编号L178551239801)已成功开奖: 创建人:hate[6509055996] 已参与人数:31 中奖名单如下: George[6753617612](奖品为半价券)

31 Jul 2026, 15:45 UTC≈1,740 viewsread 28 August 2026

🎟️ 抽奖标题:@zz52178 龙华妞妞半价券 📪抽奖说明:中奖者机器人会发送中奖信息 🎫 参与条件: 🎫 加入-妞妞 🎫 加入-深圳·晨钟暮鼓 🎫 加入-深圳晨钟暮鼓(优惠及地址汇总) 🎁 奖品内容: 💰️ 半价券 × 1 📅 开奖时间:2026-08-01 20:00自动开奖 👉 参与抽奖链接: https://t.me/CzmgBot?start=join-L178551239801

29 May 2026, 06:25 UTC≈3,410 viewsread 28 August 2026

@missyikui 这个一葵的号登不上了,可能被盗了,谨防受骗 @yikuimiss 目前一葵是这个新号

27 May 2026, 07:34 UTC≈3,840 viewsread 28 August 2026

@Sshi2006 休息中 @yyy66116 已兑完 有半价券,需出报告,500积分可兑,联系机器人或者管理 @MuChenChannel_bot

29 Apr 2026, 01:37 UTC≈4,360 views0 reactionsread 28 August 2026

https://lhweb.jjjxgc.com/#/register?code=3BFSa7Ds 蓝海vpn ,自用1年 https://mgjc.top/#/register?code=AlNXKsda 芒果云,便宜vpn 付费3个月,暂时没有出现问题 https://t.me/longmaoyun 龙猫云邀请码JRJCJEEZ 稳定vpn可在下方留言

16 Apr 2026, 08:24 UTC≈4,410 viewsread 28 August 2026

原认证榜单未解除18禁查看不了 现在更新新的认证榜单 榜单id不变 无限制认证榜单 https://t.me/czbd10 老榜单 https://t.me/+4i0_WMpR0ek1NTZk

14 Apr 2026, 00:18 UTC≈4,870 views2 reactionsread 28 August 2026
Photo

福田云熙 @jinli9992 300通用券✖️3 需写报告,直接联系老师约课即可 频道: https://t.me/jinli887

2

31 Oct 2025, 08:34 UTC≈12,100 views0 reactionsread 28 August 2026
Photo

https://t.me/czbd10/6488?comment=7614 https://t.me/czbd10/6 没见到人切勿给全款,定金最多100,认准榜单,在群里不等于上榜 上榜请查看 @czbd10

23 Mar 2025, 12:23 UTC≈14,500 views2 reactionsread 28 August 2026

优惠卷兑换列表(约好课再兑换) ☀️晨钟暮鼓🌙兑奖助手🤖 限量优惠券需要599积分兑换 🚀南山千惠 100 🚀南山梨花 200 🚀福田倪妮 200 🚀福田林晚樱 200 常驻优惠券 200券499积分兑换 100券300积分兑换 南山: 🚀静崽200 🚀甜心酱200 🚀梦珂200 🚀小QT 200 福田: 🚀婉妮100 🚀一克拉100 🚀财月200 🚀黎巴啦200 🚀姜娜200 🚀KK兔 200 🚀柿子200 🚀元气妹妹200 宝安: 🚀旺仔牛奶200(限PP) 100(限P) 晨钟暮鼓备用(优惠券及地址汇总频道):@CZMGBY

1👍1

6 Mar 2025, 07:57 UTC≈10,300 views1 reactionsread 28 August 2026

地区 南山 福田 宝安 罗湖 龙岗 龙华

1

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

@czmgby edited 1 post 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
8 August 2026
Most recent edit
8 August 2026

Mentions

Named by 2 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.

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

“深圳晨钟暮鼓(优惠及地址汇总)” (@czmgby), 8,826 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/czmgby.

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.