Telegram RegisterThe public register of Telegram
Telegram profile photo for LeiKwan Host What's New|利群主機新鮮事

Channel

LeiKwan Host What's New|利群主機新鮮事

@leikwanhost

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

883subscribers

-96 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-1002597761420
TypeChannel
Username@leikwanhost
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live13 October 2026
Measurements held10
Confirmed unchanged1 time, most recently 13 October 2026
On Telegramt.me/leikwanhost

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 19 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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

883980931.57 August 2026 — 979 subscribers7 August 2026 — 980 subscribers8 August 2026 — 980 subscribers15 August 2026 — 932 subscribers24 August 2026 — 913 subscribers30 August 2026 — 914 subscribers9 September 2026 — 908 subscribers17 September 2026 — 896 subscribers2 October 2026 — 891 subscribers13 October 2026 — 883 subscribers7 August 202613 October 2026
10 measurements spanning 67 days, net -96. 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 868–995 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Oct 2026, 14:08883-8
2 Oct 2026, 19:39891-5
17 Sept 2026, 16:59896-12
9 Sept 2026, 03:14908-6
30 Aug 2026, 11:17914+1
24 Aug 2026, 10:03913-19
15 Aug 2026, 19:22932-48
8 Aug 2026, 00:45980no change
7 Aug 2026, 23:12980+1
7 Aug 2026, 18:40979first reading

Engagement

20 posts held, back to 17 April 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 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 20 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

40 reactions across 8 posts, in 10 distinct kinds. The most used accounts for 42.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1742.5%
🥰615.0%
👍410.0%
🌭37.50%
💯25.00%
😁25.00%
🤣25.00%
🤯25.00%
👎12.50%
🔥12.50%

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

Measured over the 20 most recent posts we hold, published 17 April 2026 to 7 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

7 Aug 2026, 16:35 UTC149 viewsread 8 August 2026

- Luckybot 家寬出口變更 / 滬台 SDWAN 下綫 - - Changes to Home Broadband Routing of Luckybot / Exit of Shanghai-Taiwan SDWAN - https://square.leikwanhost.com/forum-post/585.html

30 Jul 2026, 17:48 UTC489 views1 reactionsread 8 August 2026

- 利群人工智慧試運行 - - Trial Operation of LeiKwan AI - 細則與價格 Details and Price: https://square.leikwanhost.com/forum-post/584.html 不關心! 直接體驗! EXPERIENCE NOW: https://ai.leikwanhost.com/

❤1

25 Jul 2026, 06:18 UTC646 views0 reactionsread 8 August 2026

- 網站維護時段 - - Webserver Down for Maintenance Period - 由於原有服務器租約到期, 利群主機網站將進行主機遷移. Due to the expiration of web sesrver colocation, there is an upcoming migration for LeiKwan Host webs. 影響範圍: Scope of interruption: 利群廣場、Buy 站、LuckyBot 之有價功能 (轉發、家寬出口的配置)、Hiternet Bot. LeiKwan Square, Buy Site, Value-related Functions of Lucky Bot, Hiternet Bot. 預估影響時間: Estimated Downtime: 20260726 0015 (UTC+8) – 20260726 1230 (UTC+8)…

21 Jul 2026, 14:26 UTC700 viewsread 8 August 2026

- 利群主機一周年 - - 1st Anniversary of LeiKwan Host - 一載,默以致遠。 Silent service, lasting strength. 當然, 也並非毫無笙簫. 您可參加新品預定: https://square.leikwanhost.com/forum-post/569.html

7 Jul 2026, 17:41 UTC959 viewsread 8 August 2026

服務器遇到了故障, 待白天修復完畢後再作補償Fixed.

7 Jul 2026, 16:43 UTC800 views1 reactionsread 8 August 2026
Photo

https://square.leikwanhost.com/forum-post/353.html

🔥1

7 Jul 2026, 15:54 UTC640 views1 reactionsread 8 August 2026

- 安全補丁所致服務中斷 - - Patch Reload Caused Upcoming Service Interruption - 為應用 CVE-2026-53359 補丁修復問題, 現計劃于 2026-07-08 0100 - 0130 UTC+8 間對宿主機進行更新應用套取. 期間服務中斷屬於正常現象. To apply the batch for the bug of CVE-2026-53359, now we've planned a reboot from 2026-07-08 0100 - 0130 UTC+8 on the main server. Unavailability during that time is normal. 影響範圍: 上海 CN2/9929/SDWAN/Hiternet. (浦東電信、上海單綫、廣州單綫、廣州多綫不受影響) Scope of Interruption: S…

❤1

4 Jul 2026, 16:11 UTC763 views17 reactionsread 8 August 2026

7·8 集霸节 (集霸们先导版) 🐎 马年初创版返厂 & 成长回归 🌐 Hiternet 全体优化升级 🎁 喜闻乐见抽奖活动 (含 💥 9929 大口径特殊产品限量售卖资格) 🏠 家宽出口自选 🎁 Hiternet 福利升级 7·8 见,这次是真 · 狠狠干一波大的 🔥

❤11🌭3😁2👍1

28 Jun 2026, 10:45 UTC978 views12 reactionsread 8 August 2026

家人们谁懂啊,这次真的不是普通更新,是扛过大考后的系统进化 + 集霸节前夜的全面狂欢 —— 集美有 3·8 节,集霸当然也必须拥有自己的高光时刻:7·8 集霸节正式提上日程,而且还是「利群主机 7·8 集霸节暨周年活动」,活动筹备预热中 🔥

🥰6💯2🤣2🤯2

28 Jun 2026, 10:15 UTC911 viewsread 8 August 2026

- IXP 路由組維護時段 - - Scheduled Maintenance on IXP Routing - https://square.leikwanhost.com/forum-post/346.html

16 Jun 2026, 14:34 UTC965 viewsread 8 August 2026

- 請 " 哪吒面板 " 用戶務必立刻更新面板 - - Please update your "Nezha Monitor" Panel ASAP - 原文: https://t.me/leikwanhostchat/180292 Source link: https://t.me/leikwanhostchat/180292 現已有兩位用戶突發一小時内爆出超過 10k 連接數, 已被停機.

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

“LeiKwan Host What's New|利群主機新鮮事” (@leikwanhost), 883 subscribers as measured 13 October 2026. Telegram Register, tgregister.com/channel/leikwanhost.

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.