稳定回单 手机轨迹 够五条出单 直接带定位链接 地址更精准(街道/村) 出单率高 只出三个月内的 20-30条 每天凌晨发车 隔天回

Channel
字节跳动查档.轰炸机
@zjtdcd
On this record: Topic · Growth · Engagement · Posts · Cite this entry
401subscribers
+2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003322548515 |
|---|---|
| Type | Channel |
| Username | @zjtdcd |
| Created | Between 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 2 November 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 2 November 2026 |
| On Telegram | t.me/zjtdcd |
Topic
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 22 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Nov 2026, 10:15 | 401 | +1 |
| 26 Oct 2026, 03:56 | 400 | +3 |
| 18 Oct 2026, 16:36 | 397 | +7 |
| 11 Oct 2026, 19:36 | 390 | -3 |
| 1 Oct 2026, 21:55 | 393 | -10 |
| 16 Sept 2026, 12:37 | 403 | -2 |
| 9 Sept 2026, 08:22 | 405 | -7 |
| 30 Aug 2026, 15:06 | 412 | +2 |
| 24 Aug 2026, 02:16 | 410 | +6 |
| 16 Aug 2026, 03:16 | 404 | +5 |
| 8 Aug 2026, 05:49 | 399 | no change |
| 7 Aug 2026, 18:36 | 399 | first reading |
Engagement
19 posts held, back to 1 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 page of 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 19 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
再最早的488,到888,再到1888,用户越来越多,需求越来越大,数据量全部最新数据,50亿数据库
过几天全面升级1888得了,再也没有888得了,只卖1888
开户app 低价出售128u,数据50亿,全是最新数据,数据不定时更新
车管所业务 检验记录 保险记录 转让记录 转递记录 补换记录 抵押记录
京东地址 快递 外卖一体 提供:姓名身份号手机号 最新一条地址带商品 最近多条地址带商品 历史全部所有地址 订单详情给最新三条订单 回单给购物详情图和运单号 外卖给订单号 在线基本都是秒
微信破解实名 微信公网反手机号 微信公网实名 如果你知道对方的部分信息 可以与我沟通 能走破解就走破解 破解不是百分之百出 告知破解不行就只能公网了 只要账号没有问题,公网基本都能出
人员轨迹 报单:姓名+身份证+手机号 出两个月内活动轨迹记录 部分含微信 支付宝账号 保真不保漏 低于3条不收费
公网抖音评论提取 纯内部直出 非市面上破解找评论版本 提供抖音号报单 隐私/封禁/白号/私密 都可以出 全网独一线 二合一版本 保真不保漏 当天隔天回
个人名下所有卡号带余额 回单:报单5-7天回单 借记卡、储蓄卡、信用卡 正常卡全部都出 注意敏感人物扣单收费
个人名下卡 三合一版本 稳定当天隔天回单 保证不堵车 可以备注一张可以不出 带名下公司 名下etc车辆 保真不保漏 代理给优势
京东快递 出最近一条和最近三条购物地址 如地址空 京东商城有三个月内的购买记录,可能发第三方快递三通一达极兔顺丰,可选择性出单 假一赔三 全网独家一条线
Showing the 12 most recent of 19 posts we hold for @zjtdcd. 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.
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 2 November 2026 — this entry's latest reading, not the date you are reading this.
“字节跳动查档.轰炸机” (@zjtdcd), 401 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/zjtdcd.
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.