停车库实时定位 (抓车抓人 比定位更加准确) 提供车牌报单,车在车库就出 文字带链接图片回单 (个别停车场系统无图 进库时间) 回单时间30分钟左右 可预约未来10天内出实时,10天内车进库就出 空不收 早上10.00-凌晨2.00 在线秒
👍4❤1

Channel
@uuub3
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
164,463subscribers
-139 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
| Telegram ID | -1002520503737 |
|---|---|
| Type | Channel |
| Username | @uuub3 |
| Description | @fa6bot 社工库 @s7cbot 大头户籍 @ngccc 客服 @uuub3 主频道 @mysbot 双向点我 |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/uuub3 |
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 8 August 2026 and assigned it the closest of 31 fixed categories, at 96% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 03:53 | 164,463 | -21 |
| 11 Aug 2026, 06:54 | 164,484 | -43 |
| 10 Aug 2026, 06:31 | 164,527 | -37 |
| 9 Aug 2026, 03:00 | 164,564 | -43 |
| 8 Aug 2026, 00:57 | 164,607 | +5 |
| 7 Aug 2026, 19:45 | 164,602 | first reading |
18 posts held, back to 6 November 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 15 pagesof 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 12 August 2026 |
|---|---|
| Posts held | 18 (6 November 2025 – 12 August 2026) |
| Views total | 19,188 |
| Reactions total | 10 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 18:05 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 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.
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.
73 reactions across 16 posts, in 2 distinct kinds. The most used accounts for 93.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 68 | 93.2% | |
| 👍 | 5 | 6.85% |
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 16 of the 18 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 73reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 6 November 2025 to 12 August 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.
停车库实时定位 (抓车抓人 比定位更加准确) 提供车牌报单,车在车库就出 文字带链接图片回单 (个别停车场系统无图 进库时间) 回单时间30分钟左右 可预约未来10天内出实时,10天内车进库就出 空不收 早上10.00-凌晨2.00 在线秒
👍4❤1
新业务,抖音查一年评论,有单来报。
❤3
医疗记录恢复,之前查不了的可以来查了!!
❤2
❤️❤️❤️❤️❤️❤️❤ ❤️❤️❤️❤️❤️❤️❤️❤️❤️❤️ 🎯 合作招募资源对接) 全国范围招:公安 刑侦 网安 快递 银行 三大运营商 各类高权限岗位人员 📈 有权限就有收入,带你赚金豆,日入上万不是梦,干三月就能提前退休! 三网手机通话记录,清单 微信号出身份证号码, 微信提取好友。挖生意好用 📍 手机定位找人、一抓一个准 🚗 查车辆轨迹、行驶路线、名下车辆 💔 查开房记录、小三信息、婚姻次数 🐟 卡带鱼数据:有名字+卡号就能查,所有银行都行 🧠 一句话总结:专业找人、查车、查记录,别人找不到的,我可以
❤3
🕠骑士查档案例图🕠 【微信/QQ好友提取】 【微信反查】 【银行卡反查】 【企业法人反查】 【护照/通行证反查】 【支付宝收款码反查】 【名下全部微信账号】 【名下全部支付宝账号】 【抖音/小红书/快手/qq 反查/手机号】 【模糊找人】 【照片找人】 【模糊搜索】 📱📱【地址】 外卖地址快递地址 水电地址 📌【行踪-轨迹】 【出入境记录】 【手机轨迹】 【手机定位】 【人物轨迹】 【开房记录】 【飞火记录】 【车辆轨迹】 【背景大调查】 【学籍记录】 【疫苗记录】 【婚姻记录】 【学信网】 【出生证明】 【社保记录】 【医保记录】 【全家户籍】 【医疗记录】 【人物小关联】 【人物大关联】 【金融贷款记录】 【出入境证件】 名下财产大调查 【公司财产】 【名下房子】 【名下银行卡】 【名下所有车子】 【企业工商内档】 【私户/公户/微信/支付宝流水】 具体价格咨询客服 📱【犯罪违法】 【犯罪在逃】【…
❤8
综合快递 一年内记录 包含京东 邮政 极兔 圆通 申通 一年内记录带单号有些快递单号只能在半年内可以查询 隔天回单
❤6
企业开票信息 全部开票内容 超级详细
🔐 超强个人档案(全维度汇总) 📌 一人一档 · 信息完整 · 清晰可查 🏠 资产概览 🏡 名下房产 🚗 名下车辆 📄 身份 / 出行 1️⃣ 出入境记录 2️⃣ 驾照 / 行驶证 / 电动自行车证 3️⃣ 护照 / 往来港澳通行证 🏥 医保 / 社保 4️⃣ 医保卡 · 社保卡 · 居住证 5️⃣ 医疗保险个人账户资金 🎓 资质 / 教育 6️⃣ 各类证书(资格证 / 职业证) 7️⃣ 学历信息(学历层级 / 毕业院校) 👥 关系 / 状态 8️⃣ 关联人信息 · 身份证有效期 9️⃣ 常用地址(居住 / 往来) 🔟 就职单位 案例找客服拿
❤5
👤 机主信息:7U 🪪 身份证有效期:5U 🏠 全家户籍:15U ✈️ 出入境记录:10U 🚗 查车主:5U 🎓 学历查询:3U 🏢 法人信息:3U 💳 卡反查询:3U
❤3
外面风大雨大,回国必查 ➡️网逃 35u ➡️犯罪记录 35u ➡️服刑记录 35u ➡️司法冻结 210u ➡️名下诉讼 35u ➡️出入境限制 50u ➡️重点人员排查 35u ➡️立案详情 220u 消除案底 消除网逃 私聊客服
❤10
😀全国找车业务 全国现实手贴实体贴GPS (偏远地区+米) 😀找到车反馈照片,绕车一周视频验证, 😀补完余款告诉你具体停放地址,GPS后台账号密码,流程完成 😀GPS可休眠 最长可以实时查看定位半年目标车辆
❤2
外面风大雨大,回国必查 ➡️网逃 35u ➡️犯罪记录 35u ➡️服刑记录 35u ➡️司法冻结 210u ➡️名下诉讼 35u ➡️出入境限制 50u ➡️重点人员排查 35u ➡️立案详情 220u 消除案底 消除网逃 私聊客服
❤6
Showing the 12 most recent of 18 posts we hold for @uuub3. 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 — 340,623 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.
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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“骑士信息查询🏡🕹 @ngccc” (@uuub3), 164,463 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/uuub3.
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.