Telegram RegisterThe public register of Telegram
Telegram profile photo for ReZygisk CIs

Channel

ReZygisk CIs

@rezygisk_ci

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

9,145subscribers

+926 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002786581440
TypeChannel
Username@rezygisk_ci
DescriptionOfficial ReZygisk CI Channel. Official PerformanC Chat: @performancorg
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live15 November 2026
Measurements held28
Confirmed unchanged2 times, most recently 15 November 2026
On Telegramt.me/rezygisk_ci

Topic

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 11 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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 the other topics.

Growth

8,2199,1458,6826 August 2026 — 8,219 subscribers6 August 2026 — 8,219 subscribers6 August 2026 — 8,233 subscribers9 August 2026 — 8,258 subscribers12 August 2026 — 8,291 subscribers16 August 2026 — 8,310 subscribers19 August 2026 — 8,325 subscribers22 August 2026 — 8,331 subscribers25 August 2026 — 8,341 subscribers28 August 2026 — 8,388 subscribers31 August 2026 — 8,463 subscribers3 September 2026 — 8,506 subscribers8 September 2026 — 8,554 subscribers12 September 2026 — 8,576 subscribers16 September 2026 — 8,623 subscribers25 September 2026 — 8,748 subscribers4 October 2026 — 8,867 subscribers10 October 2026 — 8,932 subscribers14 October 2026 — 8,975 subscribers17 October 2026 — 8,988 subscribers19 October 2026 — 8,999 subscribers22 October 2026 — 9,014 subscribers25 October 2026 — 9,029 subscribers28 October 2026 — 9,036 subscribers31 October 2026 — 9,054 subscribers3 November 2026 — 9,077 subscribers6 November 2026 — 9,097 subscribers10 November 2026 — 9,145 subscribers6 August 202610 November 2026
28 measurements spanning 96 days, net +926. 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 8,080–9,284 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 28
Measured (UTC)SubscribersChange
10 Nov 2026, 08:579,145+48
6 Nov 2026, 12:599,097+20
3 Nov 2026, 17:599,077+23
31 Oct 2026, 07:549,054+18
28 Oct 2026, 12:119,036+7
25 Oct 2026, 13:279,029+15
22 Oct 2026, 21:399,014+15
19 Oct 2026, 18:108,999+11
17 Oct 2026, 01:368,988+13
14 Oct 2026, 07:448,975+43
10 Oct 2026, 16:398,932+65
4 Oct 2026, 19:158,867+119
25 Sept 2026, 00:428,748+125
16 Sept 2026, 23:008,623+47
12 Sept 2026, 20:028,576+22
8 Sept 2026, 20:018,554+48
3 Sept 2026, 10:438,506+43
31 Aug 2026, 04:478,463+75
28 Aug 2026, 14:348,388+47
25 Aug 2026, 03:538,341first reading

Engagement

23 posts held, back to 25 July 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 52 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
150.2%
avg views ÷ 9,145 subscribers
Avg views / post
13,700
3 posts measured
Reaction rate
0.512%
reactions ÷ views · ER floor
Posts in window
3
of 23 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 7 November 2026
Posts held23 (25 July 2026 – 7 November 2026)
Views total41,210
Reactions total211
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Nov 2026, 01:25 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.

What this channel posts

Links
176

Lifetime counters from Telegram’s own channel header, read 18 November 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.

Reaction mix

1,147 reactions across 23 posts, in 24 distinct kinds. The most used accounts for 40.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤46640.6%
🔥26923.5%
👏12010.5%
🤡1038.98%
👍635.49%
🫡322.79%
😱221.92%
🖕161.39%
🤯100.872%
🤮80.697%
🥰60.523%
🎉50.436%
👎50.436%
💩50.436%
☃30.262%
👀30.262%
❤‍🔥20.174%
😁20.174%
🤩20.174%
⚡10.087%
4 further kinds40.349%

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

Measured over the 23 most recent posts we hold, published 25 July 2026 to 7 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: 0 of 3 posts held from the last 30 days (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).

7 Nov 2026, 01:45 UTC≈3,310 views125 reactionsread 18 November 2026

Small note to commemorate the 9k subscribers, though that might be late, I didn't want to send a message without a CI close by. We shall keep growing and bringing freedom for everyone, everywhere. 🍰

🔥83❤34🎉5👍3

7 Nov 2026, 01:36 UTC≈19,900 views46 reactionsread 18 November 2026
File

Trusted CI #255: 4aff785a1b82250ab0be7b5e4cae5cdb2f4d988b fix: get_loaded_libraries stopping early due to EACCES

👏24❤16🔥4👍2

2 Nov 2026, 23:32 UTC≈18,000 views40 reactionsread 18 November 2026
File

Trusted CI #254: 2c1d0df3b0d6e40d064927523c4dd1116cb8e832 improve: functions to pick high address; improve: libraries collect

🔥26❤8👀3👏2🐳1

11 Oct 2026, 21:04 UTC≈20,900 views52 reactionsread 18 November 2026
File

Trusted CI #253: b5aa415c2ce1161ab807578ce0414129fbfc6313 add: analyzer target for static analysis

👏26❤17👍6🔥2🍌1

8 Oct 2026, 00:34 UTC≈11,400 views45 reactionsread 18 November 2026
File

Trusted CI #252: 5b0a02bd92b42382c1ffb42b555df54968c802dd update: sync zh_CN README with README.md (#394)

👍34❤7👏4

8 Oct 2026, 00:31 UTC≈8,900 views23 reactionsread 18 November 2026
File

Trusted CI #251: 553f0983d04a245f42989bf522267a44ddf65ff9 improve: properly use Termux's sysroot (#390)

👏16❤7

8 Oct 2026, 00:19 UTC≈7,070 views22 reactionsread 18 November 2026
File

Trusted CI #250: d1332823499b5965f2d46abb6add215a8ee52bb4 fix: switches keep their real state after changing tabs (#397)

❤20👏2

30 Sept 2026, 16:20 UTC≈23,300 views56 reactionsread 18 November 2026
File

Trusted CI #249: 791507aa925e9fec1da9b6dafd86824e744b445a fix: disorganization in datagram messages

❤40🤡11❤‍🔥2👏2👍1

30 Sept 2026, 16:11 UTC≈7,810 views35 reactionsread 18 November 2026
File

Trusted CI #248: eb4f23266ec874bfbd68ee75cdb3dcda967d8ba9 fix: rezygiskd_connect ruturns a closed fd (#395)

❤23🤡9👍2👏1

26 Sept 2026, 02:15 UTC≈22,700 views45 reactionsread 18 November 2026
File

Trusted CI #247: 63d955687b6cd7d6dec07d2d32d461b85812d665 add: GrapheneOS Android 16 QPR2 forkAndSpecialize signature

❤35🤡5👏2👎1🔥1😁1

21 Sept 2026, 18:05 UTC≈22,200 views50 reactionsread 18 November 2026
File

Trusted CI #246: d0393457a6a345d50d6deb516fb826099ef6129d improve: manager uid retrieval through stat; improve: multi user handling (#391)

❤34👍10💩3🤡2👏1

18 Sept 2026, 21:20 UTC≈23,900 views62 reactionsread 6 November 2026
File

Trusted CI #245: b57ca65e1d2e6948612e5de191e6852749eca1ea improve: simplify status reset system (#393) WARNING: First uninstall the current ReZygisk, reboot, then install this version for maximum efficiency. Only needed when coming from versions older 544 (this one).

❤35🤡11🔥6👍5👎2💩2☃1

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

Named by 5 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.

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

“ReZygisk CIs” (@rezygisk_ci), 9,145 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/rezygisk_ci.

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.