Telegram RegisterThe public register of Telegram
Telegram profile photo for Egern 频道

Channel

Egern 频道

@egern_news

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry

3,405subscribers

+39 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001255717187
TypeChannel
Username@egern_news
CreatedBetween 1 March 2018 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live16 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/egern_news

Growth

3,3663,4053,385.56 August 2026 — 3,366 subscribers6 August 2026 — 3,366 subscribers6 August 2026 — 3,367 subscribers9 August 2026 — 3,379 subscribers12 August 2026 — 3,391 subscribers16 August 2026 — 3,405 subscribers6 August 202616 August 2026
6 measurements spanning 10 days, net +39. 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 3,360–3,411 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 05:473,405+14
12 Aug 2026, 10:333,391+12
9 Aug 2026, 19:023,379+12
6 Aug 2026, 16:233,367+1
6 Aug 2026, 04:463,366no change
6 Aug 2026, 04:083,366first reading

Engagement

20 posts held, back to 28 November 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
114.5%
avg views ÷ 3,405 subscribers
Avg views / post
3,900
1 post measured
Reaction rate
1.05%
reactions ÷ views · ER floor
Posts in window
1
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.

What these figures were computed from
WindowRolling 30 days · latest post in window 24 July 2026
Posts held20 (28 November 202524 July 2026)
Views total3,900
Reactions total41
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 23:26 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

Video runtime
15s
Average length
8s

Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

944 reactions across 20 posts, in 71 distinct kinds. The most used accounts for 40.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍38640.9%
18920.0%
🥰454.77%
😱131.38%
🤩111.17%
🔥101.06%
🤡101.06%
👀90.953%
😡90.953%
🙈90.953%
🎉80.847%
💯80.847%
70.742%
70.742%
🌭70.742%
👏70.742%
🤮70.742%
🥱70.742%
🦄70.742%
🆒60.636%
51 further kinds18219.3%

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 20 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 944reactions 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 28 November 2025 to 24 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

24 Jul 2026, 15:22 UTC≈3,900 views41 reactionsread 7 August 2026

Egern 更新了 App Store 版本,以下是 2.20.0 的更新内容: 新功能 · 新增 Snell 代理协议(v1–v5),支持连接复用池、obfs 混淆与 ShadowTLS,可解析 Clash(`type: snell`)与 Surge 配置 · 新增 SSH 出站代理,支持密码 / 私钥认证与 host key 校验 · 新增 SOCKS5 over TLS 协议 · 新增 VMess / VLESS 的 gRPC(Gun)传输,并针对高延迟链路优化下载速度 · Trojan、AnyTLS、HTTPS 新增 REALITY 支持,含 X25519MLKEM768 抗量子密钥交换,可从分享链接与 Clash 订阅导入 · 新增服务器证书 SHA-256 指纹固定,支持 Trojan、AnyTLS、HTTPS、Hysteria2、TUIC 及 VMess(HTTP/2、TLS、WSS) · 所有策略组类型均可直

👍3010🎉1

24 May 2026, 10:24 UTC≈13,400 views52 reactionsread 7 August 2026

Egern 更新了 App Store 版本,以下是 2.19.0 的更新内容: 新功能 · 智能策略组:根据延迟、抖动和稳定性对节点评分,并持续学习;各子策略权重系数可让你调整选择倾向 · Clash / mihomo 订阅格式 · IPv6 Fake IP(需启用 IPv6) · 图库中可按组件单独选择尺寸(小 / 中 / 大;iPad 还支持超大) · 模块列表图标及开关切换;无图标模块以字母头像兜底 · 各策略组可设置 latency_test_url,自定义延迟 / 健康检查 URL · KeyValue 编辑器支持导入 / 导出 · 连接详情中显示本地端口 · 资源下载可取消:离开页面或重新触发会中止前一个任务 · 网络变化通知现在会显示蜂窝网络的无线制式(LTE / NR / WCDMA 等) · SOCKS5 UDP 中继流量纳入速率和单连接统计 改进 · 重写域名规则匹配器:精确匹配约 10 倍、后缀匹

👍3616

13 Apr 2026, 13:34 UTC≈17,400 views48 reactionsread 7 August 2026

Egern 更新了 App Store 版本,以下是 2.18.0 的更新内容: 新功能 · 首页新增快捷操作按钮,支持快速添加订阅、扫码添加代理、导入配置等常用操作 · 新增代理专用 DNS 解析器,支持为代理连接指定独立的加密 DNS(DoH/DoT/DoQ/H3),告别明文 DNS · URL 重写的 reject 类型现在直接返回对应 HTTP 响应,无需额外重定向 · 支持导入 Surge 完整配置文件和 Loon 配置及插件 · 支持通过 URL 导入 SOCKS5、HTTP、HTTPS 代理节点 · VLESS/VMess 支持自定义字符串作为用户 ID · 脚本引擎新增 SSH 支持 · HTTP 请求脚本支持动态切换代理策略 · 新增 DNS 跳过 TLS 验证选项,支持自签名证书的 DNS 服务器 · 策略组页面新增「显示隐藏项」开关 · 支持在单个 AnyTLS 会话上复用多条流 改进 · Surg

40👍6🔥1🥰1

27 Mar 2026, 06:02 UTC≈11,800 views23 reactionsread 7 August 2026
Video

给 Egern 首页新增快捷操作按钮,添加订阅、添加代理、扫码导入、下载配置

🥰183👍2

18 Mar 2026, 13:08 UTC≈15,000 views42 reactionsread 7 August 2026
Photo

Egern 的新模块:服务器监控 通过 SSH 实时监控服务器状态,支持所有 Widget 尺寸: - CPU / 内存 / 磁盘 / 网络 - 动态警告色:正常绿 → 警告黄 → 危险红 - 锁屏小组件也能看 使用方法: 1. 工具 → 模块 → 点击 + → 填入模块地址 2. 在模块的 Env 中填写 host、username、password(或 privateKey) 3. 分析 → 小组件画廊,即可预览 4. 长按主屏幕添加 Egern 小组件,选择「服务器监控」 模块地址: https://raw.githubusercontent.com/egerndaddy/quick-start/main/modules/server-monitor.yaml

👍2118👏1🔥1😁1

18 Mar 2026, 08:06 UTC≈12,600 views20 reactionsread 7 August 2026
Photo

Egern 脚本引擎新增 SSH 支持,几行代码搞定远程命令执行 + SFTP 文件操作,直接在主屏幕实时查看服务器状态

19👏1

17 Mar 2026, 11:51 UTC≈7,290 views16 reactionsread 7 August 2026

Egern 更新了 App Store 版本,以下是 2.17.0 的更新内容: 新功能 · 引入全新的 Script API · 新增自定义小组件支持。可以使用脚本 + Widget DSL 创建主屏幕和锁屏小组件 · 脚本编辑器中现在提供 Widget DSL 预览 · 新增 DNS 规则预匹配 · 新增 REJECT-NO-DROP 策略 · 命中 REJECT 策略的 DNS 查询现在可以返回空响应,以阻止域名解析 · 新增 URL Rewrite Header 模式支持 · 模块现在可以声明环境变量类型和选项,编辑器会自动生成对应的UI控件 · 从脚本列表直接运行脚本时,现在会传递脚本环境变量 改进 · 降低了某些事件的日志等级,以防止日志文件过度增长 Bug 修复 · 修复非 Pro 用户打开外观设置页面时可能卡住的问题 · 修复当某一跳被解析为 DIRECT 时,代理链可能失败的问题 · 修复超时或TC

16

13 Mar 2026, 13:35 UTC≈9,470 views32 reactionsread 7 August 2026
Video

在脚本编辑器中可以直接预览小组件的渲染效果了

👍15🥴3💯2🕊2🏆1👌1🖕1🤓1

12 Mar 2026, 05:30 UTC≈5,870 views51 reactionsread 7 August 2026
Photo

Egern 的小组件也支持锁屏界面

👍26🦄4🎉3😱32👀2💔2🤝2

12 Mar 2026, 04:01 UTC≈10,500 views62 reactionsread 7 August 2026

Egern 小组件提示词,直接喂给 ChatGPT 自动生成小组件。可以修改“帮我写一个天气小组件”这句话来生成不同的小组件。 帮我写一个天气小组件 严格按 Egern 文档实现,不要访问其他网站,下面两行是文档链接 https://egernapp.com/zh-CN/docs/configuration/widgets https://egernapp.com/zh-CN/docs/javascript-api

23🤔3🆒3👍2👾2💯2🤗2🤷2

11 Mar 2026, 09:55 UTC≈9,790 views81 reactionsread 7 August 2026
Photo

Egern 全新 JavaScript API https://egernapp.com/zh-CN/docs/javascript-api

👍37🙈5👀4🤮322🎅2💔2

11 Mar 2026, 05:12 UTC≈18,200 views93 reactionsread 7 August 2026
Photo

给 Egern 做了一个新功能可编程小组件

👍48😱5💩4🤡4🌭3🍾2🎉2🔥2

Showing the 12 most recent of 20 posts we hold for @egern_news. 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.

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

18 Jan 2026, 11:32 UTCAnonymous Poll361 voters

现在订阅节点必须用 external 单独配置,是否应该让普通策略组直接支持订阅链接与子策略放在同一个组里?

  1. 子策略 + 订阅链接放在一起57%
  2. 订阅链接继续用独立的 external 组43%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 20 most recent posts we hold, published 28 November 2025 to 24 July 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Citation-graph rank

Citation-graph rank — 542,241 of 1,480,975entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

Mentions

Named by 1 registered channel — 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.

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 16 August 2026 — this entry's latest reading, not the date you are reading this.

“Egern 频道” (@egern_news), 3,405 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/egern_news.

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.