Telegram RegisterThe public register of Telegram

Channel

๐’€๐’–๐’“๐’Š

@yuriiroot

On this record: Growth ยท Engagement ยท Reactions ยท Stars ยท Posts ยท Citations ยท Cite this entry

38,143subscribers

+211 since we began measuring on 6 August 2026

Risers and fallers across the register ยท movement among entries of 31,623โ€“100,000.

Register entry

Telegram ID-1002682088604
TypeChannel
Username@yuriiroot
CreatedBetween 1 March 2025 and 31 July 2025โ€” estimated from Telegramโ€™s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/yuriiroot

Growth

37,93238,14338,037.56 August 2026 โ€” 37,932 subscribers6 August 2026 โ€” 37,957 subscribers7 August 2026 โ€” 37,992 subscribers8 August 2026 โ€” 38,020 subscribers9 August 2026 โ€” 38,043 subscribers10 August 2026 โ€” 38,081 subscribers11 August 2026 โ€” 38,101 subscribers12 August 2026 โ€” 38,122 subscribers13 August 2026 โ€” 38,143 subscribers6 August 202613 August 2026
9 measurements spanning 7 days, net +211. 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 37,900โ€“38,175 and does not start at zero.
Measurement log โ€” every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 03:5638,143+21
12 Aug 2026, 07:2338,122+21
11 Aug 2026, 08:2438,101+20
10 Aug 2026, 11:1438,081+38
9 Aug 2026, 07:5438,043+23
8 Aug 2026, 10:5938,020+28
7 Aug 2026, 12:5537,992+35
6 Aug 2026, 15:1837,957+25
6 Aug 2026, 03:0637,932first reading

Engagement

23 posts held, back to 20 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 17 pagesof Telegramโ€™s post history, 20 posts per page.

ERR ยท 30 days
49.4%
avg views รท 38,143 subscribers
Avg views / post
18,800
23 posts measured
Reaction rate
0.3%
reactions รท views ยท ER floor
Posts in window
23
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 12 August 2026
Posts held23 (20 July 2026 โ€“ 12 August 2026)
Views total433,030
Reactions total1,301
Forwards / commentsnot exposed by the public surface โ€” not measured, not estimated
Readings taken12 Aug 2026, 20:41 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

1,236 reactions across 22 posts, in 31 distinct kinds. The most used accounts for 37.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
โค46237.4%
๐Ÿคช21317.2%
๐Ÿ‘16413.3%
๐Ÿ”ฅ15712.7%
๐Ÿ‘Œ544.37%
๐Ÿค“312.51%
๐Ÿ˜191.54%
๐Ÿค”191.54%
๐Ÿคจ181.46%
โšก171.38%
๐Ÿ˜ญ100.809%
โคโ€๐Ÿ”ฅ90.728%
๐ŸŽ‰90.728%
๐Ÿ’Š90.728%
๐Ÿ™Š90.728%
๐Ÿ†’50.405%
๐Ÿ˜ˆ50.405%
๐Ÿ™ˆ40.324%
๐Ÿ‘€30.243%
๐Ÿ’…30.243%
11 further kinds161.29%

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,301reactions 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 20 July 2026 to 12 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
1
across the posts below
Posts paid on
1
of 23 we hold a reading for ยท 4%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars โ€” bought with money โ€” on a post by @yuriiroot. 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 23 most recent posts we hold for this entry, published 20 July 2026 to 12 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.

Recent posts

12 Aug 2026, 00:59 UTCโ‰ˆ4,650 views48 reactionsread 12 August 2026
Forwarded from @aerathfunsPhoto

Hi everyone, I uploaded the new version (oss-166) and all of future version updates will be visible in the root manager too (it will download the release version through GitHub) You can use this code if you want to implement a similar update checker mechanism (you will need a hosting service, also you will need to edit the code for version calculations): https://github.com/frknkrc44/HMA-OSS/tree/update-checker Thaโ€ฆ

โค41๐Ÿ”ฅ4๐Ÿ‘3

Signed VD Priv8 (VD171) ๐Ÿ‡ง๐Ÿ‡ท๐Ÿ‡ท๐Ÿ‡บ๐Ÿ‡ฎ๐Ÿ‡ณ๐Ÿ‡จ๐Ÿ‡ณ๐Ÿ‡ฎ๐Ÿ‡ท

11 Aug 2026, 19:22 UTCโ‰ˆ6,130 views15 reactionsread 12 August 2026

Join @BlankAssistance and @RootDetected โค๏ธ

โค11๐Ÿ”ฅ2๐Ÿ‘1๐Ÿคทโ€โ™‚1

Signed VD Priv8 (VD171) ๐Ÿ‡ง๐Ÿ‡ท๐Ÿ‡ท๐Ÿ‡บ๐Ÿ‡ฎ๐Ÿ‡ณ๐Ÿ‡จ๐Ÿ‡ณ๐Ÿ‡ฎ๐Ÿ‡ท

10 Aug 2026, 08:01 UTCโ‰ˆ9,050 views37 reactionsread 12 August 2026
File

COPG-VD v5.1.0 The most effective Global Device Spoofer. Download: https://t.me/RootDetected/4049 Source code & How to use: https://github.com/VD171/COPG-VD Changelog: - The Android version is no longer spoofed. ANDROID_VERSION, SDK_INT, SDK_FULL and CODENAME describe the ROM, not the build being spoofed. A device told its SDK is newer than it really is has apps calling APIs its framework does not have: Google's apโ€ฆ

โค24๐Ÿ˜ญ7๐Ÿ‘5๐Ÿคฏ1

Signed VD Priv8 (VD171) ๐Ÿ‡ง๐Ÿ‡ท๐Ÿ‡ท๐Ÿ‡บ๐Ÿ‡ฎ๐Ÿ‡ณ๐Ÿ‡จ๐Ÿ‡ณ๐Ÿ‡ฎ๐Ÿ‡ท

6 Aug 2026, 06:06 UTCโ‰ˆ17,100 views54 reactionsread 12 August 2026
File

COPG-VD v5.0.1 The most effective Global Device Spoofer. Download: https://t.me/RootDetected/3988 Source code & How to use: https://github.com/VD171/COPG-VD Changelog: - Updated FINGERPRINT and Build info to: ZP11.260618.005. - Added auto-update, from the WebUI (Check Update / Update Now) or once per boot. . Can be turned off in the WebUI: "Auto-update JSON on boot". - A daily workflow keeps COPG-VD.json.example onโ€ฆ

โค43๐Ÿ‘4๐Ÿ˜ญ3๐Ÿ”ฅ2๐Ÿ—ฟ2

Signed VD Priv8 (VD171) ๐Ÿ‡ง๐Ÿ‡ท๐Ÿ‡ท๐Ÿ‡บ๐Ÿ‡ฎ๐Ÿ‡ณ๐Ÿ‡จ๐Ÿ‡ณ๐Ÿ‡ฎ๐Ÿ‡ท

5 Aug 2026, 05:14 UTCโ‰ˆ12,400 views78 reactionsread 12 August 2026
Forwarded from @PixelProps

New soft-root tools dropped ! Two interesting projects using the same public kernel vuln (GhostLock) for temporary root (no bootloader unlock): - Root My Galaxy (Samsung) - Root My Pixel (Pixel devices) - Root My OnePlus Both give temporary KernelSU / ReSukiSU root on supported firmware. Root is lost after reboot and only works on specific builds for now. Worth keeping an eye on if youโ€™re on a supported device.

โค59๐Ÿ”ฅ11๐Ÿค“8

Signed VD Priv8 (VD171) ๐Ÿ‡ง๐Ÿ‡ท๐Ÿ‡ท๐Ÿ‡บ๐Ÿ‡ฎ๐Ÿ‡ณ๐Ÿ‡จ๐Ÿ‡ณ๐Ÿ‡ฎ๐Ÿ‡ท

5 Aug 2026, 04:58 UTCโ‰ˆ13,800 views23 reactionsread 12 August 2026
Forwarded from @rezygisk_ciFile

Trusted CI #238: e42886f48eb1c9eabcc94f08a3c3af0cdbffb99e fix: gid position in A17 nativeForkAndSpecialize signature

โค19โšก2๐Ÿ”ฅ2

Signed VD Priv8 (VD171) ๐Ÿ‡ง๐Ÿ‡ท๐Ÿ‡ท๐Ÿ‡บ๐Ÿ‡ฎ๐Ÿ‡ณ๐Ÿ‡จ๐Ÿ‡ณ๐Ÿ‡ฎ๐Ÿ‡ท

3 Aug 2026, 19:11 UTCโ‰ˆ16,200 views137 reactionsread 12 August 2026
Forwarded from @TrickyStoreOSS

TrickyStoreOSS is back and its BIG! Today marks the release of TrickyStoreOSS v3.0.0 packed with major refactoring and detection fixes that push our implementation ahead of the proprietary alternative. Never knew a project born out of pure frustration would grow into something this big, let it be the countless number of forks or the contributions made. This project has run on community support and love from day oneโ€ฆ

โค98๐Ÿ‘19๐Ÿ”ฅ8โšก5๐Ÿคช3๐Ÿ™Š3๐Ÿค”1

Signed VD Priv8 (VD171) ๐Ÿ‡ง๐Ÿ‡ท๐Ÿ‡ท๐Ÿ‡บ๐Ÿ‡ฎ๐Ÿ‡ณ๐Ÿ‡จ๐Ÿ‡ณ๐Ÿ‡ฎ๐Ÿ‡ท

30 Jul 2026, 22:45 UTCโ‰ˆ21,800 views73 reactionsread 12 August 2026

I'm not stupid to let myself be insulted and lose face when the post is garbage, lies, and baseless.

๐Ÿคช36โค11๐Ÿ‘8๐Ÿ”ฅ4๐Ÿคจ4โšก2โคโ€๐Ÿ”ฅ2๐Ÿ˜2

Signed ๐—ฌ๐˜‚๐—ฟ๐—ถ

30 Jul 2026, 22:42 UTCโ‰ˆ21,100 views32 reactionsread 12 August 2026

I wish everyone would just leave each other alone. I didn't do anything to affect bad him, but he deliberately wants to create drama to attract viewers.

๐Ÿคช16โค8๐Ÿคจ3โคโ€๐Ÿ”ฅ2๐Ÿ‘2๐Ÿค“1

Signed ๐—ฌ๐˜‚๐—ฟ๐—ถ

30 Jul 2026, 22:38 UTCโ‰ˆ20,500 views24 reactionsread 12 August 2026

There is a person is a hypocrite. He always justifies it by saying "I don't hate you,"while the post remains the same, the lies and baseless accusations remain. Just tell the truth. I know that anyone like -> hate. That's perfectly normal.

๐Ÿคช11โค10๐Ÿ‘3

Signed ๐—ฌ๐˜‚๐—ฟ๐—ถ

30 Jul 2026, 22:24 UTCโ‰ˆ18,900 views24 reactionsread 12 August 2026

In short, he hates me and that's what he said. There's no concrete evidence. It's just a lie.

๐Ÿคช17โค5๐Ÿ‘2

Signed ๐—ฌ๐˜‚๐—ฟ๐—ถ

30 Jul 2026, 22:20 UTCโ‰ˆ18,400 views27 reactionsread 12 August 2026

Please find me a post that criticizes Android root developers.

๐Ÿคช20โค3๐Ÿ‘3๐Ÿ’Š1

Signed ๐—ฌ๐˜‚๐—ฟ๐—ถ

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

Citation-graph rank โ€” 161,574 of 1,160,990entries 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.

Forward network

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 4 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 13 August 2026 โ€” this entry's latest reading, not the date you are reading this.

โ€œ๐’€๐’–๐’“๐’Šโ€ (@yuriiroot), 38,143 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/yuriiroot.

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.