Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 98% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Also posting the same content
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
35 measurements spanning 50 days, net +2,295. 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 17,630–20,613 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 35
Measured (UTC)
Subscribers
Change
25 Sept 2026, 19:42
20,269
+470
19 Sept 2026, 03:01
19,799
+350
16 Sept 2026, 15:17
19,449
+327
14 Sept 2026, 21:18
19,122
+152
13 Sept 2026, 09:20
18,970
+39
11 Sept 2026, 12:57
18,931
+39
8 Sept 2026, 22:21
18,892
+77
5 Sept 2026, 12:36
18,815
+36
3 Sept 2026, 16:37
18,779
+26
2 Sept 2026, 08:24
18,753
+26
1 Sept 2026, 06:03
18,727
+43
31 Aug 2026, 02:27
18,684
+57
29 Aug 2026, 23:54
18,627
+37
28 Aug 2026, 21:34
18,590
+53
27 Aug 2026, 19:07
18,537
+93
26 Aug 2026, 19:17
18,444
+329
25 Aug 2026, 19:32
18,115
+9
24 Aug 2026, 19:13
18,106
+19
23 Aug 2026, 04:58
18,087
+13
21 Aug 2026, 15:55
18,074
first reading
Engagement
22 posts held, back to 16 November 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 55 pages of 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 22 posts for this entry, the most recent from 26 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
2,623 reactions across 22 posts, in 32 distinct kinds. The most used accounts for 47.1% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
1,236
47.1%
👍
363
13.8%
🔥
266
10.1%
😁
266
10.1%
🥰
126
4.80%
😇
113
4.31%
🤔
62
2.36%
🤡
45
1.72%
👎
39
1.49%
❤🔥
32
1.22%
🙏
15
0.572%
👏
12
0.457%
🤩
7
0.267%
👀
5
0.191%
💊
4
0.152%
🤯
4
0.152%
🆒
3
0.114%
🍾
3
0.114%
😍
3
0.114%
🤗
3
0.114%
12 further kinds
16
0.61%
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 22 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 2,623 reactions 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 16 November 2025 to 26 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.
Telegram Stars
Stars received
16
across the posts below
Posts paid on
8
of 22 we hold a reading for · 36%
Most on one post
3
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @nullptr_dev. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 22 most recent posts we hold for this entry, published 16 November 2025 to 26 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
ZygiskNext 1.4.3 正式版
增加模块崩溃检查,如果模块导致系统崩溃,会尝试找出导致问题的模块并显示在 WebUI 和模块描述中
增加导出 bugreport 功能,增加 action ,可通过 action 或 WebUI 导出并发送 bugreport
提升安全性
WebUI 支持 RTL 布局
更新 WebUI 翻译
ZygiskNext 1.4.3 Stable Release
Added module crash checking. If a module causes a system crash, it will attempt to find the problematic module and display it in the WebUI and module description.
Added bug report export functionality and action. Bug r…
ZygiskNext 1.4.1 正式版
解决 ZN Linker 与某些模块的兼容性问题(参见文档)
解决与光速虚拟机的兼容性问题
WebUI 补充翻译
如果 zygisk 模块无法加载, WebUI 和模块状态会显示错误
ZygiskNext 1.4.1 Stable Release
Resolved compatibility issues between ZN Linker and certain modules (see documentation)
Resolved compatibility issues with VPhoneOS
Supplemented translation of WebUI
If zygisk modules fails to load, the WebUI and module status will display errors.
SHA256: 9bdc393f119c4b3bd…
ZygiskNext 1.3.4 正式版
修复使用某些模块导致崩溃的问题
WebUI 增加 ZN 模块列表
增加 Zygisk 模块错误检查机制,发现存在问题的模块会显示在 ZN 的模块状态和 WebUI 中(可检查的错误请参见文档)
补充 1.3.3 的更新:ZN 模块的 inline hook 功能无需额外在 sepolicy 增加 execmem 规则
ZygiskNext 1.3.4 Stable Release
Fixed an issue that caused crashes when using certain modules.
Add ZN module list to the WebUI.
Add Zygisk module error checking mechanism. Modules with issues will be displayed in ZN's module status and W…
ZygiskNext 1.3.3 正式版
默认启用 ZN linker
适配 Android Canary 2603 的相关改动
提升对 nubia 系统、三星系统的兼容性
修复某些情况下与 magisk 的兼容性问题
修复其他小问题
ZygiskNext 1.3.3 Stable Release
Enable ZN linker by default
Adapt to changes in Android Canary 2603
Improve compatibility with certain nubia and Samsung systems
Fix compatibility issues with Magisk in some cases
Fix other minor issues
SHA256: a528584874dd814423dece1a6bc734aee524886d74f4453f48af0715a…
❤110👍18🥰12🤡4💊2🍌1👏1🤪1
Showing the 12 most recent of 22 posts we hold for @nullptr_dev. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
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.
Channels Telegram recommends alongside this one
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 28 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
5ec1cff @real5ec1cff · 37,318 Telegram ranks this channel #1 of 51 here — alongside 50 others — read 2 September 2026
LSPosed @LSPosed · 194,124 Telegram ranks this channel #2 of 57 here — alongside 56 others — read 17 August 2026
SCENE Downloads @scene2023 · 54,890 Telegram ranks this channel #3 of 50 here — alongside 49 others — read 12 September 2026
Magisk alpha @magiskalpha · 65,706 Telegram ranks this channel #3 of 40 here — alongside 39 others — read 21 August 2026
Hide My Applist @HideMyApplist · 40,938 Telegram ranks this channel #4 of 24 here — alongside 23 others — read 30 August 2026
HyperCeiler | Release & Notice @cemiuiler_release · 26,729 Telegram ranks this channel #6 of 51 here — alongside 50 others — read 12 September 2026
FunProject @QToolCI · 49,485 Telegram ranks this channel #9 of 51 here — alongside 50 others — read 12 September 2026
QAuxiliary @QAuxiliary · 44,820 Telegram ranks this channel #11 of 58 here — alongside 57 others — read 12 September 2026
不靠谱的喵(>^ω^<) #CatGPT @MlgmXyysd_bibilailai · 21,690 Telegram ranks this channel #13 of 54 here — alongside 53 others — read 23 September 2026
LuckyTool @LuckyTool · 28,572 Telegram ranks this channel #16 of 56 here — alongside 55 others — read 12 September 2026
Matsuridayo GitHub @MatsuriDayo · 45,413 Telegram ranks this channel #16 of 58 here — alongside 57 others — read 30 August 2026
LSPosedArchives @LSPosedArchives · 25,244 Telegram ranks this channel #18 of 36 here — alongside 35 others — read 14 September 2026
APatch Updates @APatchChannel · 25,201 Telegram ranks this channel #23 of 37 here — alongside 36 others — read 14 September 2026
Nagram Tips @NagramTips · 46,239 Telegram ranks this channel #25 of 49 here — alongside 48 others — read 30 August 2026
KernelSU @KernelSU · 61,920 Telegram ranks this channel #35 of 49 here — alongside 48 others — read 14 September 2026
Seal @seal_app · 25,021 Telegram ranks this channel #38 of 45 here — alongside 44 others — read 15 September 2026
This channel appears in 16 seed channels' Telegram-generated recommendation lists 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 25 September 2026 — this
entry's latest reading, not the date you are reading this.
“Real Nullptr” (@nullptr_dev), 20,269 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/nullptr_dev.
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.