Telegram RegisterThe public register of Telegram
Telegram profile photo for PixelLineage by Quick

Channel

PixelLineage by Quick

@PixelLineage

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

519subscribers

+4 since we began measuring on 22 August 2026

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

Register entry

Telegram ID-1002203488898
TypeChannel
Username@PixelLineage
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded22 August 2026
Last confirmed live23 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 23 August 2026
On Telegramt.me/PixelLineage

Growth

51551951722 Aug 2026, 11:00 — 515 subscribers23 Aug 2026, 21:34 — 519 subscribers22 Aug 2026, 11:0023 Aug 2026, 21:34
2 measurements spanning 1 day, 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 514–520 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 21:34519+4
22 Aug 2026, 11:00515first reading

Engagement

20 posts held, back to 1 November 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
26.4%
avg views ÷ 519 subscribers
Avg views / post
137
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 20 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 held20 (1 November 202522 August 2026)
Views total137
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken22 Aug 2026, 11:00 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.

Recent posts

22 Aug 2026, 09:18 UTC137 viewsread 22 August 2026

lineage-23.2-20260822-quick-alioth OneDrive | SourceForge lineage-23.2-20260822-quick-munch OneDrive | SourceForge Changelog: * august security patch * new los updater * keep updater checks daily for integrity * internal bluetooth permission fixes * updated revanced prebuilts * source upstream and minor patches Check pinned message 📌 Smoking and Drinking is injurious to health.

30 Jun 2026, 23:22 UTC719 viewsread 22 August 2026

If you enjoy this project and want to support its development, consider sponsoring it! Your contributions help keep the updates coming. Every bit counts—thank you!

7 Jun 2026, 23:46 UTC≈1,250 viewsread 22 August 2026

lineage-23.2-20260607-quick-alioth OneDrive | SourceForge lineage-23.2-20260607-quick-munch OneDrive | SourceForge Changelog: * june security patch * added auto-updater for integrity * source upstream Check pinned message 📌 Smoking and Drinking is injurious to health.

25 May 2026, 11:00 UTC≈1,520 viewsread 22 August 2026

lineage-23.2-20260525-quick-alioth OneDrive | SourceForge lineage-23.2-20260525-quick-munch OneDrive | SourceForge Changelog: * update keybox * buttons settings crash fix * fixed bugs with revanced implementation Check pinned message 📌 Smoking and Drinking is injurious to health.

15 May 2026, 00:40 UTC≈1,630 viewsread 22 August 2026

lineage-23.2-20260515-quick-alioth OneDrive | SourceForge lineage-23.2-20260515-quick-munch OneDrive | SourceForge Changelog: * may security patch * update keybox and fp * update ksu legacy * upstream lineage sources * drop irrelevant thermal configs * added back pixel bootanimation * bring back old calibration for auto brightness on munch * make home search use google search page (same behaviour as pixel phone) *

22 Apr 2026, 03:09 UTC≈2,040 viewsread 22 August 2026

lineage-23.2-20260501-quick-alioth OneDrive | SourceForge lineage-23.2-20260430-quick-munch OneDrive | SourceForge Changelog: * update keybox and fp * improved audio latency on bluetooth devices * use high perf task profiles for UI rendering * fixed usb tethering on windows * misc. optimizations & upstream Notes: * Android 16 has blur enabled by default. If you want to save battery and have a smoother UI, disable

17 Apr 2026, 14:03 UTC≈1,700 viewsread 22 August 2026

If you enjoy this project and want to support its development, consider sponsoring it! Your contributions help keep the updates coming. Every bit counts—thank you!

16 Apr 2026, 08:47 UTC≈1,620 viewsread 22 August 2026

lineage-23.2-20260417-quick-alioth OneDrive | SourceForge lineage-23.2-20260417-quick-munch OneDrive | SourceForge Changelog: * match signal bars as aosp/pixel * improve UI and blur rendering * update ksu 0.9.5 to ksu legacy 3.2.2 (get apk from notes) * directly open inner page on battery app info settings (took from GrapheneOS) * fixed ignore window secure flags * fixed nfc on munch * misc. fixes and improvements

11 Apr 2026, 15:16 UTC≈1,410 viewsread 22 August 2026

HOTFIX PUSHED - April 11 Switched from Cortex A76 to A55, enhancing overall efficiency and ensuring smoother, faster performance. Thanks @peternoz for recommendation! Please head to Settings -> System -> System updates links updated on previous post.

11 Apr 2026, 04:54 UTC≈1,340 viewsread 22 August 2026
Photo

lineage-23.2-20260411-quick-alioth OneDrive | SourceForge lineage-23.2-20260411-quick-munch OneDrive | SourceForge Changelog: * Android 16 QPR2 April security patch. * 32-bit apps will no longer work. If you have any, delete them before updating. * KernelSU-Next removed due to regressions. Revert to KernelSU 0.9.5 (get APK from notes). * Dropped Leica Micam. * Updated Revanced prebuilts. * Updated Twemoji prebuilt

18 Feb 2026, 21:24 UTC≈1,950 viewsread 22 August 2026

lineage-22.2-20260224-quick-alioth OneDrive | SourceForge lineage-22.2-20260224-quick-munch OneDrive | SourceForge Changelog: - Update keybox for integrity - 95 audio bugs fixed - Minor RAM management fixes Known Bugs: 1] "ok google" voice trigger doesn't work. Play Integrity Note: This ROM currently uses a prebuilt keybox to pass integrity checks. It works for many apps, but some banking apps may not function pr

29 Jan 2026, 00:50 UTC≈2,350 viewsread 22 August 2026

lineage-22.2-20260129-quick-alioth OneDrive | SourceForge lineage-22.2-20260129-quick-munch OneDrive | SourceForge Changelog: - Update keybox for integrity - Update kernel Known Bugs: 1] "ok google" voice trigger doesn't work. Play Integrity Note: This ROM currently uses a prebuilt keybox to pass integrity checks. It works for many apps, but some banking apps may not function properly. A fix is not guaranteed, bu

Showing the 12 most recent of 20 posts we hold for @PixelLineage. 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 — 1,153,195 of 1,623,166entries 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 2 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 23 August 2026 — this entry's latest reading, not the date you are reading this.

“PixelLineage by Quick” (@PixelLineage), 519 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/PixelLineage.

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.