Telegram RegisterThe public register of Telegram

Channel

Loon News

@LoonNews

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

45,175subscribers

+114 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001475508058
TypeChannel
Username@LoonNews
DescriptionLoon News
CreatedBetween 1 April 2019 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/LoonNews

Growth

45,06145,17545,1186 August 2026 — 45,061 subscribers6 August 2026 — 45,061 subscribers7 August 2026 — 45,089 subscribers8 August 2026 — 45,111 subscribers9 August 2026 — 45,147 subscribers10 August 2026 — 45,167 subscribers11 August 2026 — 45,171 subscribers12 August 2026 — 45,175 subscribers6 August 202612 August 2026
8 measurements spanning 6 days, net +114. 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 45,044–45,192 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 08:1645,175+4
11 Aug 2026, 06:2445,171+4
10 Aug 2026, 08:1645,167+20
9 Aug 2026, 05:0845,147+36
8 Aug 2026, 06:0345,111+22
7 Aug 2026, 09:3145,089+28
6 Aug 2026, 04:1545,061no change
6 Aug 2026, 04:0845,061first reading

Engagement

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

ERR · 30 days
13.6%
avg views ÷ 45,175 subscribers
Avg views / post
6,140
22 posts measured
Reaction rate
0.234%
reactions ÷ views · ER floor
Posts in window
22
of 22 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 20 of 22 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 12 August 2026
Posts held22 (17 July 202612 August 2026)
Views total135,124
Reactions total296
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 20:04 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
1,080
Videos
25
Links
406

Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Reaction mix

190 reactions across 14 posts, in 11 distinct kinds. The most used accounts for 76.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
14676.8%
👍189.47%
🤔73.68%
🌚52.63%
🙊42.11%
🫡42.11%
👌21.05%
🆒10.526%
🤨10.526%
🤩10.526%
🤷10.526%

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 22 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 296reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 22 most recent posts we hold, published 17 July 2026 to 12 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.

Recent posts

12 Aug 2026, 16:32 UTC454 views1 reactionsread 12 August 2026
Forwarded from @ibilibiliPhoto

🎉 中国天气去广告 ⭐️ 移除开屏广告、弹窗广告、横幅广告,移除焦点视频、精简我的页面。 ❓ 此插件存在依赖,使用前请确保依赖为最新版。 🔗 可莉的插件中心 ❗️ 禁止中国境内传播 ❗️ 禁止二次分发 ❗️ 此插件不开源 ✈️ 发布频道 @ibilibili #Plugin

1

10 Aug 2026, 16:39 UTC≈4,530 views4 reactionsread 12 August 2026
Photo

#TestFlight #iOS Loon 3.5.1(982)版本已准备好在iOS 上进行测试。 - 重构正则匹配方式,大幅优化正则匹配时的内存占用,不用担心过多的 rewrite 和脚本了 - 修复 rewrite 旧语法部分兼容性问题 - 修复因转发 http headers 顺序异常导致的请求失败 - reality 增加一种 Chrome 指纹,用于兼容singbox 等一些服务器的 chorme 指纹,默认 chrome 会选择这个 - reality 的版本字段更新到最新 - hostmap 支持连续匹配,比如 A-B,B-C,会让 A 映射到 C - 修复 anytls 代理链的一个多线程 bug - 修复一些偶现的 crash 👥 频道:@LoonNews 💬 群组:@Loon0x00

4

Signed Tartarus

10 Aug 2026, 16:21 UTC≈3,070 viewsread 12 August 2026
Forwarded from @ibilibiliPhoto

🎉 慧生活798去广告 ⭐️ 移除开屏广告、横幅广告,精简底栏。 ❓ 此插件存在依赖,使用前请确保依赖为最新版。 🔗 可莉的插件中心 ❗️ 禁止中国境内传播 ❗️ 禁止二次分发 ❗️ 此插件不开源 ✈️ 发布频道 @ibilibili #Plugin

8 Aug 2026, 16:11 UTC≈3,450 views4 reactionsread 12 August 2026
Forwarded from @ibilibiliPhoto

🎉 天天跳绳去广告 ⭐️ 移除开屏广告、横幅广告、弹窗广告、活动推广,精简首页标签和搜索页面。 ❓ 此插件存在依赖,使用前请确保依赖为最新版。 🔗 可莉的插件中心 ❗️ 禁止中国境内传播 ❗️ 禁止二次分发 ❗️ 此插件不开源 ✈️ 发布频道 @ibilibili #Plugin

3🤨1

6 Aug 2026, 22:08 UTC≈4,460 views11 reactionsread 12 August 2026
Forwarded from @ibilibiliPhoto

🎉 大姨妈月经期助手去广告 ⭐️ 移除信息流广告,精简首页金刚位及我的页面。 ❓ 此插件存在依赖,使用前请确保依赖为最新版。 🔗 可莉的插件中心 ❗️ 禁止中国境内传播 ❗️ 禁止二次分发 ❗️ 此插件不开源 ✈️ 发布频道 @ibilibili #Plugin

🤔73🤷1

6 Aug 2026, 13:49 UTC≈6,880 views62 reactionsread 12 August 2026
Photo

最近在重做 Loon for Mac 的 UI,新的 UI 草稿,还在设计阶段,大家踊跃提意见

53🌚5🙊4

4 Aug 2026, 20:10 UTC≈5,170 views2 reactionsread 12 August 2026
Forwarded from @ibilibiliPhoto

🎉 WakeUp课程表去广告 ⭐️ 移除横幅广告、弹窗广告,精简我的页面。 ❓ 此插件存在依赖,使用前请确保依赖为最新版。 🔗 可莉的插件中心 ❗️ 禁止中国境内传播 ❗️ 禁止二次分发 ❗️ 此插件不开源 ✈️ 发布频道 @ibilibili #Plugin

2

4 Aug 2026, 08:56 UTC≈6,170 views18 reactionsread 12 August 2026
Forwarded from @mayiheiPhoto

🪶 IPQuality Quick · 全新测试版 提供原生单项快速检测与 Safari 多项检测,可按需查询节点出口信息、风险属性、流媒体解锁及网络质量。 ━━━━━━━━━━ 主要功能 · 原生快速查看基础信息 · 原生检测 IP 风险与网络属性 · 检测流媒体及 AI 服务可用性 · 在 Safari 中按需组合 15 个检测项目 · 支持隐藏 IP、Apple 地图、HTTPS 轻量测速和三网探针 ━━━━━━━━━━ 安装与说明 🪶 长按复制插件链接 需要 Loon 3.5.1(980) 或更高版本。 安装后,在节点或策略组页面可以看到三个“IP 快速检测”入口和一个“IP 自选检测 · 网页”入口。 本插件与原版 IPQuality 相互独立,可以同时安装。 ━━━━━━━━━━ 💬 交流群 · 🪶 插件索引 · 📢 频道 #Loon #IPQuality #节点检测

18

Signed Tartarus

3 Aug 2026, 16:55 UTC≈6,550 views21 reactionsread 12 August 2026
Photo

#TestFlight #iOS #website Loon 3.5.1(980)版本已准备好在iOS 上进行测试。 - 优化 rewrite 语法,多个 action 支持数组参数,如:response if ${url} ~= /api/ then response.json.add(["data.a", "data.b"], [1, true]),更多请参考文档:https://nsloon.app/docs/Rewrite/rewrite_v2#%E6%89%B9%E9%87%8F%E6%95%B0%E7%BB%84%E5%8F%82%E6%95%B0 - 修复大量action操作JSON时的内存溢出bug - 插件列表页面支持图标模式 👥 频道:@LoonNews 💬 群组:@Loon0x00

20🤩1

Signed Tartarus

2 Aug 2026, 16:11 UTC≈4,610 views12 reactionsread 12 August 2026
Forwarded from @ibilibiliPhoto

🎉 Telegram重定向 ⭐️ 适用于安装了多个不同Telegram客户端的用户,用于指定客户端打开Telegram短链。 ❓ 这是Loon的专用插件,使用新的语法编写,仅支持最新的测试版。 🔗 可莉的插件中心 ❗️ 禁止中国境内传播 ❗️ 禁止二次分发 ❗️ 此插件不开源 ✈️ 发布频道 @ibilibili #Plugin

12

2 Aug 2026, 15:17 UTC≈8,440 views24 reactionsread 12 August 2026
Photo

#TestFlight #iOS #website Loon 3.5.1(979)版本已准备好在iOS 上进行测试。 - Rewrite 现已支持更灵活的条件组合、变量引用和多 Action 执行,可同时处理URL、Header、Body、JSON、Mock 等内容,也可以同时匹配执行多个 Rewrite。详细语法请查看 Rewrite 使用文档( https://nsloon.app/docs/Rewrite/rewrite_v2 ) - 新的匹配机制通过优化匹配算法减少无效匹配,提升大量 Rewrite 配置下的匹配速度,并降低运行时内存占用。同时兼容旧版配置,新增可视化编辑、配置校验和语法预览,并统一了 HTTP、HTTPS 与 HTTP/2 下的 Rewrite 执行行为。 - 新语法重构了整个 rewire 模块,改动较大,如遇到问题请及时反馈。 Website - 官网( https://nsloo

21👌2🆒1

31 Jul 2026, 20:36 UTC≈4,750 views1 reactionsread 12 August 2026
Forwarded from @ibilibiliPhoto

🎉 挖财记账去广告 ⭐️ 移除开屏广告、横幅广告,顶部推广、活动配置。 ❓ 此插件存在依赖,使用前请确保依赖为最新版。 🔗 可莉的插件中心 ❗️ 禁止中国境内传播 ❗️ 禁止二次分发 ❗️ 此插件不开源 ✈️ 发布频道 @ibilibili #Plugin

1

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

Citation-graph rank

Citation-graph rank — 194,477 of 1,151,006entries 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

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.

Mentions

Named by 11 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.

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

科技圈🎗在花频道📮
@zaihuapd · 274,310
Telegram ranks this channel #36 of 40 here — alongside 39 others — read 12 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Loon News” (@LoonNews), 45,175 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/LoonNews.

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.