100%现绑微反手机号😉😉😉 范冰冰独家复活✅ 三天回一批 微反破解身份证😉😉😉 提供名字地区 1-2左右回 公网微反身份证😉😉😉😉
👍2

Channel
@jingshui13141
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry
17,867subscribers
+8,150 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003798639132 |
|---|---|
| Type | Channel |
| Username | @jingshui13141 |
| Description | 天眼查司法/网逃/案件/定位/流水 查卡司法/冻结原因/查料的类型! 网络逃犯/嫌疑仁查询/案件细节! 手机查身份证/银行卡余额/流水! 微信提取好友列表/盘口打份必备! 出入境记录/飞机/签证/高铁记录! 全家戸籍信息/个仁结婚记录! 在逃仁员信息/查被抓案件详情! 名下手机号/淘宝/美团/快递地址 手机超级精准定位 开房记录/同住仁员 汽车轨迹/仁物轨迹 司法冻结/网逃仁员/案件记录 手机定位/查身份证/全家戸籍 银行流水/微信提取/手机反查 照片找仁/开房记录/同住记录 婚姻记录/微信实名/支付实名 |
| Created | Between 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 November 2026 |
| Measurements held | 55 |
| Confirmed unchanged | 1 time, most recently 17 November 2026 |
| On Telegram | t.me/jingshui13141 |
Hacking & security — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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.
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 in near-verbatim form on 1 other registered channel. This entry also sits inside a group of 7 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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 |
|---|---|---|---|
| @tbxggg/4354 Aug 2026, 12:20 UTC | @jingshui13141/534 · this entry8 Aug 2026, 05:59 UTC | 1.00 | 4 days |
| @tbxggg/49012 Aug 2026, 06:49 UTC | @jingshui13141/550 · this entry12 Aug 2026, 10:39 UTC | 1.00 | 3.8 hours |
| @jingshui13141/557 · this entry14 Aug 2026, 11:20 UTC | @tbxggg/7468 Sept 2026, 13:17 UTC | 1.00 | 25 days |
| @tbxggg/56822 Aug 2026, 08:05 UTC | @jingshui13141/598 · this entry22 Aug 2026, 10:28 UTC | 1.00 | 2.4 hours |
| @tbxggg/6681 Sept 2026, 05:35 UTC | @jingshui13141/660 · this entry1 Sept 2026, 09:54 UTC | 1.00 | 4.3 hours |
| @tbxggg/113226 Oct 2026, 09:42 UTC | @jingshui13141/961 · this entry2 Nov 2026, 09:19 UTC | 1.00 | 7 days |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @tbxggg | 9 (8/8 hand-verifiable sample passed) | 0.98 | 7.1 hours | @tbxggg (6–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. 5 of the 5 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 49 comparable posts for this entry, running 4 August 2026 to 16 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.
Of the group of 7 channels, the one whose matching posts we hold earliest is @bgshark03. That channel is not among the channels listed above, so this entry may share no posts with it and this does not say where this entry’s content came from. It is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, last confirmed 17 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.
This channel is in a group of 7 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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 |
|---|---|---|
| 17 Nov 2026, 17:36 | 17,867 | +22 |
| 14 Nov 2026, 15:17 | 17,845 | +76 |
| 11 Nov 2026, 19:36 | 17,769 | +46 |
| 9 Nov 2026, 22:10 | 17,723 | +14 |
| 8 Nov 2026, 10:45 | 17,709 | +24 |
| 7 Nov 2026, 08:41 | 17,685 | +12 |
| 6 Nov 2026, 07:48 | 17,673 | +24 |
| 5 Nov 2026, 07:25 | 17,649 | +6 |
| 4 Nov 2026, 09:17 | 17,643 | +22 |
| 3 Nov 2026, 08:55 | 17,621 | +5 |
| 2 Nov 2026, 10:05 | 17,616 | +20 |
| 1 Nov 2026, 09:36 | 17,596 | +4 |
| 31 Oct 2026, 11:47 | 17,592 | +5 |
| 30 Oct 2026, 09:46 | 17,587 | -1 |
| 29 Oct 2026, 07:19 | 17,588 | +31 |
| 28 Oct 2026, 04:56 | 17,557 | +26 |
| 27 Oct 2026, 06:30 | 17,531 | +42 |
| 26 Oct 2026, 09:56 | 17,489 | +42 |
| 25 Oct 2026, 11:35 | 17,447 | +51 |
| 24 Oct 2026, 08:58 | 17,396 | first reading |
189 posts held, back to 3 August 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 79 pages of 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. It is computed over the 55 of 75 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 17 November 2026 |
|---|---|
| Posts held | 189 (3 August 2026 – 17 November 2026) |
| Views total | 63,746 |
| Reactions total | 116 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 19:36 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.
Lifetime counters from Telegram’s own channel header, read 17 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.
Measured directly from 2 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.
172 reactions across 80 posts, in 13 distinct kinds. The most used accounts for 63.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 109 | 63.4% | |
| ❤ | 40 | 23.3% | |
| 🎉 | 4 | 2.33% | |
| 🤣 | 3 | 1.74% | |
| 💯 | 2 | 1.16% | |
| 🔥 | 2 | 1.16% | |
| 😎 | 2 | 1.16% | |
| 😴 | 2 | 1.16% | |
| 🤔 | 2 | 1.16% | |
| 🤗 | 2 | 1.16% | |
| 🤷♂ | 2 | 1.16% | |
| 🤡 | 1 | 0.581% | |
| 🤯 | 1 | 0.581% |
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 91 of the 189 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 172 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 189 most recent posts we hold, published 3 August 2026 to 17 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.
Telegram’s own ‘edited’ marker: 13 of 75 posts held from the last 30 days (17.3%) 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).
100%现绑微反手机号😉😉😉 范冰冰独家复活✅ 三天回一批 微反破解身份证😉😉😉 提供名字地区 1-2左右回 公网微反身份证😉😉😉😉
👍2
五年医疗记录😉😉😉 同行代理来拿价格 私信我看板 假一赔十 带病种,金额,具体自己看 假一赔十 假一赔十 对比了一下市面上有的医疗记录,此版本最清晰,出单最快,资料最全 报单格式:身份证+姓名
自家技术已突破 高德地图轨迹😉😉😉😉 稳定回单 渠道在线 就秒回单 同行代理找我拿价格 利润拉满 历史所有去过地址 历史所有打车记录 高德机票记录 高德订酒店 能出酒店记录 他历史旅游记录+时间 所有导航记录 没有遗漏 概率出车牌号 只要在高德上使用过的都能显示 抓人神器 比美团 邮政 各种外卖快递都好 敏感提前说加钱出 不提前说收费不出单! 报单提供 姓名 身份证 手机号
公司对公名下卡 😉😉😉 个人名下卡三合一😉😉😉 可以带排除 排除不收费 出多少都一个价 其他渠道空的来出概率带余额‼️
出入境😉😉😉任何单百分百全网唯一都统统出,外面失败的都来,我在就秒 @B5200B
👍2
大数据征信 😉😉😉 法院版犯罪记录😉😉😉 出入境记录百分百😉😉😉 范冰冰源头本人读就秒 不秒直接送不要钱 @B5200B
👍1
提供 姓名身份证 报单😉😉😉 能看见各种贷款风险记录 借贷次数 名下车辆等 总还款金额 法院执行案件 被执行案件内容 个人能力消费 空给图收费,全天秒回单。
个人大关联😉😉😉 出来的百分百认识 打电话核验 有多少给多少 2条以下免单 出来的全是九族七大姑八大姨 文字全户空的直接上 提供:名字身份证
👍1
国政名下证件 😉😉😉 国政app绑定所有证件照 已知全国名下证都有 身份证 行驶证 驾驶证 健康证 户口本 献血证 离婚证 结婚证 出生证 社保卡 来往港澳通行证 护照 等 有多少出多少,用处自己想有多牛逼 一个证件也正常收,空不收费 提供:姓名证件号大头 不需要有效期
24小时秒出联通降价! 普通用户 😉😉 翡翠/铂金 😉😉 机器人🆔 @fbbnb666_bot
开同特价 😉😉😉限量 单开出近5年记录 同住人出近1-3年记录 1-3天回单
公网实时网逃带撤销详情😉😉😉 优先网逃后撤销 撤销带详情 全天在线秒单 空给图也收费 源头渠道 同行代理来拿价 网逃 涉毒 失信 是一体的云搜系统 如果没有网逃但是有涉毒和失信都是可以赠送的条子全天秒价格全网最低 另外接黑龙江全省业务 开同 刑侦全户 飞火人轨等 公网无盲机主 公网实时网逃详情撤销 白天全天秒 一手条 同行代理来拿价~
👍2
Showing the 12 most recent of 189 posts we hold for @jingshui13141. 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.
@jingshui13141 edited 2 posts 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.
We recorded 7 posts on @jingshui13141 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.
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.
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.
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 17 November 2026 — this entry's latest reading, not the date you are reading this.
“范冰冰 【源头批发查档业务】” (@jingshui13141), 17,867 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/jingshui13141.
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.