Channel
@rnagicat
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
204subscribers
+3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003267963864 |
|---|---|
| Type | Channel |
| Username | @rnagicat |
| Created | Between 1 October 2025 and 31 January 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/rnagicat |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 03:27 | 204 | +3 |
| 7 Aug 2026, 04:02 | 201 | no change |
| 7 Aug 2026, 03:45 | 201 | first reading |
18 posts held, back to 5 April 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 pageof 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 18 posts for this entry, the most recent from 5 June 2026. An engagement rate over an empty window would be a number about nothing.
76 reactions across 16 posts, in 10 distinct kinds. The most used accounts for 69.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 53 | 69.7% | |
| 🔥 | 5 | 6.58% | |
| 👎 | 4 | 5.26% | |
| 👏 | 4 | 5.26% | |
| 🫡 | 3 | 3.95% | |
| 👾 | 2 | 2.63% | |
| 🤔 | 2 | 2.63% | |
| ❤🔥 | 1 | 1.32% | |
| 🏆 | 1 | 1.32% | |
| 👍 | 1 | 1.32% |
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 18 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 76reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 5 April 2026 to 5 June 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.
#blossom #sashimi #kernel #RVendor Sashimi Kernel V4.1 Release date: 2026/06/05 Maintainer: @zyexro Device: Blossom Changelogs: • GitHub Commit History Links: • Kernel: [NON-KSU] | [KSU] | [KSU-SUS] • [KernelSU Manager] • [SUSFS-FOR-KERNELSU] • Source Bugs: • Slow charging reported on some units • Report bugs below Credits: • @fukiame — base tree • backslashxx — KernelSU • simonpunk & JackA1ltman – SuSFS Notes:…
❤12🤔2
build succeeded in 7m, 1s md5: 4eefb7efc59a1536ea39e8debc8bb8ba compiler: ClangBuiltLinux clang version 22.1.7, ClangBuiltLinux LLD 22.1.7
❤3👎1
Chinese novel its peak
👍1
"لان شدائد تقوي العزم فلن يتم اغواء الاقوياء بشهوات الدنياوية، اليوم اخطو علي عشب و غدا اخطو علي جبال و الانهار." فانغ يوان - عودة القس المجنون
❤2👎1
Video, posted without a caption
❤6
File, posted without a caption
Exams season is here, so I'll be inactive for a while, wish me luck!"
❤5🫡1
Regarding decryption issues on Sashimi v4 (blossom): If you are experiencing decryption issues, it is due to the recent encryption rework, to resolve this, you can use the latest unofficial OrangeFox build by @VertekPlus, as it handles the decryption correctly with v4. Note: Not my build, not my support
🫡2❤1
#blossom #sashimi #kernel #RVendor Sashimi Kernel V4 Release date: 2026/05/12 Maintainer: @zyexro Device: Blossom BREAKING CHANGE: Userdata format required Changelogs: • Merge upstream f2fs-stable • Rework fscrypt encryption stack (PRIVATE mode cleanup) • Backport BBR3 congestion control • Switch TCP scheduler to SCH_CAKE • Enable FUSE_BPF, drop sdcardfs • Remove some debugging Bugs: • Slow charging reported on s…
❤5❤🔥1
build succeeded in 0m, 49s md5: 702a3de011ee21c05c5ecec59ee3d7f4 compiler: Android (14488419, +pgo, +bolt, +lto, +mlgo, based on r584948) clang version 22.0.0, LLD 22.0.0 (/mnt/disks/build-disk/src/googleplex-android/llvm-r584948-release/out/llvm-project/llvm 2d65e4108033380e6fe8e08b1f1826cd2bfb0c99)
❤4
build succeeded in 9m, 5s md5: 567dab27e751834ab1156d13b6be12da compiler: Android (14488419, +pgo, +bolt, +lto, +mlgo, based on r584948) clang version 22.0.0, LLD 22.0.0 (/mnt/disks/build-disk/src/googleplex-android/llvm-r584948-release/out/llvm-project/llvm 2d65e4108033380e6fe8e08b1f1826cd2bfb0c99)
❤4
Sashimi Kernel V3 Release date: 2026/04/26 Maintainer: @zyexro Device:Blossom Changelog: • merged cip-131 • enabled memfd ashmem shim; disabled fuse_bpf, trace, and debug features; cleanup • enabled CC inline optimization with enhanced math • reduced lz4 memory usage to 1KB • imported multiple upstream scheduler 5.4 • update sbalance • backported bbr2; bbr2 + fq as default Notes: • MIUI ROMs are not supported • Wor…
❤6🏆1
Showing the 12 most recent of 18 posts we hold for @rnagicat. 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 — 945,918 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.
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.
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.
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.
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.
“Yethreb” (@rnagicat), 204 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/rnagicat.
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.