28 Aug 2025, 14:41 UTC44 viewsread 12 August 2026
Photo
盖章社保 😤😤😤 不定时秒单 提供信息：名字 身份证号 回单内容：如图所示的社保信息
Channel
文渊查档模版
@WYCDMB
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
12subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002920030841 |
|---|---|
| Type | Channel |
| Username | @WYCDMB |
| Created | Between 1 August 2025 and 28 August 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 24 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/WYCDMB |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 04:16 | 12 | no change |
| 8 Aug 2026, 08:31 | 12 | first reading |
Engagement
20 posts held, back to 28 August 2025 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 28 August 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 34
- Links
- 2
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.
Recent posts
28 Aug 2025, 14:37 UTC38 viewsread 12 August 2026
File
征信记录 😤😤😤 一天多批：稳定回单 提供信息：名字+身份证号码+名下任意手机号 回单内容：如文件的征信报告
28 Aug 2025, 14:36 UTC35 viewsread 12 August 2026
工商局企业股东😤😤😤 三天内回单 20u指一位股东 提供信息： 企业代码跟股东名字 回单内容：对应股东身份证号码
28 Aug 2025, 14:36 UTC35 viewsread 12 August 2026
Photo
破解法人 😤🀄️😤 工商法人 😤🀄️🀄️ 破解和工商的区别在于 破解出单率低 工商出单率高 可以先过一下破解 工作日隔天 回单 提供信息：企业信用代码 出单内容：企业法人身份证号
28 Aug 2025, 14:34 UTC36 viewsread 12 August 2026
Photo
医保缴费记录😤👌😤 参保至今的医保缴费记录 比社保质量好 排敏感 根据基数判断还款能力 找老赖必备！ 提供内容：名字+身份证号码 回单内容：从首次参保（包括历史公司）到最新一条的医保缴费记录
28 Aug 2025, 14:33 UTC35 viewsread 12 August 2026
Photo
个人详细档案 😤😤😤 当天隔天回单 带本人照片给我回的比较快 包括有：常用号、有效期、名下证、名下房、名下护照、出入境记录、公积金、社保单位（缴费记录）、医保单位（缴费记录）、医疗记录、婚姻记录等 保真不保漏 提供信息：名字+身份证号码+大头照 回单内容：个人详细档案 保真不保漏
28 Aug 2025, 14:30 UTC38 viewsread 12 August 2026
Photo
三十年出入境记录😤😤😤 报单带大头 当天隔天回单 提供信息：名字＋身份证号+大头 回单内容：十年出入境记录和名下所有通行证
28 Aug 2025, 14:30 UTC39 viewsread 12 August 2026
Photo
三网名下号 😤👌😤 每天15：00发车 18：00回单 20：00发车 次日凌晨2：00前回单 批量两百个1u 一天两车 稳定回 提供信息：身份证号码（有无名字都可） 回单内容：名下移动联通电信手机号
28 Aug 2025, 14:28 UTC38 viewsread 12 August 2026
File
手机轨迹 单月😤😤😤😤 三月 😤👌😤😤 六月😤😤😤😤 一年 😤😤👌😤 所有😤👌👌😤 开普勒系统定位轨迹 由于设备识别基于WIFI IP GPS APP软件 基站等 多重识别方式 结果直接导出未经过人为编辑，所以个别位置会有误导识别现象，产生经纬跳跃 结果以总体较多出现的位置为准，下单前麻烦和客户明确，数据保真不保漏，避免扯皮 此系统可指定查询截获的短信和手机IMEI串码，手机型号等，手机轨迹以系统为准抓取到多少数据算多少，有数据就收费 部分号码因手机型号，号码异常等原因会查空 空不收费。
28 Aug 2025, 14:24 UTC37 viewsread 12 August 2026
Photo
网逃带撤销 😤😤😤 带拘留撤销 😤😤😤 空回图收费 提供信息：身份证 回单内容：网逃信息
28 Aug 2025, 14:23 UTC31 viewsread 12 August 2026
Photo
网逃带案件详情 👌😤😤 图1 是上过网逃的版本 图2 是没有上过网逃的版本 空回图收费 提供信息：身份证号 回单内容：网逃信息
28 Aug 2025, 14:21 UTC34 viewsread 12 August 2026
Photo
新版极速网逃 😤😤😤 空回图收费 周末不休息
Showing the 12 most recent of 20 posts we hold for @WYCDMB. 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 — 470,903 of 1,627,445entries 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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“文渊查档模版” (@WYCDMB), 12 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/WYCDMB.
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.