Telegram RegisterThe public register of Telegram

Channel

LV内核主频道🇨🇳【永久公益】

@LV520A

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

151,884subscribers

+0 since we began measuring on 12 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID-1001844155436
TypeChannel
Username@LV520A
Description交流群 @LV520ABC 导航频道 @LV520A
CreatedBetween 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live13 August 2026
Measurements held2
On Telegramt.me/LV520A

Topic

Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 13 August 2026 and assigned it the closest of 31 fixed categories, at 70% 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 why it has no browse page of its own yet.

Growth

151,88412 Aug 2026, 23:51 — 151,884 subscribers13 Aug 2026, 00:00 — 151,884 subscribers12 Aug 2026, 23:5113 Aug 2026, 00:00
2 measurements taken within a single day. 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 151,732–152,036 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 00:00151,884no change
12 Aug 2026, 23:51151,884first reading

Engagement

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

ERR · 30 days
11.9%
avg views ÷ 151,884 subscribers
Avg views / post
18,100
11 posts measured
Reaction rate
1.70%
reactions ÷ views · ER floor
Posts in window
16
of 18 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 13 August 2026
Posts held18 (4 July 202613 August 2026)
Views total199,620
Reactions total3,401
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 13:20 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
72
Videos
5
Links
38

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

Video runtime
12s
Average length
12s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

3,401 reactions across 11 posts, in 16 distinct kinds. The most used accounts for 42.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😭1,45242.7%
1,23836.4%
👍36110.6%
😍1103.23%
😱732.15%
🫡722.12%
🎉310.911%
😁170.5%
🤩150.441%
👏140.412%
🙏70.206%
💯50.147%
😴30.088%
🔥10.029%
🤝10.029%
🥰10.029%

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

Measured over the 18 most recent posts we hold, published 4 July 2026 to 13 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.

Recent posts

13 Aug 2026, 06:15 UTC484 views38 reactionsread 13 August 2026
Forwarded from @enennbaFile

三角洲公益解密内核 添加内核陀螺仪自瞄 自瞄水平速度跟垂直速度要保持一致,跳屏速度调低,跟不上速度调高 打头皮压枪力度调高,相反则调低 添加physx地图模型掩体判断,开启后自瞄自动实现漏打功能,漏那打那( 模型掩体判断,会占用设备大量性能,手机发烫,性能跟不上的不要开) 公益三角洲解密项目,卡密随便输入,已更新至8.12日最新解密,内核级驱动,不协议,不十年,不三十天,稳定得吃,安全性拉满 不嘿嘿频道: @enennba

👍305😁2🔥1

Signed 不嘿嘿 hei

13 Aug 2026, 04:18 UTC≈1,620 views27 reactionsread 13 August 2026
Video

落叶公益内核回归更新新频道功能齐全自瞄打火箭都没问题 加入频道 https://t.me/luoyenb521 😀😃😀点击此处跳转落叶官方指定卡网

👍233😁1

13 Aug 2026, 03:40 UTC696 views18 reactionsread 13 August 2026
Forwarded from @BYGWJJFile

爱玩系列全系公益内核启动器3.6 1.取消启动器频道验证 2.更新和平精英自瞄算法, 3.更新和平驱动,适用多款最新驱动 内置 1.lolm 2.无畏契约 3.失控进化 4.和平精英 集成多款爱玩系列辅助,只是一个启动器,本质还是内核,不影响稳定性 内置 1.lolm 2.无畏契约 3.失控进化 4.和平精英 全部都为内核,需给启动器root权限,才可以正常使用。 内置解密全都为算法解密,不动内存 具体辅助驱动请查看历史记录找到对应游戏的压缩包里有对应驱动下载。 爱玩解密内核主频道 @BYGWJJ 永久公益卡密@BYGWJJ 反馈频道 @bhsfss

👍152😁1

Signed hoh .

11 Aug 2026, 14:01 UTC≈4,050 views35 reactionsread 13 August 2026
Forwarded from @angel_kernelFile

🎮Angel(天使)王者公益算法解密内核[2.6版本] ✔️修复验证失败问题 ✔️花重金升级服务器确保所有人正常使用 ✔️修复软件内刷入dit_ko驱动问题 ✔️修复克隆包云更新问题 💻支持CPU渲染后端 安卓16以下推荐使用 😁纯算法解密 无视任何检测 ❌如果内存解密作者死全家 ❌如果内置端口作者死全家 ⭐音量键控制UI隐藏 or 显示 ⚡️解密教程必须看 https://t.me/angeljlpd/4731 ⚡️解密教程必须看 ⭐卡密:@Angel_kernel ✉️作者 @Jinang_Hello 🔝更新频道 https://t.me/angel_kernel 🚨Angel声明: https://t.me/angel_kernel/6049 🤩换装教程:https://t.me/angeljlpd/22697 👽APK使用教程:https://t.me/angeljlpd/22595

👍314

Signed 广告推广号 大量收广告联系@MC52HH

9 Aug 2026, 20:04 UTC≈14,500 views1,337 reactionsread 13 August 2026

Posted without readable text

1,140😍110😱48👍33🎉4🥰1🙏1

9 Aug 2026, 13:34 UTC≈9,070 views38 reactionsread 13 August 2026
Photo

🎮王者Angel无敌公益算法解密内核 💻支持CPU渲染后端 安卓16以下推荐使用 😁纯算法解密 无视任何检测 ❌如果内存解密作者死全家 ❌如果内置端口作者死全家 ⭐音量键控制UI隐藏 or 显示 ⚡️解密教程必须看 https://t.me/angeljlpd/4731 ⚡️解密教程必须看 ⭐卡密:@Angletwt ✉️作者 @Jinang_Hello 🔝更新频道 https://t.me/angel_kernel

👍297😱2

Signed 广告推广号 大量收广告联系@MC52HH

2 Aug 2026, 10:03 UTC≈32,600 views347 reactionsread 13 August 2026

出售本频道与交流群与项目最新源码需要的联系我 @HJK092 不会更新的话将作者联系方式给你

😭206👍7321😱16🫡13🎉6🤩4👏3

1 Aug 2026, 08:42 UTC≈33,900 views528 reactionsread 13 August 2026

2026年8月1日

😭409👍47🫡3810🎉9🙏5🤩4💯3

1 Aug 2026, 08:42 UTC≈33,800 views444 reactionsread 13 August 2026

找到合适的接班人会继续更新,有技术的没时间 没技术的我不放心给你们更新

😭362👍3916🫡16🎉6🤩3💯2

1 Aug 2026, 08:40 UTC≈33,500 views569 reactionsread 13 August 2026

LV一个月前已经退网了 今天以这种方式让大家看一下LV其实挺开心的 像这种大项目的信息怎么可能会真正泛滥出来,你们就看个乐就行了

😭475👍3418😁12👏10🎉6🫡5🤩4

27 Jul 2026, 20:11 UTC≈35,400 views20 reactionsread 13 August 2026
Forwarded from @LVSJHAPhoto

❗️❗️❗️❗️❗️LV内核官方认证数据号 🥇进来看不是全网最便宜死全家🥇 🥇进来看不是全网最便宜死全家🥇 🥇进来看不是全网最便宜死全家🥇 😂同行没我便宜高质量抄宣传词生儿子没屁眼😂 ♥️全网一手号商一个也是批发价♥️ 👉可乐宗旨是薄利多销低价质优👈 😳无视鉴权失败黑号,无限授权 🥵非传统垃圾数据号,纯退游号 🤯客服小姐姐全天2️⃣4️⃣小时在线 ✅100%不鉴别/不人脸/不封号✅ 🧦所有账号问题都包售后🧦 主营:『和平无限授权号』『和平微区扫码号』『和平地铁存款号』『和平Q手打地铁直登号』🎉 ‼️请在购买付款时开启录屏‼️ 👍👍👍购买链接: https://wkaiw.oqzgb.com/shop/SJHABC 🩵官方频道 https://t.me/LVSJHA 免费数据号【每天500个】 封号清理文件【设备黑】 上号器使用教程 🧸橘子/葫芦娃/落叶/小烧鸡/A内核/巴巴托斯/lV内核

12👍7👏1

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

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 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.

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.

“LV内核主频道🇨🇳【永久公益】” (@LV520A), 151,884 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/LV520A.

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.