Telegram RegisterThe public register of Telegram
Telegram profile photo for Pixel Props

Channel

Pixel Props

@PixelProps

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry

14,112subscribers

+238 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001394853245
TypeChannel
Username@PixelProps
DescriptionMagisk modules & guides by @T3SL4 https://github.com/Pixel-Props https://www.pling.com/p/2129780 https://pixelprop.pages.dev
CreatedBetween 1 June 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live22 August 2026
Measurements held16
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/PixelProps

Growth

13,87414,11413,9946 August 2026 — 13,874 subscribers6 August 2026 — 13,883 subscribers7 August 2026 — 13,914 subscribers8 August 2026 — 13,967 subscribers9 August 2026 — 13,971 subscribers10 August 2026 — 13,980 subscribers11 August 2026 — 13,985 subscribers12 August 2026 — 14,023 subscribers12 August 2026 — 14,021 subscribers14 August 2026 — 14,031 subscribers15 August 2026 — 14,061 subscribers17 August 2026 — 14,085 subscribers18 August 2026 — 14,097 subscribers19 August 2026 — 14,104 subscribers20 August 2026 — 14,114 subscribers22 August 2026 — 14,112 subscribers14,1126 August 202622 August 2026
16 measurements spanning 16 days, net +238. 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 13,838–14,150 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 01:4614,112-2
20 Aug 2026, 15:4814,114+10
19 Aug 2026, 16:5514,104+7
18 Aug 2026, 14:3514,097+12
17 Aug 2026, 11:2714,085+24
15 Aug 2026, 20:2514,061+30
14 Aug 2026, 07:2714,031+10
12 Aug 2026, 22:4214,021-2
12 Aug 2026, 01:1614,023+38
11 Aug 2026, 00:0313,985+5
10 Aug 2026, 03:2113,980+9
9 Aug 2026, 06:4313,971+4
8 Aug 2026, 06:1613,967+53
7 Aug 2026, 09:3613,914+31
6 Aug 2026, 10:4113,883+9
6 Aug 2026, 03:0613,874first reading

Engagement

43 posts held, back to 18 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 30 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
31.7%
avg views ÷ 14,112 subscribers
Avg views / post
4,470
24 posts measured
Reaction rate
0.327%
reactions ÷ views · ER floor
Posts in window
24
of 43 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 22 August 2026
Posts held43 (18 June 202622 August 2026)
Views total107,232
Reactions total351
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken22 Aug 2026, 12:59 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

Photos
46
Videos
6
Links
102

Lifetime counters from Telegram’s own channel header, read 22 August 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

524 reactions across 42 posts, in 12 distinct kinds. The most used accounts for 62.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
32962.8%
🔥6312.0%
😢5310.1%
❤‍🔥244.58%
🤩163.05%
😨112.10%
🎉101.91%
91.72%
🏆50.954%
👍20.382%
👌10.191%
🙏10.191%

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

Measured over the 43 most recent posts we hold, published 18 June 2026 to 22 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
5
across the posts below
Posts paid on
5
of 43 we hold a reading for · 12%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @PixelProps. 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 43 most recent posts we hold for this entry, published 18 June 2026 to 22 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

22 Aug 2026, 06:21 UTC592 views10 reactionsread 22 August 2026

build.prop update Full pipeline overhaul is live. Changelog: - Complete CI rewrite with matrix builds - Weekly automatic OTA dumps (every Sunday) - Manual trigger support for specific devices or all - Android 17 support - Proper EROFS + sparse + boot/init_boot handling - Lower memory extraction - Duplicate detection (skips already released modules) - Telegram now only posts download links (no more zip spam) Module

9👌1

Signed Tesla

21 Aug 2026, 15:11 UTC≈1,160 views6 reactions1 Starread 22 August 2026
File

File, posted without a caption

6

Signed build.prop

21 Aug 2026, 15:11 UTC≈1,150 views6 reactions1 Starread 22 August 2026
File

File, posted without a caption

6

Signed build.prop

21 Aug 2026, 15:11 UTC≈1,130 views7 reactions1 Starread 22 August 2026
File

File, posted without a caption

7

Signed build.prop

21 Aug 2026, 15:11 UTC≈1,130 views5 reactions1 Starread 22 August 2026
File

File, posted without a caption

5

Signed build.prop

21 Aug 2026, 15:11 UTC≈1,140 views7 reactions1 Starread 22 August 2026

Pixel Props — New OTA Available ! Tag: build-20260821 Modules: 4 Devices: - Pixel 11: Cubs_CD1A.260714.001.A9.zip - Pixel 11 Pro: Grizzly_CD1A.260714.001.A9.zip - Pixel 11 Pro XL: Kodiak_CD1A.260714.001.A9.zip - Pixel 11 Pro Fold: Yogi_CD1A.260714.001.A9.zip

7

Signed build.prop

14 Aug 2026, 02:32 UTC≈3,210 views31 reactionsread 22 August 2026
Photo

Well i guess KSU is working 👍

🔥228👍1

Signed Tesla

13 Aug 2026, 15:13 UTC≈3,180 views18 reactionsread 22 August 2026

BetterKnownInstalled v1.5.0 is out Just pushed a new release with some important behavioral fixes: - No longer wipes packages-warnings.xml (that was only causing repeated warning dialogs and has nothing to do with DroidGuard/Play Integrity) - System packages (system="true") are now properly skipped instead of being marked as Play Store installs - packageSource="2" is now added when missing (not just replaced) - Als

❤‍🔥171

Signed Tesla

13 Aug 2026, 08:46 UTC≈3,140 views29 reactionsread 22 August 2026

HaGeZi GitHub restricted again A few days ago HaGeZi got hit by the usual automated bots reporting the account. GitHub locked the repo + account and forced a password reset. Classic “fraud detection” nonsense on a project that’s been running for years with 25k+ stars. xRuffKez (DNSBunker) stepped up immediately and they’re now hosting the full official mirror together. Lists refresh every 4 hours straight from HaG

😢253👍1

Signed Tesla

12 Aug 2026, 14:29 UTC≈2,820 views5 reactionsread 22 August 2026
File

Pixel 10 Pro - Blazer generic_system_google-user 17 CP2A.260805.005 15828068 release-keys

5

Signed build.prop

12 Aug 2026, 14:29 UTC≈2,710 views5 reactionsread 22 August 2026
File

Pixel 10 Pro XL - Mustang mustang-user 17 CP2A.260805.005 15828068 release-keys

5

Signed build.prop

12 Aug 2026, 14:29 UTC≈2,530 views7 reactionsread 22 August 2026
File

Pixel 9 Pro - Caiman caiman-user 17 CP2A.260805.005 15828068 release-keys

7

Signed build.prop

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

Posts edited after publishing

@PixelProps edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
10 August 2026
Most recent edit
14 August 2026

Citation-graph rank

Citation-graph rank — 79,269 of 1,584,142entries 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 7 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.

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.

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.

Magisk alpha
@magiskalpha · 65,367
Telegram ranks this channel #18 of 40 here — alongside 39 others — read 21 August 2026
LSPosed
@LSPosed · 189,402
Telegram ranks this channel #39 of 57 here — alongside 56 others — read 17 August 2026

This channel appears in 2 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 22 August 2026 — this entry's latest reading, not the date you are reading this.

“Pixel Props” (@PixelProps), 14,112 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/PixelProps.

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.