Telegram RegisterThe public register of Telegram
Telegram profile photo for re:呪い's Channel

Channel

re:呪い's Channel

@renoroi

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

624subscribers

+4 since we began measuring on 4 October 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002482806320
TypeChannel
Username@renoroi
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded4 October 2026
Last confirmed live21 October 2026
Measurements held5
Confirmed unchanged1 time, most recently 21 October 2026
On Telegramt.me/renoroi

Topic

Software piracy — a classification, not a measurement. An on-box language model (qwen3.6:35b-a3b, prompt version 1) read this channel’s own recent posts on 21 October 2026 and assigned it the closest of 31 fixed categories, at 76% 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.

Growth

6206246224 October 2026 — 620 subscribers4 October 2026 — 620 subscribers8 October 2026 — 622 subscribers14 October 2026 — 621 subscribers21 October 2026 — 624 subscribers4 October 202621 October 2026
5 measurements spanning 17 days, net +4. 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 619–625 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
21 Oct 2026, 00:19624+3
14 Oct 2026, 19:57621-1
8 Oct 2026, 10:54622+2
4 Oct 2026, 07:22620no change
4 Oct 2026, 06:47620first reading

Engagement

11 posts held, back to 12 May 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 1 page 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 11 posts for this entry, the most recent from 23 July 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

128 reactions across 9 posts, in 15 distinct kinds. The most used accounts for 19.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤2519.5%
👍1914.8%
🤯1814.1%
🤣1713.3%
🔥1410.9%
😢118.59%
❤‍🔥86.25%
💋75.47%
👀21.56%
🥴21.56%
👎10.781%
👏10.781%
🗿10.781%
😁10.781%
🤝10.781%

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

Measured over the 11 most recent posts we hold, published 12 May 2025 to 23 July 2025, 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

23 Jul 2025, 07:57 UTC≈4,300 views31 reactionsread 4 October 2026
File

File, posted without a caption

🤯18❤7🔥4👀2

15 Jul 2025, 17:23 UTC≈4,010 views7 reactionsread 4 October 2026

Public leaked keybox updated, dunno how long it'll work. Use it however you like, this is different than the keybox i'm currently using

😢7

15 Jul 2025, 06:45 UTC≈4,120 views0 reactionsread 4 October 2026
File

ReZygisk v1.0.0-rc.3 📅 14.07.2025 👨‍🔧 PerformanC 💬 Description: ReZygisk is a fork of Zygisk Next, a standalone implementation of Zygisk, providing Zygisk API support for KernelSU, APatch and Magisk (Official and Kitsune). It aims to modernize and re-write the codebase to C entirely, allowing a more efficient and faster implementation of the Zygisk API with a more permissive, and FOSS friendly, license. 📝 Notes: …

15 Jul 2025, 06:45 UTC≈3,330 viewsread 4 October 2026
File

NeoZygisk v1.1 📅 12.06.2025 👨‍🔧 JingMatrix 💬 Description: NeoZygisk is a Zygote injection module implemented using ptrace, which provides Zygisk API support for APatch/KernelSU and serves as a replacement of Magisk's built-in Zygisk. Github | History #Module #Zygisk #Root #FOSS

15 Jul 2025, 06:44 UTC≈2,810 views1 reactionsread 4 October 2026
File

LSPosed v1.10.2 📅 12.07.2025 👨‍🔧 JingMatrix 💬 Description: A Zygisk module trying to provide an ART hooking framework which delivers consistent APIs with the OG Xposed, leveraging LSPlant hooking framework. 🆑 Full Changelogs 📝 Notes: • Use with with ReZygisk, NeoZygisk or Zygisk Next (Fully Supported for A16) Github | History #Module #Zygisk #LSPosed #Root #FOSS

❤1

25 Jun 2025, 05:11 UTC≈3,260 views8 reactionsread 4 October 2026

Keybox updated, update only when you need it

💋7❤1

19 Jun 2025, 05:20 UTC≈3,530 views30 reactionsread 4 October 2026
Photo

Taken from @popMODS

🤣17❤‍🔥8❤2👍1👏1😁1

11 Jun 2025, 06:02 UTC≈3,380 views10 reactionsread 4 October 2026

the keybox already used by integrity box, well might as well use it until it's dead. Updated

🔥10

5 Jun 2025, 04:55 UTC≈5,470 views24 reactionsread 4 October 2026
Photo

Warning!! Don't ever use Integrity Box with susfs kernel, as someone building kernel with susfs I need to inform all my users. This module that should be providing keyboxes to users that can't replace their own keybox just adding a bunch of sus_path without the users permission. As you already know, susfs isn't a clean way to hide root with how they umount things (it just works). Adding hundreds of sus_path is just …

❤14😢4👍3🥴2🗿1

28 May 2025, 14:56 UTC≈3,090 views16 reactionsread 4 October 2026

keybox updated, do not check integrity every seconds. Be a reasonable person

👍15👎1

12 May 2025, 02:00 UTC≈4,000 views1 reactionsread 4 October 2026

Keybox updated, thanks to Prateek Gurjar (i won't share his uname so no one will pm him) this time for sharing

🤝1

Showing the 11 most recent of 11 posts we hold for @renoroi. 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.

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

“re:呪い's Channel” (@renoroi), 624 subscribers as measured 21 October 2026. Telegram Register, tgregister.com/channel/renoroi.

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.