5 measurements spanning 23 days, net +1. 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 871–877 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
30 Aug 2026, 15:55
873
-3
23 Aug 2026, 07:37
876
+3
15 Aug 2026, 00:18
873
+1
8 Aug 2026, 01:16
872
no change
7 Aug 2026, 15:10
872
first reading
Engagement
20 posts held, back to 6 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 pageof Telegram’s post history, 20 posts per page.
ERR · 30 days
35.7%
avg views ÷ 873 subscribers
Avg views / post
312
2 posts measured
Reaction rate
1.12%
reactions ÷ views · ER floor
Posts in window
2
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 1 of 2 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 6 August 2026
Posts held
20 (6 April 2026 – 6 August 2026)
Views total
623
Reactions total
3
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
8 Aug 2026, 01:16 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
8 reactions across 6 posts, in 2 distinct kinds. The most used accounts for 62.5% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
5
62.5%
👍
3
37.5%
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 7 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 8reactions 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 6 April 2026 to 6 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.
网卡更换完成。我们为宿主机跟换了Intel XL710网卡,以便更高的稳定性。VM批量开机中 如果您着急可以前往面板手动开机
The NIC replacement is complete. We replaced the bare metal with an Intel XL710 NIC to ensure greater stability.
VM are bulk powering on; if you are in a hurry, you can go to the panel to start it manually.
ネットワークカードの交換が完了しました。安定性を向上させるため、ホストマシンのネットワークカードをIntel XL710モデルに交換しました。
VMは起動中です。お急ぎの場合は、パネルから手動で起動することもできます。
ref: https://www.cisco.com/c/dam/en/u…
#通知
JP 网络维护通知
由于 JP 节点网卡异常,导致部分用户出现丢包及网络波动情况。
我们计划于 2026 年 8 月 6 日 18:00 - 19:00(日本时间 UTC+9)进行网卡更换维护。
本次维护涉及 JP BGP / JPCNT 网络。维护期间可能出现短暂网络中断、丢包、延迟升高或路由收敛等情况。
维护期间无需用户侧操作,我们将持续关注维护进度,如有变化将及时同步。
⸻
Scheduled Network Maintenance for JP
Due to a network card issue on the JP node causing packet loss and network instability for some users, scheduled maintenance will be performed.
The network card replacement is pl…
+ 08:45 Update: SONiC system upgrade start.
+ 08:57 Update: Almost Done!!!
+ 09:15 Update complete. Actual start time was 8:45 AM. Service recovery time was 9:18 AM.
+ Downtime: 33 mins
更新完成
lain.sh
#通知
JPC+ 东京上游计划维护通知
接上游通知,东京节点将于 2026 年 6 月 4 日 09:00 - 12:00(日本时间 UTC+9) 进行计划内网络维护。本次维护内容包括更换 ToR(Top of Rack)交换机及升级东京核心路由器。
受影响产品为 JPC+。维护期间可能出现短暂网络中断、丢包、延迟升高或路由收敛等情况。维护期间无需用户侧操作,我们将持续关注上游维护进度,如有变化将及时同步。
⸻
Scheduled Upstream Maintenance for JPC+
According to the upstream provider’s notice, scheduled network maintenance will be performed in Tokyo on 2026-06-04 09:00 - 12:00 JST / UTC+9.
The maintenance includ…
#通知
HK 区域网络故障说明
目前 HK 区域一台核心设备突发故障,导致部分业务网络出现异常波动或中断。
我方已在进行线路切换与故障隔离,预计切换完成后网络将陆续恢复。期间可能出现短暂丢包、延迟升高或连接不稳定。
请受影响用户耐心等待恢复,后续如有进一步进展将另行通知。
lain.sh
已恢复
downtime: ~45mins
Showing the 12 most recent of 20 posts we hold for @lain_log. 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 30 August 2026 — this
entry's latest reading, not the date you are reading this.
“Lain_Notification” (@lain_log), 873 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/lain_log.
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.