Channel
@ks_merlin
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
13,015subscribers
+14 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001348878846 |
|---|---|
| Type | Channel |
| Username | @ks_merlin |
| Description | 信息发布 |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/ks_merlin |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 19:46 | 13,015 | -4 |
| 13 Aug 2026, 09:24 | 13,019 | +3 |
| 12 Aug 2026, 11:14 | 13,016 | +4 |
| 11 Aug 2026, 14:21 | 13,012 | +2 |
| 10 Aug 2026, 11:21 | 13,010 | +3 |
| 9 Aug 2026, 14:16 | 13,007 | +2 |
| 8 Aug 2026, 15:10 | 13,005 | +5 |
| 7 Aug 2026, 12:52 | 13,000 | -1 |
| 6 Aug 2026, 13:16 | 13,001 | first reading |
19 posts held, back to 27 January 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 18 pagesof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 19 posts for this entry, the most recent from 11 July 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 15 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.
259 reactions across 19 posts, in 4 distinct kinds. The most used accounts for 47.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 123 | 47.5% | |
| 👍 | 100 | 38.6% | |
| 👏 | 27 | 10.4% | |
| 🤔 | 9 | 3.47% |
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 19 of the 19 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 259reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 27 January 2026 to 11 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.
🎉【20260711】R大梅林改版固件102.8_0发布，包括12款机型 支持机型： RT-BE58_GO RT-AX86U_PRO RT-AX88U_PRO RT-BE86U RT-BE88U RT-BE92U RT-BE96U GT-AX11000_PRO GT-AX6000 GT-AXE16000 GT-BE98_PRO XT12 简要更新日志： 1. 同步上游R大梅林固件102.8_0代码 2. 梅林更新要点：Wifi 6机型GPL: 102_37538, RT-BE58_Go GPL: 102_37538, 其余Wifi 7机型GPL: 102_39995 3. 同步软件中心最新版本 ———————————— 此次固件需要发电获取，获取地址： https://ifdian.net/item/9b16f1ce7d3111f18e9e5254001e7c00 大家关注的MC运行问题…
👍14❤10
扒了下华硕wifi6和wifi7路由器的固件和源代码，感想就是华硕这机海战术…
❤12
📢【618 福利专区】 🎉 618 团购福利来了！ 🔹 BeeconMini SEED AC5 + WiFi 7 自组网 AP 团购福利： https://mp.weixin.qq.com/s/tMrcMzPL44lWe50W2k7_Uw 🔹 华硕 WiFi 7 路由器 618 团购活动： https://mp.weixin.qq.com/s/_b7Q9gp_xrcNd8nL5VILTg ━━━━━━━━━━━━━━ 🚀 此外，EasePi-R2 少量现货已上架 目前库存有限，有需要的朋友可通过复制下方淘宝链接购买： 【淘宝】https://e.tb.cn/h.RSH8D3qWLEscmb0?tk=J5LhgZ4Uitc tG-#22>lD 「EasePi-R2 RK3588高性能多网口计算主机AI开发多用途路由NAS」 点击链接直接打开 或者 淘宝搜索直接打开
❤2
🎉【20260528】华硕RT-BE58_GO官改固件102_39127发布 ———————————————————————————————— 支持机型： RT-BE58_GO 更新日志： 1. 同步华硕上游GPL源代码：GPL 102.39127； 2. 移除curl/wget在jffs分区下载记录的功能 3. 内置软件中心更新到1.9.56 4. 极大提升httpd稳定性，现在httpd几乎不会崩溃了 5. 恢复华硕针对国区隐藏的ASUSDDNS功能（ascomm.com） 6. 固件默认添加jq，这个很多插件会用到 7. iptables添加 libip6t_REDIRECT模块支持（fancyss ipv6代理会用到） ———————————————————————————————— 此次固件需要发电获取。 🧧 赞助获取固件 | ⬇️ 固件论坛贴 | 🚀科学插件 | ✈️ 机场推荐
❤6
🎉【20260526】华硕RT-BE86U官改固件102_39125_R1 ———————————————————————————————— 支持机型： RT-BE86U 更新日志： 1. 由于RT-BE86U ASUS上游源码未更新，此次由开发组修复了路由器自身网络访问网站等出现ssl错误的问题（解决某猫访问直连网站ssl错误） ，强烈建议更新！ 2. 注意：刷机此版本后，固件顶部的版本号不会发生变化，用软件中心ROG工具箱查看信息会显示固件编译日期： 2026-05-26 22:23:10，则表示此固件为：3006_102_39125_R1版本 ———————————————————————————————— 注：此次固件需要发电获取 📝固件论坛贴 |🧧 赞助获取固件 | 🚀科学插件 | ✈️ 机场推荐
👍6❤2
🎉【20260526】华硕RT-BE88U官改固件102_39256 ———————————————————————————————— 支持机型： RT-BE88U 更新日志： 此版本固件华硕方面的更新修复了一个重要的问题：路由器自身网络访问网站等出现ssl错误的问题，强烈建议更新 1. 同步华硕上游GPL源代码：GPL 102.39256； 2. 同步内容内置软件中心版本到1.9.56 ———————————————————————————————— 注：此次固件需要发电获取 📝固件论坛贴 |🧧 赞助获取固件 | 🚀科学插件 | ✈️ 机场推荐
❤8
🎉【20260526】华硕GT-BE96（ROG八爪鱼7） 官改固件102_39099发布 ———————————————————————————————— 支持机型： GT-BE96 更新日志： 1. 由于GT-BE96 ASUS上游源码未更新，此次由开发组修复了路由器自身网络访问网站等出现ssl错误的问题（解决某猫访问直连网站ssl错误） ，强烈建议更新！ 2. 注意：刷机此版本后，固件顶部的版本号不会发生变化，用软件中心ROG工具箱查看信息会显示固件编译日期： 2026-05-23 11:06:29，则表示此固件为：3006_102_39099_R1版本 ———————————————————————————————— 注：此次固件需要发电获取 📝固件论坛贴 |🧧 赞助获取固件 | 🚀科学插件 | ✈️ 机场推荐
❤5👍2
我擦，这520 ASUS搞爱的放送么？竟然放出了RT-BE88U 102_39256的源代码！
👏23🤔7❤3
🎉【20260509】华硕GT-BE96（ROG八爪鱼7） 官改固件102_39099发布 ———————————————————————————————— 支持机型： GT-BE96 更新日志： 1. 同步华硕上游GPL源代码：GPL 102.39099； 移除华硕curl/wget在jffs分区记录下载记录的功能 2. 内置软件中心更新到1.9.55 3. 极大提升httpd稳定性，现在httpd几乎不会崩溃了 4. 恢复华硕针对国区隐藏的ASUSDDNS功能（ascomm.com） 5. 固件默认添加jq，这个很多插件会用到 iptables添加 libip6t_REDIRECT模块支持 ———————————————————————————————— 此次固件不需要发电，直接论坛回复可直接下载 此版本五星强烈建议更新，因为解决了一个从有软件中心以来就潜在的问题：httpd崩溃。虽然之前的固件版本中…
❤10
🎉【20260509】华硕RT-BE86U 官改固件102_39125发布 ———————————————————————————————— 支持机型： RT-BE86U 更新日志： 1. 同步华硕上游GPL源代码：GPL 102.39125； 移除华硕curl/wget在jffs分区记录下载记录的功能 2. 内置软件中心更新到1.9.55 3. 极大提升httpd稳定性，现在httpd几乎不会崩溃了 4. 恢复华硕针对国区隐藏的ASUSDDNS功能（ascomm.com） 5. 固件默认添加jq，这个很多插件会用到 iptables添加 libip6t_REDIRECT模块支持 ———————————————————————————————— 此次固件不需要发电，直接论坛回复可直接下载 此版本五星强烈建议更新，因为解决了一个从有软件中心以来就潜在的问题：httpd崩溃。虽然之前的固件版本中也有改善htt…
❤2
🎉【20260507】华硕RT-BE88U 官改固件102_39112发布 ———————————————————————————————— 支持机型： RT-BE88U 更新日志： 1. 同步华硕上游GPL源代码：GPL 102.39112； 移除华硕curl/wget在jffs分区记录下载记录的功能 2. 内置软件中心更新到1.9.55 3. 极大提升httpd稳定性，现在httpd几乎不会崩溃了 4. 恢复华硕针对国区隐藏的ASUSDDNS功能（ascomm.com） 5. 固件默认添加jq，这个很多插件会用到 iptables添加 libip6t_REDIRECT模块支持 ———————————————————————————————— 此次固件不需要发电，直接论坛回复可直接下载 此版本五星强烈建议更新，因为解决了一个从有软件中心以来就潜在的问题：httpd崩溃。虽然之前的固件版本中也有改善htt…
❤13👏4
🎉【20260506】R大梅林改版固件102.7_2发布，包括12款机型 支持机型： RT-BE58_GO RT-AX86U_PRO RT-AX88U_PRO RT-BE86U RT-BE88U RT-BE92U RT-BE96U GT-AX11000_PRO GT-AX6000 GT-AXE16000 GT-BE98_PRO XT12 简要更新日志： 1. 同步上游R大梅林固件102.7_2代码 2. 梅林更新要点1：curl更新到8.17；wget更新到1.25 3. 梅林更新要点2：RT-BE92U合并了华硕GPL 102_39848 4. 同步软件中心最新版本 ———————————— 此次固件不需要发电，直接论坛回复可直接下载 大家关注的MC运行问题，梅林改102.7_2仍然没有解决，预计102.9会解决?，目前要么大家降级固件用MC，要么可以新固件用fancyss（现在也支持…
👍11❤7
Showing the 12 most recent of 19 posts we hold for @ks_merlin. 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 — 695,398 of 1,350,102entries 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.
Named by 2 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.
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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“KoolCenter Merlin Firmware” (@ks_merlin), 13,015 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/ks_merlin.
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.