Telegram RegisterThe public register of Telegram
Telegram profile photo for 云闹钟战斗机 - 免费短信轰炸-戰鬥機-轟炸機

Channel

云闹钟战斗机 - 免费短信轰炸-戰鬥機-轟炸機

@hzaaccc

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

47,422subscribers

-517 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001819277894
TypeChannel
Username@hzaaccc
CreatedBetween 1 October 2022 and 24 July 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 August 2026
Measurements held10
Confirmed unchanged1 time, most recently 17 August 2026
On Telegramt.me/hzaaccc

Growth

47,42247,93947,680.57 August 2026 — 47,939 subscribers8 August 2026 — 47,914 subscribers9 August 2026 — 47,858 subscribers10 August 2026 — 47,801 subscribers11 August 2026 — 47,755 subscribers12 August 2026 — 47,693 subscribers13 August 2026 — 47,648 subscribers14 August 2026 — 47,588 subscribers16 August 2026 — 47,519 subscribers17 August 2026 — 47,422 subscribers7 August 202617 August 2026
10 measurements spanning 10 days, net -517. 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 47,344–48,017 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Aug 2026, 13:4747,422-97
16 Aug 2026, 07:0347,519-69
14 Aug 2026, 14:1347,588-60
13 Aug 2026, 06:2547,648-45
12 Aug 2026, 09:0247,693-62
11 Aug 2026, 06:3247,755-46
10 Aug 2026, 06:1647,801-57
9 Aug 2026, 05:0247,858-56
8 Aug 2026, 04:3647,914-25
7 Aug 2026, 13:4547,939first reading

Engagement

19 posts held, back to 24 July 2023the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 24 pagesof 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 19 posts for this entry, the most recent from 14 November 2023. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
55s
Average length
28s

Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

10,628 reactions across 19 posts, in 29 distinct kinds. The most used accounts for 30.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤡3,21430.2%
👍2,06619.4%
👎1,29012.1%
💩1,0289.67%
9739.16%
🖕5084.78%
😁3493.28%
😱2952.78%
😭2242.11%
👏1551.46%
🤣940.884%
🤬550.518%
🤯470.442%
🥰460.433%
🤪400.376%
🤮400.376%
🗿370.348%
😢350.329%
🤔320.301%
🍌200.188%
9 further kinds800.753%

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 10,628reactions 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 24 July 2023 to 14 November 2023, 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

14 Nov 2023, 04:05 UTC≈287,000 views3,872 reactionsread 17 August 2026

已恢复。

🤡2,330🖕444👍306💩280134👎100🤣94😱55

14 Nov 2023, 02:00 UTC≈283,000 views829 reactionsread 17 August 2026

机器人故障短信服务暂不可用,预计今天恢复。

👎329💩144👍12893🖕64🥰22😁17🍌12

23 Oct 2023, 03:52 UTC≈296,000 views918 reactionsread 17 August 2026

电话轰炸最新地址 https://tel-alarm.top/vip/index.html 暂无电话轰炸

278💩188👍182😁145👎81👏21🥰16🍌7

13 Oct 2023, 10:50 UTC≈266,000 views552 reactionsread 17 August 2026

机器人已恢复,这次增加了多台服务器增强了轰炸效果

👍350💩10040👎32😁19🙊6🤡4🤔1

11 Oct 2023, 18:57 UTC≈237,000 views442 reactionsread 17 August 2026

机器人维护中,请勿使用

👎244💩5931🤡23👍22😁16👌15🤔10

11 Oct 2023, 04:07 UTC≈216,000 views195 reactionsread 17 August 2026

机器人维护中,短信通道暂不可用。

💩155👍1412😁9🤡5

15 Aug 2023, 10:01 UTC≈279,000 views1,807 reactionsread 17 August 2026

由于原机房故障数据丢失导致无法恢复。现已购买新的服务器恢复了相关服务,不幸的是我们所有的数据丢失了,目前数据库恢复到了6月12日。 ⚠️⚠️⚠️如果您在6月12日到8月12日期间存在充值,邀请积分丢失,若需要积分恢复的情况,请于2023年8月18日23:59:59前联系客服申请恢复,过后将不再提供恢复功能,群聊功能将在本周或下周恢复⚠️⚠️⚠️ (充值用户携带订单信息可正常恢复) ⚠️⚠️⚠️携带正确信息优先恢复,请看准客服所需要的信息⚠️⚠️⚠️ 付费用户充值记录截图,8月11号前最新的tg机器人积分信息与等级截图(带上消息时间),为了提高恢复效率,请大家申请恢复时粘贴提供您的uid,提供uid与积分信息截图可优先处理(机器人中发送/my可以查看复制))。 没有截图,与机器人ID将无法处理 请认准当前只有两个客服号!!!! 客服1回家种地了,明天回来 客服2 @boom666002(+86手机区号客户请重新联系此客服)

🤡702👍492192👎143💩74🤬38🗿37🤮35

12 Aug 2023, 14:23 UTC≈142,000 views286 reactionsread 17 August 2026

由于数据量过于庞大,客服已连续处理6个小时,目前暂时回复不过来,我们会针对留言逐步处理,这个耗时可能会比较长。

👎150👍54🤡3717🤯13😁6🤮5👏4

12 Aug 2023, 06:34 UTC≈133,000 views324 reactionsread 17 August 2026

服务器已经恢复,机器人正在调试中,但是很不幸的是硬盘服务器硬盘炸了,数据可能丢失,我们正在尝试恢复用户数据,如果恢复失败我们会给出相应的解决方案。

😭194👎38🤡25👍18🤬179🐳6🔥6

11 Aug 2023, 13:07 UTC≈123,000 views466 reactionsread 17 August 2026

汇报一下:现在机房拉闸,且无法联系上机房。所以今晚是否能够恢复是个未知数。若今晚机房还未恢复,明天就开始购买新的服务器部署服务。

😱236👎63👍47🤡42💩2414🕊11🎉9

11 Aug 2023, 10:50 UTC≈110,000 views159 reactionsread 17 August 2026

机房突然维护,大家耐心等待一下。

👎83😢28👍1913🤯9👏7

9 Aug 2023, 08:57 UTC≈105,000 views189 reactionsread 17 August 2026
Photo

Photo, posted without a caption

👍11640👎25😁7👏1

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

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

“云闹钟战斗机 - 免费短信轰炸-戰鬥機-轟炸機” (@hzaaccc), 47,422 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/hzaaccc.

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.