Telegram RegisterThe public register of Telegram

Channel

PixysOS

@PixysOS

On this record: Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

1,694subscribers

-7 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001325986623
TypeChannel
Username@PixysOS
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/PixysOS

Growth

1,6941,7011,697.56 August 2026 — 1,701 subscribers7 August 2026 — 1,701 subscribers10 August 2026 — 1,698 subscribers13 August 2026 — 1,694 subscribers6 August 202613 August 2026
4 measurements spanning 7 days, net -7. 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 1,693–1,702 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 03:251,694-4
10 Aug 2026, 07:301,698-3
7 Aug 2026, 05:441,701no change
6 Aug 2026, 07:191,701first reading

Engagement

20 posts held, back to 15 January 2024the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof 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 20 posts for this entry, the most recent from 24 March 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

440 reactions across 18 posts, in 14 distinct kinds. The most used accounts for 35.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥15835.9%
8920.2%
👍8820.0%
🥰429.55%
❤‍🔥225.00%
🤝132.95%
🗿81.82%
👏71.59%
40.909%
🥱40.909%
👀20.455%
👎10.227%
😍10.227%
🤷‍♂10.227%

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

Measured over the 20 most recent posts we hold, published 15 January 2024 to 24 March 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

24 Mar 2025, 17:04 UTC≈2,760 views0 reactionsread 7 August 2026

The problem with downloads should be fixed. All existing builds can be downloaded from www.pixysos.com. Sorry for inconvenience. Thanks for patience. ✌️

Signed Shreejoy Dash

21 Nov 2024, 12:15 UTC≈5,730 views15 reactionsread 7 August 2026

https://www.change.org/p/stop-google-from-limiting-custom-roms

👍132

Signed 𝕾𝖚𝖇𝖎𝖓𝖘𝖒𝖆𝖓𝖎

10 Sept 2024, 10:31 UTC≈6,120 views72 reactionsread 7 August 2026
Photo

Guess who's back #VanillaIceCream

🥰38🔥12👍8🗿822👏1🤷‍♂1

Signed Aswin A S

10 Jul 2024, 14:28 UTC≈11,600 views77 reactionsread 7 August 2026

Hello PixysOS community! It's been a while since we started promising stable releases and official builds for Android 14 and never delivered. Main reason being the team has been busy with their personal lives. Rather than rushing out a buggy release, we’ve decided to skip the official builds for Android 14 and set our sights on Android 15 instead. The current source that was in the works based on 14 QPR3 will be pu

54👍11🥱4🥰3🤝2👏1🔥1😍1

Signed 𝕾𝖚𝖇𝖎𝖓𝖘𝖒𝖆𝖓𝖎

21 Apr 2024, 15:50 UTC≈9,360 views36 reactionsread 7 August 2026
Photo

PixysOS v7.2.1 is here !! We have just pushed our latest release based 14 QPR2 ( April asb) to our main github org Most of the features from our previous releases has been added back and further improvements will follow as we are nearing the platform stability and official releases in the coming weeks Maintainers can now build/test the source and let us know if something is missing . Information about the official

🔥24👍65👏1

Signed Aswin A S

21 Apr 2024, 11:47 UTC≈6,050 views41 reactionsread 7 August 2026
Photo

NOT DEAD!! 👉🏻 www.pixysos.com

🔥37👍3👎1

Signed Shreejoy Dash

18 Mar 2024, 07:29 UTC≈8,650 views42 reactionsread 7 August 2026
Photo

The first android trunk stable release (current release: 14-QPR2). Coming soon to a pixys_device near you :) #TeamPixys

🔥31👍11

Signed Aswin A S

29 Feb 2024, 06:30 UTC≈6,380 views10 reactionsread 7 August 2026
Photo

🔅PixysOS v7.1.2 Beta 1 for Oneplus Nord (avicii) 🔹Download: Here 🔹 Recovery: Here #PixysOS #avicii

6👍3🔥1

Signed ѕωєєтσ

26 Feb 2024, 15:49 UTC≈5,960 views11 reactionsread 7 August 2026
Photo

🔅 PixysOS v7.1.2 Beta 5.1 for Nothing Phone (1) 🔹Download: Full OTA | Fastboot 🔹Instructions: XDA Thread 🔹Changelog: XDA Post 🔹Screenshots: GPhotos #PixysOS #Spacewar

👍73🥰1

Signed Aswin A S

25 Feb 2024, 20:59 UTC≈4,530 views12 reactionsread 7 August 2026
Photo

🔅 PixysOS v7.1.2 Beta 3 for Pixel 4 🔹Download: Fastboot Build 🔹Instructions: XDA Thread 🔹Changelog: XDA Post 🔹Screenshots: GPhotos #PixysOS #flame

❤‍🔥8👍2🔥2

Signed Aswin A S

25 Feb 2024, 20:59 UTC≈5,620 views16 reactionsread 7 August 2026
Photo

🔅 PixysOS v7.1.2 Beta 4 for Pixel 4 XL 🔹Download: Fastboot Build 🔹Instructions: XDA Thread 🔹Changelog: XDA Post 🔹Screenshots: GPhotos #PixysOS #coral

❤‍🔥142

Signed Aswin A S

Showing the 12 most recent of 20 posts we hold for @PixysOS. 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 — 959,215 of 1,183,361entries 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.

Mentions

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.

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.

Sarkari results Exams Update
@Sarkari_results_Exams_Update · 133,007
Telegram ranks this channel #55 of 71 here — alongside 70 others — read 13 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list 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 13 August 2026 — this entry's latest reading, not the date you are reading this.

“PixysOS” (@PixysOS), 1,694 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/PixysOS.

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.