Channel
@TLS8888
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Posts · Citations · Cite this entry
1,431subscribers
+2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001662820827 |
|---|---|
| Type | Channel |
| Username | @TLS8888 |
| Created | Between 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 10 August 2026 |
| On Telegram | t.me/TLS8888 |
Hacking & security — 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 11 August 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 why it has no browse page of its own yet.
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.
Posts published here appear word for word 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @TLS8888/1054 · this entry18 Jul 2026, 03:16 UTC | @weixin21/347218 Jul 2026, 03:16 UTC | 1.00 | under a minute |
| @TLS8888/1062 · this entry25 Jul 2026, 14:23 UTC | @weixin21/348025 Jul 2026, 14:23 UTC | 1.00 | under a minute |
| @TLS8888/1064 · this entry30 Jul 2026, 04:12 UTC | @weixin21/348230 Jul 2026, 04:12 UTC | 1.00 | under a minute |
| @TLS8888/1067 · this entry1 Aug 2026, 14:14 UTC | @weixin21/34851 Aug 2026, 14:14 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @weixin21 | 14 (7/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (12–2) |
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. None of the 1 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 15 comparable posts for this entry, running 16 July 2026 to 5 August 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.
Across the whole group of 2, the earliest publisher we hold is @TLS8888 — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 7 August 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.
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 17:44 | 1,431 | +2 |
| 7 Aug 2026, 18:50 | 1,429 | no change |
| 7 Aug 2026, 05:31 | 1,429 | first reading |
19 posts held, back to 16 July 2026 — the 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 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.
| Window | Rolling 30 days · latest post in window 5 August 2026 |
|---|---|
| Posts held | 19 (16 July 2026 – 5 August 2026) |
| Views total | 6,429 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 05:31 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.
（柠檬·天眼查 极速秒出） 😃😀😃😀😀😃 ✅司法冻结✅犯罪网逃✅立案详情 ✅人脸识别✅个户全户✅手机定位 ✅手机轨迹✅开房记录✅人轨车轨 ✅微支实名✅查收款码✅抖音实名 ✅卡号实名✅手机实名✅现住地址 ✅外卖快递✅常用号码✅护照反查 ✅名下车房✅名下公司✅名下护照 ✅名下号码✅名下卡号✅身份正反 ✅银行流水✅微支流水✅微Q提取 ✅查出入境✅人员关联✅卡内余额 ✅模糊找人✅银行预留✅公司法人 ✅飞机火车✅婚姻医疗✅学历征信 ✅车牌车主✅车辆违章✅社保记录 ✅通话记录✅出生证明✅工商内档 新增查档业务 有律师事务所的话可以谈价格 国外盘口可查网逃 价格一手 需要的宝子滴滴 ========================== 👍👍👍👍👍👍 🥳柠檬客服 👍@NM_8888 🥳被限制私聊请联系👍 @nmsxbot 🥳手机卡自助机器人 @NMWL_bot
云机手表微信，到货，需要来 大量纯国内爆粉加人号、主动加新朋友那边有提示好友、不提示非境外用户、聊天不爆红、隔天不死、几天都不死。基本当天就可以用（包加人的号）十几天都不死。精聊也可以用。一天可➕10人 非常好用每天都是回购、包的兄弟们 每天都在大量出📱 不好用顾客不会一直拿而且还加量。不是市场垃圾号。虽然号一样但是质量绝对不一样 真的不错稳定了、可以查地址每天都在出货 👍👍现货秒发 稳定无压力 ========================== 👍👍👍👍👍👍 🥳柠檬客服 👍@NM_8888 🥳被限制私聊请联系👍 @nmsxbot 🥳手机卡自助机器人 @NMWL_bot
一伴婚恋 心对婚恋 依恋婚恋 美缘婚恋 😀一线姻缘 only婚恋 甄选婚恋 七大婚恋APP 可挑男女，欢迎问价 ========================== 👍👍👍👍👍👍 🥳柠檬客服 👍@NM_8888 🥳被限制私聊请联系👍 @nmsxbot 🥳手机卡自助机器人 @NMWL_bot
新品———————-⚡️⚡️⚡️ 介绍：美国/香港护照支付宝！！ sm支付宝，可做收付 售后：上号第一时间检查是否实名，支付密码， 售后发货一小时内反馈。不包出售后的违规。 【后期可解封16U一次】 ========================== 👍👍👍👍👍👍 🥳柠檬客服 👍@NM_8888 🥳被限制私聊请联系👍 @nmsxbot 🥳手机卡自助机器人 @NMWL_bot
国内微信号满月、一年无视，带身份正反图片 纯新非解☄️ 🉑进企业、🉑手持、三色人脸解封⚠️ 价格下调，需要宝子滴滴 售后：包登录，找回 ========================== 👍👍👍👍👍👍 🥳柠檬客服 👍@NM_8888 🥳被限制私聊请联系👍 @nmsxbot 🥳手机卡自助机器人 @NMWL_bot
193-7387-5069湖南电信6 134-6922-2572湖南移动28 153-6706-7824湖南电信44 177-3113-7740河北电信51 153-6912-7391河北电信54 191-9154-0354陕西电信41 171-9118-4009北京虚拟32 198-4867-9760四川移动55 181-9690-4137新疆电信59 181-6038-6422新疆电信60 190-3980-7177新疆电信62 189-9768-0981新疆电信63 180-4081-0779新疆电信64 130-7992-1372新疆联通65 190-1846-6701新疆电信66 155-6930-2589新疆联通69 185-8829-2497广东联通70 147-6964-9969云南移动71 157-1875-6292云南移动72 184-6952-9906云南移动73 136-5789-8086广西移动74 1…
👇点击下方按钮查看产品价格表VIP👇 👉国内网络登录的微信全系列 👉国外网络登录的微信全系列 👉国内微信纯私人鱼号系列 👉国内微信原机带设备全国包邮 👉微信备份包满月三月半年 👉企业微信公众号小程序系列 👉微信解封+实名+绑定微信换绑卡 👉 QQ全系列全等级国卡美卡 👉支付宝+淘宝店铺+闲鱼 👉京东实名绑卡全系列老号 👉抖音实名号+千粉号+直登 👉钉钉个人高级专业实名号 👉微博高信用分老号黄V号 👉陌陌高等级号男女全系列 👉小红书老号百粉千粉老号 👉快手实名老号百粉私人号 👉灵魂探探老白号实名老号 👉美篇闲趣岛全名K歌三条 👉飞机成品号+代开会员 👉所有国外软件成品号 👉各app软件接码注册+代实名 👉定制电报机器人+频道加粉及点赞 👉国内电话卡流量卡+国外流量卡注册卡 👉苹果安卓工作机 👉主营微信QQ支付宝抖音微博等各类账号点击联系柠檬
新增物联卡自助机器人 可以自助充值流量套餐和下单 @NMWL_bot
交友婚恋———✅✅✅✅ 闲趣岛云机号— 心对备份包—-❤️🔥❤️🔥❤️🔥已恢复 一伴备份包— 伴婚恋——- 心对婚恋——- 依恋婚恋 ——- 美缘婚恋——- 一线姻缘 ——- only婚恋——- 甄选婚恋 ——- 七大婚恋APP 介绍：都是实名号，可挑性别年龄 售后：包登录，找回 ========================== 👍👍👍👍👍👍 🥳柠檬客服 👍@NM_8888 🥳被限制私聊请联系👍 @nmsxbot 🥳手机卡自助机器人 @NMWL_bot
柠檬私人QQ报价 🏆私人星月—36u 💰可解封 🔥销售火爆🔥 🏆私人单太—50u💰 可解封 🔥销售火爆🔥 🏆私人双太—63u💰 可解封 🔥销售火爆🔥 🏆私人三太—73u💰无人脸 可解封 🔥销售火爆🔥 🏆私人皇冠—135u 💰 可解封 🔥销售火爆🔥 🏆月卡靓号—90u 🔥【带年费超级会员 不弹窗 不爆红 0违规】 带一个月卡位，到期前可以自行换绑走，高品质私人号，抗封耐造，加人加群，也可以付费解封13u 都有货 需要的老板滴滴👍👍👍👍👍 🥳柠檬客服 👍@NM_8888 🥳被限制私聊请联系👍 @nmsxbot
📱📱📱🐈🐈🐈🐈🐈✅ 产品：抖音店铺蓝 机构蓝 比特转移 价格：40u 售后：店铺后台 机构后台 比特店铺成品全新 机构成品全新 不出垃圾箱 不封私信 掉线随便登陆 可以上任意浏览器 ========================== 👍👍👍👍👍👍 🥳柠檬客服 👍@NM_8888 🥳被限制私聊请联系👍 @nmsxbot 🥳手机卡自助机器人 @NMWL_bot
新增物联卡自助机器人 可以自助充值流量套餐和下单 @NMWL_bot
Showing the 12 most recent of 19 posts we hold for @TLS8888. 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 — 453,542 of 1,151,006entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“柠檬 微信号商 微信账号 微信老号 微信白号 微信数据号 QQ账号” (@TLS8888), 1,431 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/TLS8888.
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.