Supergroup
Huidu.io 灰度台灣遊戲圈
@huiduiotw
On this record: Topic · Growth · Engagement · Citations · Cite this entry
2,482members
-85 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001622033981 |
|---|---|
| Type | Supergroup |
| Username | @huiduiotw |
| Description | 🇹🇼 台灣 BC・iGaming B2B 資源交流 聚集熟悉 BC / iGaming 平台、營運與系統整合 的從業者， 交流 產品方案、API 串接與技術資源。 🔹 核心交流 平台方案｜系統整合｜資料接口｜營運工具 🚫 詐騙、誘導式行銷、低品質廣告 ⚠️ 入群請先閱讀置頂規範，違規即移除 #BC #iGaming #平台營運 #API整合 #B2B交流 【官方】 www.huidu.io/zh-TW/ 【服務】 @huiducn 【商務】 @huiduTom8 ｜ @hdjoanna |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 16 September 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 14 |
| On Telegram | t.me/huiduiotw |
Topic
Marketing & affiliate — 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 16 September 2026 and assigned it the closest of 31 fixed categories, at 47% 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
| Measured (UTC) | Members | Change |
|---|---|---|
| 16 Sept 2026, 00:06 | 2,482 | no change |
| 15 Sept 2026, 13:01 | 2,482 | -3 |
| 11 Sept 2026, 19:41 | 2,485 | -20 |
| 7 Sept 2026, 12:16 | 2,505 | -14 |
| 2 Sept 2026, 09:44 | 2,519 | -6 |
| 30 Aug 2026, 07:54 | 2,525 | -6 |
| 27 Aug 2026, 11:15 | 2,531 | -3 |
| 24 Aug 2026, 05:47 | 2,534 | -5 |
| 20 Aug 2026, 15:26 | 2,539 | -6 |
| 17 Aug 2026, 17:26 | 2,545 | -1 |
| 14 Aug 2026, 17:28 | 2,546 | -21 |
| 11 Aug 2026, 06:55 | 2,567 | +4 |
| 7 Aug 2026, 20:12 | 2,563 | -4 |
| 7 Aug 2026, 06:51 | 2,567 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.
Mentions
Named by 3 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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“Huidu.io 灰度台灣遊戲圈” (@huiduiotw), 2,482 members as measured 16 September 2026. Telegram Register, tgregister.com/channel/huiduiotw.
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.