Telegram RegisterThe public register of Telegram
Telegram profile photo for LSPosedArchives

Channel

LSPosedArchives

@LSPosedArchives

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry

27,631subscribers

+1,955 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-1001421629791
TypeChannel
Username@LSPosedArchives
DescriptionCI Builds are built automatically on every push to the primary branch. They are extremely unstable and only for testing and bugreport, and we don't take any responsibility of the consequences of flashing them. Debug builds have telemetry.
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live19 November 2026
Measurements held66
Confirmed unchanged1 time, most recently 19 November 2026
On Telegramt.me/LSPosedArchives

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 10 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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

25,11227,63126,371.56 August 202619 November 2026
66 measurements spanning 104 days, net +1,955. 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 24,734–28,009 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 66
Measured (UTC)SubscribersChange
19 Nov 2026, 05:1827,631+139
16 Nov 2026, 03:3827,492+300
12 Nov 2026, 13:1627,192+102
10 Nov 2026, 08:5927,090+96
8 Nov 2026, 17:4026,994+82
7 Nov 2026, 13:2526,912+32
6 Nov 2026, 09:4626,880+24
5 Nov 2026, 12:5626,856+32
4 Nov 2026, 11:2526,824+35
3 Nov 2026, 08:5926,789+25
2 Nov 2026, 10:0126,764+37
1 Nov 2026, 10:1626,727+53
31 Oct 2026, 06:5426,674+46
30 Oct 2026, 04:5926,628+18
29 Oct 2026, 06:4026,610+47
28 Oct 2026, 04:0026,563+126
27 Oct 2026, 04:5626,437+57
26 Oct 2026, 03:3726,380+54
25 Oct 2026, 00:5826,326+53
23 Oct 2026, 23:0526,273first reading

Engagement

28 posts held, back to 30 December 2023 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 162 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
58.2%
avg views ÷ 27,631 subscribers
Avg views / post
16,100
12 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
12
of 28 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 17 November 2026
Posts held28 (30 December 2023 – 17 November 2026)
Views total192,830
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken20 Nov 2026, 06:04 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
≈8
Links
≈121

Lifetime counters from Telegram’s own channel header, read 20 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 12 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).

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

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.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

Reveny
@reveny1 · 7,558
#1
LSPosed
@LSPosed · 202,699
#2
Pixel Props
@PixelProps · 14,440
#3
Sakion Team
@Sakion_Team · 2,066
#4
LibChecker CI
@libchecker_ci · 3,638
#5
Magisk Base || Magisk modules and other
@magiskmodules22 · 12,954
#6
XPL-EX
@xpl_ex · 3,062
#7
Hide My Applist
@HideMyApplist · 42,210
#8
Rem01 Project
@rem01schannel · 11,035
#9
unify°shelf
@unify_zip · 1,527
#10
Play integrity fix NEXT
@PifNEXT · 6,849
#11
APatch Updates
@APatchChannel · 26,083
#12
MDGram Messenger
@mdgram_messenger · 19,346
#13
YAKT | Channel
@YAKTC · 790
#14
KernelSU
@KernelSU · 76,504
#15
5ec1cff
@real5ec1cff · 40,431
#16
Magisk alpha
@magiskalpha · 66,563
#17
Real Nullptr
@nullptr_dev · 21,547
#18
Lsposed Modules Updates Tracker
@lsposed_Modules_Updates_Trackers · 5,015
#19
Android dumps
@android_dumps · 5,758
#20
NPatch
@NPatch · 20,122
#21
QQ Updates
@QQUpdates · 10,283
#22
Voyager HyperOS Update
@VoyagerMIUIUpdate · 22,395
#23
HyperCeiler | Canary Test
@cemiuiler_canary · 21,741
#24
MTU Wallpapers 😍
@MTUWallpapers · 524
#25
Mystic GSI Updates
@mysticgsi · 17,846
#26
AdClose Official
@AdClose · 12,491
#27
QAuxiliary CI Builds
@QAuxiliary_CI · 19,703
#28
Médicos pela Vida
@medicospelavidas · 2,895
#29
Thanox Release
@thanoxrel · 3,226
#30
YuKongA | Channel
@YuKongA13579 · 12,283
#31
Mobile Tech Cloud
@mobiletechfiles · 9,670
#32
rootArt
@rootart · 823
#33
GMS Flags 2.0 • GMS Insight
@gms_insight · 2,148
#34
SCENE Downloads
@scene2023 · 57,928
#35
Redmi Note 8 Pro 🇮🇩 | Update
@BegoniaUpdateIndonesia · 6,798
#36

Read from Telegram’s recommendation API, most recently 14 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

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.

Hide My Applist
@HideMyApplist · 42,210
Telegram ranks this channel #11 of 24 here — alongside 23 others — read 30 August 2026
APatch Updates
@APatchChannel · 26,083
Telegram ranks this channel #16 of 37 here — alongside 36 others — read 14 September 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 19 November 2026 — this entry's latest reading, not the date you are reading this.

“LSPosedArchives” (@LSPosedArchives), 27,631 subscribers as measured 19 November 2026. Telegram Register, tgregister.com/channel/LSPosedArchives.

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.