AS4242423374 已适配 DN42 Peer finder 的 Global Latency Measurement 功能。 #dn42

Channel
Baka.Pub Network
@BakaNetwork
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
38subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001532891326 |
|---|---|
| Type | Channel |
| Username | @BakaNetwork |
| Description | DN42 dn42.baka.pub / AS4242423374 IANA net.baka.pub / AS214933 |
| Created | Between 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/BakaNetwork |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 21:16 | 38 | no change |
| 8 Aug 2026, 06:49 | 38 | first reading |
Engagement
20 posts held, back to 26 May 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
- 269.7%
- avg views ÷ 38 subscribers
- Avg views / post
- 103
- 4 posts measured
- Reaction rate
- 3.05%
- reactions ÷ views · ER floor
- Posts in window
- 5
- 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 4 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 30 July 2026 |
|---|---|
| Posts held | 20 (26 May 2026 – 30 July 2026) |
| Views total | 410 |
| Reactions total | 10 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Aug 2026, 21: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.
What this channel posts
- Photos
- 10
- Links
- 27
Lifetime counters from Telegram’s own channel header, read 10 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Reaction mix
24 reactions across 7 posts, in 5 distinct kinds. The most used accounts for 37.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😱 | 9 | 37.5% | |
| ❤ | 8 | 33.3% | |
| 👍 | 4 | 16.7% | |
| 😭 | 2 | 8.33% | |
| 👌 | 1 | 4.17% |
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 24reactions 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 26 May 2026 to 30 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.
Recent posts
出于安全原因,AS214933 将在近期退出 BGP.Exchange。 #clearnet
Posted without readable text
#dn42 入门节点地区怎么选
👍4
AS4242423374 的香港主节点受到 GFW 阻断。 目前 AS4242423374 位于中国大陆的流量均途径或绕路上海阿里云节点,延迟和丢包可能上升,敬请谅解。 #dn42
😱4😭2
现可在 https://irr.baka.dn42 获取 RIR Statistics Exchange 格式的存档。 #dn42
荷兰节点疑似遭到入侵,正在排查。 排查完毕,正常现象。 #dn42
😱5
目前,我们已更换所有节点的 Agent。 当您在通过 @baka_lg_bot 操作遇到问题是,请联系 @bakabakabing 直接反馈。 #dn42
日本节点已更换为新版 Agent,如通过 Bot 与日本节点交互时遇到问题请联系 @bakabakabing 直接反馈。 #dn42
因技术原因,当前日本节点的 Bot Agent 未能顺利运行,预计需要一至两天重新部署 Bot Agent。 仅自动对等 / 修改受到影响,不影响已有 Peer。 #dn42
Whois 服务器现已支持 RDAP,参见此页面。 这是一项测试服务!此服务可能存在大量错误,我们正在快速追踪和修复它们! #dn42
DNS Center 已结束前期测试,我们预计在七月上旬完成技术测试和内部测试,并在七月下旬开放 Beta 测试,敬请期待。 #dn42
❤3
Showing the 12 most recent of 20 posts we hold for @BakaNetwork. 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.
Mentions
Names
Channels on the register whose handles appear in this channel's posts.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“Baka.Pub Network” (@BakaNetwork), 38 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/BakaNetwork.
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.