Telegram RegisterThe public register of Telegram
Telegram profile photo for 华夏联盟 IDC👺

Channel

华夏联盟 IDC👺

@huaxiaidc

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

85subscribers

-3 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-1002325847894
TypeChannel
Username@huaxiaidc
Created4 March 2025 — measured — dated from the channel’s first post
First recorded9 August 2026
Last confirmed live12 October 2026
Measurements held6
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/huaxiaidc

Topic

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

838885.57 August 2026 — 88 subscribers9 August 2026 — 88 subscribers16 August 2026 — 86 subscribers24 August 2026 — 84 subscribers9 September 2026 — 83 subscribers12 October 2026 — 85 subscribers857 August 202612 October 2026
6 measurements spanning 66 days, net -3. 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 82–89 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Oct 2026, 12:3185+2
9 Sept 2026, 03:0083-1
24 Aug 2026, 11:5784-2
16 Aug 2026, 05:5286-2
9 Aug 2026, 15:3288no change
7 Aug 2026, 15:1088first reading

Engagement

16 posts held, back to 4 March 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 16 posts for this entry, the most recent from 6 August 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

34 reactions across 6 posts, in 17 distinct kinds. The most used accounts for 23.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍823.5%
❤38.82%
🤣38.82%
🎃25.88%
🐳25.88%
👏25.88%
🤔25.88%
🥰25.88%
🫡25.88%
💯12.94%
😇12.94%
😎12.94%
🤓12.94%
🤝12.94%
🤪12.94%
🤷‍♂12.94%
🥱12.94%

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

Measured over the 16 most recent posts we hold, published 4 March 2025 to 6 August 2025, 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 2025, 13:06 UTC485 viewsread 9 August 2026

日本IIJ NAT服务器已上架 12.88每月 订购地址 idc.huaxia.cyou

30 Jul 2025, 04:03 UTC444 views1 reactionsread 9 August 2026

目前内测中,预计今天至明天开始上线

❤1

23 Mar 2025, 12:19 UTC542 views4 reactionsread 9 August 2026

日本樱花ijj现在政策变了,现在是季付机器了

❤1🎃1👍1💯1

16 Mar 2025, 11:21 UTC610 views2 reactionsread 9 August 2026

目前已上架新品 云电脑 idc.huaxia.cyou

❤1👍1

16 Mar 2025, 11:21 UTC588 viewsread 9 August 2026

之前的网站因为服务器的问题导致数据丢失,现在已经换成稳定的服务器,之前已购买的服务器不受影响,可联系客服重新迁移到本网站

6 Mar 2025, 14:51 UTC928 views6 reactionsread 9 August 2026

# 《AWS光帆服务器上架及优惠信息公告》 尊敬的用户: 您好!现向您通报关于AWS光帆服务器的最新动态及相关优惠信息。 服务器上架情况:AWS光帆服务器已在大部分地区完成上架,这意味着您在更多区域都能享受到我们优质、高效的服务器服务,满足您多样化的业务需求。 折扣惊喜:为回馈广大客户,我们特别推出折扣服务器活动!现在下单,即可享受专属折扣优惠,让您以更实惠的价格获取高性能的服务器资源,助力您的业务腾飞。 便捷服务:下单后,我们将为您提供直开服务器的便捷服务,无需繁琐等待,快速开启您的云端之旅。同时,我们的服务器支持长期续费,您无需担心使用期限问题,可安心专注于业务发展,我们将持续为您提供稳定、可靠的服务支持。 联系我们:如果您对AWS光帆服务器有任何疑问或需要进一步了解相关信息,欢迎随时与我们联系。您可以通过以下方式与我们取得联系: - 网站: midc.huaxia.cyou idc.huaxia.cyou …

🐳2🤣2👍1🥱1

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

“华夏联盟 IDC👺” (@huaxiaidc), 85 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/huaxiaidc.

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.