Telegram RegisterThe public register of Telegram
Telegram profile photo for MapleSU

Channel

MapleSU

@KernelMapleSU

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

1,576subscribers

+385 since we began measuring on 11 November 2026

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

Register entry

Telegram ID-1004313047407
TypeChannel
Username@KernelMapleSU
CreatedBetween 1 June 2026 and 31 October 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 November 2026
Last confirmed live14 November 2026
Measurements held2
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/KernelMapleSU

Growth

1,1911,5761,383.511 November 2026 — 1,191 subscribers14 November 2026 — 1,576 subscribers11 November 202614 November 2026
2 measurements spanning 2 days, net +385. 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 1,133–1,634 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Nov 2026, 03:091,576+385
11 Nov 2026, 22:221,191first reading

Engagement

16 posts held, back to 31 October 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 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
148.0%
avg views ÷ 1,576 subscribers
Avg views / post
2,330
16 posts measured
Reaction rate
0.742%
reactions ÷ views · ER floor
Posts in window
16
of 16 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 10 November 2026
Posts held16 (31 October 2026 – 10 November 2026)
Views total37,320
Reactions total277
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 22:22 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

277 reactions across 16 posts, in 6 distinct kinds. The most used accounts for 88.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍24588.4%
❤279.75%
🗿20.722%
🍌10.361%
👎10.361%
🔥10.361%

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

Measured over the 16 most recent posts we hold, published 31 October 2026 to 10 November 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

Telegram’s own ‘edited’ marker: 8 of 16 posts held from the last 30 days (50.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

10 Nov 2026, 13:17 UTC712 views27 reactionsread 11 November 2026

内测BUG基本都修完了喵。等待内测用户最后反馈问题后致谢 会准时在周五周六在频道给大家带来公测的❤️

👍25❤2

10 Nov 2026, 05:19 UTC788 views11 reactionsread 11 November 2026
Sticker

Sticker, posted without a caption

👍8❤2🍌1

7 Nov 2026, 14:16 UTC≈1,370 views16 reactionsread 11 November 2026
Sticker

Sticker, posted without a caption

👍14❤2

7 Nov 2026, 14:16 UTC≈1,340 views19 reactionsread 11 November 2026

来了来了 依旧招收内鬼来内测

👍19

6 Nov 2026, 18:16 UTC≈1,680 views20 reactionsread 11 November 2026

谢谢 我们将表明相关参考 明确开源MapleSU源码并将SKRoot及其作者加入致谢名单 打扰各位了 谢谢SKP作者 我很敬佩 相关事务已归档至 废纸桶

👍18❤1🔥1

6 Nov 2026, 15:19 UTC≈1,620 views18 reactionsread 11 November 2026
Photo

⭐Lsposed与Zygisk均已在MapleSU_Ultra实现 🔗鸭子全过 敬请期待.

👍18

5 Nov 2026, 13:10 UTC≈1,630 views22 reactionsread 11 November 2026

​⭐ #MapleSU_Notice ​近期有大量关于 MapleSU 是否只是又一个 KSU 分支”的讨论与质疑,做一次公开的技术说明: MapleSU_Ultra 非 KSU 分支,它更相当于对 SKRoot Pro 公益优化重构并向所有用户公益公开,无需担心检测问题,并作为纯公益项目向所有人完全免费支持。 ​在继承“不主动泄露检测点、无挂载”的基础上,我们额外在此基础上支持了: 🔗 既要 SKRoot 的极致,又要 KSU 的生态:解决了 SKRoot 无法使用大多模块的致命伤,自实现兼容大多数 KSU 模块(支持 Zygisk / LSP)。 🔗​底层稳定性与寄生隐身:深度修复内核 Panic 问题,并针对性支持寄生/隐藏/网页管理器功能。 🔗​支持一键修补与迁移:无需电脑,无需手动,直接支持其他管理器迁移,在MapleSU内一键识别镜像,修补并刷入。 始终秉持公益初心,只为让各位用上更纯粹的 Root 方案。好的作…

👍18❤4

5 Nov 2026, 03:52 UTC≈7,440 views20 reactionsread 11 November 2026
Photo

📣 #MapleSU_Beta ⭐About test 在此特别感谢各位内测用户在内测期间的积极测试与反馈 结束测试后将并入致谢名单中 以上为部分内测用户反馈图 我们仍在持续优化 修复问题与提升无痕性中 MapleSU_Ultra Feature: ​全新底层架构:在内核层直接实现 SU 授权,灵活可控。 ​零痕迹无检测点:坚持 0 挂载、0 SELinux 策略篡改,从根源上拒绝所有侧信道检测,全程不留痕迹。 ​极简一键刷入:告别繁琐的修补流程,支持KSU等分支面具一键迁移刷入,开箱即用。 预计支持内核版本:5.10-6.18 设备支持:全机型越狱模式/解锁 与KSU不同的实现方式 不动Selinux策略 不挂载 从根本上解决检测 🔗我们预计于本周末至下周正式开启公测 敬请期待. ⭐​Code is coming. 解决一切侧信道检测点!避免修改Selinux引起的各种问题

👍15❤5

4 Nov 2026, 09:45 UTC≈1,720 views16 reactionsread 11 November 2026

开始审核 可能需要5系内核与6.18

👍16

3 Nov 2026, 16:52 UTC≈1,820 views11 reactionsread 11 November 2026

⭐MapleSU_Ultra/越狱招募第二轮内测 内测群组申请:MapleSU_Test 请确保你有足够的刷机/救砖能力 积极参与内测更新 我们将随时更新内测名单 惰性参与内测的将会被移除 此次内测预计支持内核版本:5.10-6.18 请附上机型 与内核版本 来意 我们将挑选通过 每个内核版本均有三份内测机会 名额有限 🔗请在评论区发送相关信息备注来意与设备或许将获得更高通过率 仅发送申请 但不在评论区发送相关信息的您可能将被忽略 Any question @MapleAdm

👍8❤3

1 Nov 2026, 15:39 UTC≈1,940 views6 reactionsread 11 November 2026
Sticker

Sticker, posted without a caption

👍5❤1

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

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

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

“MapleSU” (@KernelMapleSU), 1,576 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/KernelMapleSU.

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.