民政婚姻 全天秒!全天秒! 晚上十点前都能回! 周六周日不休息!

Channel
天眼查.外卖地址.开房记录.网逃.婚姻.立案.天眼.定位.查档 (信誉频道)
@tyc1818
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
336subscribers
-579 since we began measuring on 16 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002860501118 |
|---|---|
| Type | Channel |
| Username | @tyc1818 |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 16 August 2026 |
| Last confirmed live | 2 November 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 2 November 2026 |
| On Telegram | t.me/tyc1818 |
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 21 September 2026 and assigned it the closest of 31 fixed categories, at 88% 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, 05:10 | 336 | +6 |
| 26 Oct 2026, 04:08 | 330 | +11 |
| 18 Oct 2026, 22:36 | 319 | -27 |
| 12 Oct 2026, 11:49 | 346 | -19 |
| 30 Sept 2026, 20:39 | 365 | -59 |
| 17 Sept 2026, 09:37 | 424 | -193 |
| 9 Sept 2026, 21:39 | 617 | -108 |
| 1 Sept 2026, 01:38 | 725 | -107 |
| 25 Aug 2026, 03:46 | 832 | -67 |
| 17 Aug 2026, 11:58 | 899 | -16 |
| 16 Aug 2026, 19:30 | 915 | no change |
| 16 Aug 2026, 19:15 | 915 | first reading |
Engagement
18 posts held, back to 29 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 18 posts for this entry, the most recent from 15 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 1s
- Average length
- 1s
Measured directly from 1 video 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.
Recent posts
停车库实时定位(覆盖全平台) (抓车抓人 比定位更加准确) 业务 1 提供车牌报单,车在车库就出 文字带链接图片回单 (个别停车场系统无图 进库时间) 回单时间30分钟左右 业务2 车辆监控【单次】 可预约未来10天内出实时,10天内车进库就出 业务3 车辆安装GPS 安装GPS,带车辆水印相机照片视频回单 空不收 @TYC19990 @tianyanshen 早上10.00-凌晨2.00 在线秒
老二网定位 开✔️ 每天 早11点到晚1点 (境外卡 电信 还在维护中) 发现历史赔5000 发现假位置赔10000 提供证据 秒款不嘴硬! ————————————————— 移动定位 开✔️ 目前只开通移动路线 联通 电信 陆续开放中 每天中午11点到晚上1点 误差就在10米到50米左右 出单速度快 出单率高 精准!
立案详情 隔天出单 注意 同案人数出全部 🦕 文档拍照 空收一半 案件号 案件时间 案件详情 立案单位 @TYC19990 @tianyanshen
牛逼 移动定位 ‼️‼️ 🥺10左右出单 🥺目前只要移动号码 🥺早上八点半到到凌晨两点 不关机必出 出必准 基本十到几十米误差 @tianyanshen @TYC19990
支付宝码反 来就反 【包过验证】 支付宝邮箱反 【包过验证】 支付宝码反百分百【包过验证】 QQ反 抖音反【包过验证】 支付宝订单反【不需要配合】 银行卡查预留手机号 (人在就秒) 银行卡查身份证信息(人在就秒) 10年出入境记录 秒 身份证查银行卡信息 秒 各类小业务人在就秒 @TYC19990 @tianyanshen
✅公网网逃(带详情) ✅每天多批😎,最稳最快版本 @tianyanshen @TYC19990
美团订餐记录 美团订房记录 提供手机号出26年最新一页美团点餐记录订房记录 纯美团内部直出 无遗漏 注:点餐只是记录 没有收货地址 只要下单了 当天的记录都能出 0延迟 订房记录比单开好 强推 @TYC19990 @tianyanshen
牛逼 移动定位 ‼️‼️ 🥺10左右出单 🥺目前只要移动号码 🥺早上八点半到到凌晨两点 不关机必出 出必准 基本十到几十米误差 @tianyanshen @TYC19990
公网美团 稳定回 最牛逼的公网美团渠道 手机号报单 出美团近5-10条数据 保真不包漏 包括(闪送,打车,美团) @TYC19990 @tianyanshen
全国名下房, 车位 仓库都能出 稳定当天隔天回 @TYC19990 @tianyanshen
🔩独家白底版出入境➕名下护照 往返地/出发地 都有显示 🔩出18年记录 航班飞往哪里一目了然 多少条记录都出 名下护照/通行证 出入境不带目的地版 😄🥲🤓😙😣强登 出火车票记录 有同行人一起出 报单格式:大头报单 回单时间:当天回 @TYC19990 @tianyanshen
Showing the 12 most recent of 18 posts we hold for @tyc1818. 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.
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.
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 2 November 2026 — this entry's latest reading, not the date you are reading this.
“天眼查.外卖地址.开房记录.网逃.婚姻.立案.天眼.定位.查档 (信誉频道)” (@tyc1818), 336 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/tyc1818.
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.