Telegram RegisterThe public register of Telegram

Channel

LSPosed IT Leaks

@LSP_Leaks

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

4,702subscribers

-3 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1002674104804
TypeChannel
Username@LSP_Leaks
Descriptioni like the LSP project, i just doing some historical recording, that's all. t.me/LSP_Leaks
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live11 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/LSP_Leaks

Growth

4,7024,7054,703.510 Aug 2026, 18:17 — 4,705 subscribers11 Aug 2026, 08:56 — 4,702 subscribers10 Aug 2026, 18:1711 Aug 2026, 08:56
2 measurements taken within a single day, net -3. 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 4,702–4,705 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 08:564,702-3
10 Aug 2026, 18:174,705first reading

Engagement

19 posts held, back to 25 August 2025the 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 19 posts for this entry, the most recent from 21 December 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
3

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

1,087 reactions across 18 posts, in 8 distinct kinds. The most used accounts for 20.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁22620.8%
🔥22420.6%
21419.7%
👍19317.8%
🤯1089.94%
🤔655.98%
😱514.69%
👏60.552%

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

Measured over the 19 most recent posts we hold, published 25 August 2025 to 21 December 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

21 Dec 2025, 03:50 UTC≈36,800 views145 reactionsread 12 August 2026
File

LiviaFontes Leaked on 25.12.21 10:08 AM, @XiaoCaiYe This idiot intentionally leaked it to get traffic.

😁100🤔25👍20

17 Dec 2025, 16:38 UTC≈28,000 views57 reactionsread 12 August 2026
File

Only Meet Devices Failure I think we will soon run out of publicly available keybox

😱3712👍8

5 Dec 2025, 08:22 UTC≈27,800 views83 reactionsread 12 August 2026

Can't you mark the source when you repost? It's all private sharing, which is heartbreaking to see ( This channel has no ads, it doesn't affect your profits either 😢

😁47🔥24🤯12

5 Dec 2025, 08:04 UTC≈25,500 views60 reactionsread 12 August 2026
File

File, posted without a caption

🔥42🤔108

4 Dec 2025, 12:58 UTC≈32,400 views84 reactionsread 12 August 2026
File

5MayRain Leaked on 25.12.04, leaker claimed he stole the file while helping someone else back up their cloud drive.

🔥726👍6

10 Nov 2025, 10:14 UTC≈24,400 views109 reactionsread 12 August 2026
File

pc040905 Leaked on 2025-11-10, developer banned it slowly, causing the leaked person to download it.

🤯7322👍14

6 Nov 2025, 16:18 UTC≈19,600 views85 reactionsread 12 August 2026
File

pc040905 Leaked on 2025-11-06, cause of leak unknown

64🤯12👍9

6 Nov 2025, 16:18 UTC≈17,000 views10 reactionsread 12 August 2026

模块按用户区分启用状态(以及 new api 的作用域请求屏蔽状态) 取消了旧版模块没选作用域就提示禁用模块的设定 本次更新涉及数据库格式升级,如遇数据迁移异常或失败等问题请及时反馈。可以在 /data/adb/lspd/config_backup 找到备份的更新前的数据库。

10

18 Sept 2025, 13:07 UTC≈26,800 views118 reactionsread 12 August 2026
File

Sumo1201 Leaked on 2025-09-18 Reason for leakage: 那个人进了内测群后炫耀,然后别人说让他发包出来看看是不是真的,然后他就直接发了 as for Github account, I think the account was bought

👍81🤔2215

16 Sept 2025, 15:49 UTC≈19,900 views44 reactionsread 12 August 2026
File

noire7777 Leaked on 2025-09-16, cause of leak unknown

🔥308😱6

Showing the 12 most recent of 19 posts we hold for @LSP_Leaks. 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,112,199 of 1,169,250entries 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.

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.

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 11 August 2026 — this entry's latest reading, not the date you are reading this.

“LSPosed IT Leaks” (@LSP_Leaks), 4,702 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/LSP_Leaks.

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.