专线恢复了 全体补时7天已经加上了 新买了台HKT 等会对接上去
🤮3

Channel
@lizioness
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
836subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003598096966 |
|---|---|
| Type | Channel |
| Username | @lizioness |
| Created | Between 1 December 2025 and 14 April 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/lizioness |
Other / unclassifiable — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 21:58 | 836 | -7 |
| 9 Sept 2026, 18:00 | 843 | -7 |
| 31 Aug 2026, 13:53 | 850 | -4 |
| 25 Aug 2026, 02:02 | 854 | +4 |
| 16 Aug 2026, 19:05 | 850 | +11 |
| 8 Aug 2026, 07:06 | 839 | +3 |
| 7 Aug 2026, 08:01 | 836 | first reading |
13 posts held, back to 14 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 13 posts for this entry, the most recent from 21 July 2026. An engagement rate over an empty window would be a number about nothing.
71 reactions across 13 posts, in 4 distinct kinds. The most used accounts for 66.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤮 | 47 | 66.2% | |
| 👍 | 17 | 23.9% | |
| ❤ | 5 | 7.04% | |
| 🥰 | 2 | 2.82% |
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 13 of the 13 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 71 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 14 April 2026 to 21 July 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.
专线恢复了 全体补时7天已经加上了 新买了台HKT 等会对接上去
🤮3
目前测试下来 和四月份之前没什么区别了
🤮6👍3❤2
电信单线程
🤮4
已恢复
🤮3
IEPL的项目结束了。预计还是用回透传。先别想其他的了。已经做过尝试了。行不通。。。。
🤮3
日本和新加坡不通的问题已修复。。香港家宽上线两个。
👍4🤮2
Video, posted without a caption
🤮3
全体补时7天 目前网络优化已经完成 感谢大家的陪伴与支持
🤮1
#维护通知 hkip专线产品将于6月8日进行割接维护,届时业务将出现中断。维护后将解决丢包与卡顿问题。 维护时间:2026年6月8日 02:00:00~2026年6月8日03:00:00(UTC+8) 维护原因:运营商割接维护 影响范围:hkip专线
🤮1
最新测速
👍7🤮7
是服务器电源故障,让机房现场简单重新插拔了下电源,目前已经恢复了。新的服务器电源已经在同城加急配送了,晚点会更换上 (目前已更换)
🤮2
管局无情 坤坤有情 85折优惠码: 85 月付计划已开启 商家答复下月会优化电信方向 大家一起共度难关
🤮3
Showing the 12 most recent of 13 posts we hold for @lizioness. 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.
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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“caixukun(原LiZiOne)” (@lizioness), 836 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/lizioness.
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.