Telegram RegisterThe public register of Telegram
Telegram profile photo for kmemcore (原Paradise内核驱动)

Channel

kmemcore (原Paradise内核驱动)

@ParadiseKMA

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry

24,369subscribers

+8,678 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003177416507
TypeChannel
Username@ParadiseKMA
Created9 October 2025 — measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live12 November 2026
Measurements held63
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/ParadiseKMA

Topic

Gaming — 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 82% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@ParadiseKMA/943 · this entry9 Oct 2026, 14:59 UTC@Cycle1337/127839 Oct 2026, 15:02 UTC1.003 minutes
@Cycle1337/143154 Nov 2026, 22:11 UTC@ParadiseKMA/1263 · this entry5 Nov 2026, 02:16 UTC1.004.1 hours
@ParadiseKMA/1308 · this entry7 Nov 2026, 07:33 UTC@Cycle1337/144638 Nov 2026, 06:08 UTC1.0023 hours
@ParadiseKMA/1345 · this entry10 Nov 2026, 01:00 UTC@Cycle1337/1456610 Nov 2026, 11:52 UTC1.0011 hours
@Cycle1337/1460311 Nov 2026, 07:30 UTC@ParadiseKMA/1385 · this entry11 Nov 2026, 13:00 UTC1.005.5 hours
@Cycle1337/145289 Nov 2026, 17:16 UTC@ParadiseKMA/1345 · this entry10 Nov 2026, 01:00 UTC0.917.7 hours
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@Cycle13377 (6/7 hand-verifiable sample passed)0.986.6 hours@Cycle1337 (4–3)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 1 of the 1 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 114 comparable posts for this entry, running 31 July 2026 to 14 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Recorded under the key clone_mutual, last confirmed 15 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

15,69124,36920,0307 August 202612 November 2026
63 measurements spanning 97 days, net +8,678. 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 14,389–25,671 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 63
Measured (UTC)SubscribersChange
12 Nov 2026, 20:2924,369+240
10 Nov 2026, 17:5424,129+198
9 Nov 2026, 03:3923,931+166
7 Nov 2026, 16:4723,765+124
6 Nov 2026, 18:5023,641+210
5 Nov 2026, 15:5523,431+87
4 Nov 2026, 13:1823,344+69
3 Nov 2026, 14:1423,275+31
2 Nov 2026, 13:5523,244+36
1 Nov 2026, 16:4923,208+79
31 Oct 2026, 18:0823,129+153
30 Oct 2026, 14:4022,976+69
29 Oct 2026, 14:3722,907+78
28 Oct 2026, 15:3522,829+91
27 Oct 2026, 14:1622,738+81
26 Oct 2026, 12:2922,657+78
25 Oct 2026, 10:1022,579+144
24 Oct 2026, 07:2822,435+244
23 Oct 2026, 05:2722,191+69
22 Oct 2026, 08:4622,122first reading

Engagement

241 posts held, back to 9 October 2025 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 81 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
9.41%
avg views ÷ 24,369 subscribers
Avg views / post
2,290
153 posts measured
Reaction rate
2.08%
reactions ÷ views · ER floor
Posts in window
158
of 241 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 15 November 2026
Posts held241 (9 October 2025 – 15 November 2026)
Views total350,896
Reactions total7,291
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Nov 2026, 04: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.

What this channel posts

Photos
38
Videos
2
Links
16

Lifetime counters from Telegram’s own channel header, read 15 November 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
3m 27s
Average length
30s

Measured directly from 7 videos 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

8,340 reactions across 171 posts, in 17 distinct kinds. The most used accounts for 95.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍7,95495.4%
🤣1692.03%
😱951.14%
😭360.432%
🔥180.216%
😘120.144%
😁100.12%
🍌90.108%
🤓80.096%
🕊70.084%
👏50.06%
🥰50.06%
🤩40.048%
🤯40.048%
🎉20.024%
🌚10.012%
😍10.012%

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

Measured over the 241 most recent posts we hold, published 9 October 2025 to 15 November 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

Telegram’s own ‘edited’ marker: 12 of 158 posts held from the last 30 days (7.59%) 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).

15 Nov 2026, 03:55 UTC48 views32 reactionsread 15 November 2026
File

三角洲❤️公益算法解密内核 🎮真正的算法解密,不动任何内存,绝对安全的程序 📲APP启动器不依赖mt管理器,完美规避终端检测 ✅物资显示,过滤高价值物资,精确寻包 🐱人物骨骼,射线,头甲显示 完全公益免费,卡密随便输入即可 全网真正的三角洲公益算法解密,不收取任何费用,无任何套路 ✨更新时间:2026年11月23日 🎮栖月 Kernel公益运营团队 栖月频道: https://t.me/yuenhpdd

👍31😘1

Signed zhinese words

15 Nov 2026, 01:00 UTC898 views32 reactionsread 15 November 2026
Photo

Like_4.0版本[三角洲]更新通知 更新内容: -解决10.11号和谐 - 解密1 UDP解密 - 解密2 模拟算法解密 - 适配vivo iqoo 完美解决战争迷雾 迷雾加密 不动任何内存 拒绝垃圾解密 有一处动内存的地方 支持曝光 可打假逆向 对接par/时间/TWT驱动 驱动下载 点我 漏打文件下载 点我 公益卡密 @Likenb667 共享网页雷达官网 http://108.165.255.191:8080/ 自瞄漏打必须解压文件 添加朋友暗区项目 https://t.me/Likenb667/4295 频道 @Likenb667 交流群 @Likenb669 频道负责人 @Like520A6

👍32

Signed Paradise广告Bot

15 Nov 2026, 01:00 UTC850 views32 reactionsread 15 November 2026
Photo

🌟沙漠风暴和平公益端口 v1.0 -采用独家封包制作 -桌面开启后在局内切换规则 -防高风险/小黑屋/人脸(除设备黑情况) -防内存(特征除外) 卡密:SMFBCN 点击可复制 点我加入官方频道 点我加入官方频道 点我加入官方频道 点我加入官方频道

👍32

Signed Paradise广告Bot

15 Nov 2026, 01:00 UTC793 views32 reactionsread 15 November 2026

Apex_11.13破解版 更新内容: - 更新模拟UDP - 更新模拟执行解密 - 更新apex驱动2.6 (需要重启手机刷入新驱动) (仅支持apex驱动这两个解密) 卡密@asdqw678 下载地址 https://t.me/asdqw678/33 🌟🙃🌟@asdqw678 ❗️❗️@asdqw678

👍32

Signed Paradise广告Bot

14 Nov 2026, 17:33 UTC≈2,210 views48 reactionsread 15 November 2026
Photo

不敢自杀了 怕死后被人把视频加个小浣熊在前面跳舞 评论区还一堆111求求求

👍48

Signed zhinese words

14 Nov 2026, 13:00 UTC≈1,020 views58 reactionsread 14 November 2026
Photo

Like_4.0版本[三角洲]更新通知 更新内容: -解决10.11号和谐 - 解密1 UDP解密 - 解密2 模拟算法解密 - 适配vivo iqoo 完美解决战争迷雾 迷雾加密 不动任何内存 拒绝垃圾解密 有一处动内存的地方 支持曝光 可打假逆向 对接par/时间/TWT驱动 驱动下载 点我 漏打文件下载 点我 公益卡密 @Likenb667 共享网页雷达官网 http://108.165.255.191:8080/ 自瞄漏打必须解压文件 添加朋友暗区项目 https://t.me/Likenb667/4295 频道 @Likenb667 交流群 @Likenb669 频道负责人 @Like520A6

👍58

Signed Paradise广告Bot

14 Nov 2026, 13:00 UTC924 views62 reactionsread 14 November 2026
Photo

🌟沙漠风暴和平公益端口 v1.0 -采用独家封包制作 -桌面开启后在局内切换规则 -防高风险/小黑屋/人脸(除设备黑情况) -防内存(特征除外) 卡密:SMFBCN 点击可复制 点我加入官方频道 点我加入官方频道 点我加入官方频道 点我加入官方频道

👍62

Signed Paradise广告Bot

14 Nov 2026, 13:00 UTC843 views62 reactionsread 14 November 2026

Apex_11.13破解版 更新内容: - 更新模拟UDP - 更新模拟执行解密 - 更新apex驱动2.6 (需要重启手机刷入新驱动) (仅支持apex驱动这两个解密) 卡密@asdqw678 下载地址 https://t.me/asdqw678/33 🌟🙃🌟@asdqw678 ❗️❗️@asdqw678

👍62

Signed Paradise广告Bot

14 Nov 2026, 12:21 UTC≈6,740 views66 reactionsread 15 November 2026
Photo

避雷此频道卖假gpt 盗刷我朋友冷钱包800 @AIzhichon @AIzhichonkf 卖假gpt ,诱导你去他们链接,然后盗刷你冷钱包的u 。

👍66

Signed zhinese words

14 Nov 2026, 11:24 UTC≈1,380 views66 reactionsread 14 November 2026
File

三角洲❤️公益算法解密内核 🎮真正的算法解密,不动任何内存,绝对安全的程序 📲APP启动器不依赖mt管理器,完美规避终端检测 ✅物资显示,过滤高价值物资,精确寻包 🐱人物骨骼,射线,头甲显示 完全公益免费,卡密随便输入即可 全网真正的三角洲公益算法解密,不收取任何费用,无任何套路 ✨更新时间:2026年11月23日 🎮栖月 Kernel公益运营团队 栖月频道: https://t.me/yuenhpdd

👍66

Signed zhinese words

14 Nov 2026, 01:00 UTC864 views37 reactionsread 14 November 2026
Photo

Like_4.0版本[三角洲]更新通知 更新内容: -解决10.11号和谐 - 解密1 UDP解密 - 解密2 模拟算法解密 - 适配vivo iqoo 完美解决战争迷雾 迷雾加密 不动任何内存 拒绝垃圾解密 有一处动内存的地方 支持曝光 可打假逆向 对接par/时间/TWT驱动 驱动下载 点我 漏打文件下载 点我 公益卡密 @Likenb667 共享网页雷达官网 http://108.165.255.191:8080/ 自瞄漏打必须解压文件 添加朋友暗区项目 https://t.me/Likenb667/4295 频道 @Likenb667 交流群 @Likenb669 频道负责人 @Like520A6

👍37

Signed Paradise广告Bot

14 Nov 2026, 01:00 UTC844 views37 reactionsread 14 November 2026
Photo

678三角洲公益算法解密 已适配三角洲新赛季 11.06最新更新解密 本次更新内容如下 更新算法解密 优化辅助性能 修复自瞄无效 修复人物bug 公益卡密: M7A4C1E89F90F1640BC84E006EB24E71 ❗️❗️➡️ @asdqw678 ❗️❗️➡️ @asdqw678 依旧大小地图/Ai 压枪/掩体漏打/算法解密/CPU,GPU 渲染/子追/解密无延迟😶‍🌫️😶‍🌫️😶‍🌫️😶‍🌫️😶‍🌫️😶‍🌫️😶‍🌫️😶‍🌫️😶‍🌫️😶‍🌫️

👍37

Signed Paradise广告Bot

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

Posts edited after publishing

@ParadiseKMA edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
3 November 2026
Most recent edit
4 November 2026

Posts recorded as deleted after publishing

We recorded 10 posts on @ParadiseKMA as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
9 August 2026
Most recent seen missing
3 November 2026
Median time before seen missing
2 days
Seen missing in the last 30 days
5

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

“kmemcore (原Paradise内核驱动)” (@ParadiseKMA), 24,369 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/ParadiseKMA.

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.