今天,明天,后天 有什么区别吗

Channel
LazyCatCloud☁️|Notice
@lazycat_notice
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,582subscribers
+102 since we began measuring on 10 September 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1003198894624 |
|---|---|
| Type | Channel |
| Username | @lazycat_notice |
| Created | Between 1 October 2025 and 31 December 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 September 2026 |
| Last confirmed live | 29 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 29 September 2026 |
| On Telegram | t.me/lazycat_notice |
Topic
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 29 September 2026 and assigned it the closest of 31 fixed categories, at 70% 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) | Subscribers | Change |
|---|---|---|
| 29 Sept 2026, 01:54 | 1,582 | +77 |
| 19 Sept 2026, 09:19 | 1,505 | +20 |
| 15 Sept 2026, 04:40 | 1,485 | +6 |
| 11 Sept 2026, 18:40 | 1,479 | -1 |
| 10 Sept 2026, 03:22 | 1,480 | first reading |
Engagement
20 posts held, back to 19 August 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.
- ERR · 30 days
- 34.1%
- avg views ÷ 1,582 subscribers
- Avg views / post
- 539
- 3 posts measured
- Reaction rate
- 0.399%
- reactions ÷ views · ER floor
- Posts in window
- 3
- of 20 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 2 of 3 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 9 September 2026 |
|---|---|
| Posts held | 20 (19 August 2026 – 9 September 2026) |
| Views total | 1,618 |
| Reactions total | 5 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Sept 2026, 03:22 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Reaction mix
90 reactions across 11 posts, in 7 distinct kinds. The most used accounts for 46.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤡 | 42 | 46.7% | |
| ❤ | 15 | 16.7% | |
| 🔥 | 14 | 15.6% | |
| 😁 | 10 | 11.1% | |
| 🌭 | 6 | 6.67% | |
| 👍 | 2 | 2.22% | |
| 🎉 | 1 | 1.11% |
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 12 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 90 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 19 August 2026 to 9 September 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
晚安💤各位猫猫🐱们
🤡5
📣UK-ISP发布 ⚠️非中国大陆优化,走普通线路国际优化 🔝英国原生双ISP IP,国际方向接入GTT全球骨干 不承诺中国大陆方向优化及质量 ⚡️禁止一切BT下载,版权文件,如有重度Abuse删机不退款 💵配置价格: UK Mini 3元 UK Basic 5元 ⬇️主打大流量 有需求的可以买 订购链接:https://dash.lazycat.wiki/instances/create/gb/51
📣HKT更变通知 ⚠️因HKT是家里云,硬件性能无法撑下当前运行的容器 对此觉得我们将更换机器 ⚡️模式改为IDC IN - HKT out 和之前的家宽机器一样 配置稍微改动一下,增加内存
📣最新进展 ⚠️目前已迁移完成,并且恢复现有用户的实例 更变后的价格 所有套餐加量加大 根据参考隔壁uzuma,最后决定 定价下降50%,现有用户也可享受降价 ⚡️配置价格详情: Starhub Nano 30降至15 Starhub Mini 50降至25 Starhub Basic 70降至35 ☄️配置调整: Starhub Nano 内存128变为256M 硬盘变为1GB 流量增加至500GB 带宽为500Mbps Starhub 内存变为384M 流量增加至600GB 带宽为1000Mbps Starhub Basic 固定不变,带宽升级为2Gbps
📣Starhub动态家宽产品线调整通知📣 ⚠️因销量和其他问题,导致此产品一直处于无人问津状态 我们进行了商讨,决定放弃Hosthatch SG的入口 更换接入Panstar SG Lite的机器作为入口 ⚡️移动直连优化接入Lumen,电联也能玩,速度不低 但定位还不是优化机,请注意啦 国际互联优秀接入Akari、RETN、GSL等优秀互联网交换点⚡️ 🌐后续也会把现有Starhub的用户迁移过去 产品售卖价格也会进行相对于调整,来保持正常运营 同时现有的用户也会进行价格调整(不是涨价) 🔔当然Starhub家宽出口还是带的 入口机器参考:https://www.nodeseek.com/post-910510-1 感谢各位用户对LazyCatCloud的支持😄
📣LazyCatCloud面板更新公告📣 为了LazyCatCloud的持续稳定运行 防止各用户滥用带宽资源和IP行为 我们特此推出了最新的安全监控系统 👑ArbiterX👑 ArbiterX此系统会监控各个机器的滥用行为 比如:发包,持续高量的TCP连接,持续高量带宽行为 ssh爆破、IP入站数量等⚠️ 为了各位用户的安稳使用和减少滥用风险 此系统后续会一直更新新策略来审查漏网之鱼👍 感谢各位用户选择支持LazyCatCloud 感谢有你!😘
🤡20
US-Premium又一次重置流量 HK-Lumen重置流量 JP-Lite 1-3重置流量 Frontier 1-2重置流量 Hinet 1-2重置流量 感谢各位用户对LazycatCloud的信任和选择 一路有你们真好
📣关于SoftBank问题 1.因为公寓管理公司不让多拉光纤,可能会更换至GLBB动态家宽👍 2.目前暂定方案是额外租用农村独户拉光纤宽带,Asahi和Softbank可能都会拉🫡 3.如果GLBB动态家宽能拉,那么后续租的独户拉的Asahi和Softbank可能会出新产品😘 ⚠️总结:非常大概率99.99%不会清退,除非留子不干了,只是需要时间等待,你小日子办事效率就是慢,拖一个月都有可能。
🔥9❤3
US-Premium重置流量
❤3
US-Premium已重置流量
📣新上:HK-Lumen 线路:PCCWG+TELSTRA+NTT+Lumen+Cogent+HE+EIE,面向中国移动网络访问香港业务的优化线路 电联绕美介意勿买,只有移动可玩 👍购买连接:https://dash.lazycat.wiki/instances/create/hk/50
🤡3
Showing the 12 most recent of 20 posts we hold for @lazycat_notice. 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.
Forward network
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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 29 September 2026 — this entry's latest reading, not the date you are reading this.
“LazyCatCloud☁️|Notice” (@lazycat_notice), 1,582 subscribers as measured 29 September 2026. Telegram Register, tgregister.com/channel/lazycat_notice.
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.