Video, posted without a caption
👍62😁6❤3👏2🔥2

Channel
@xiaodoro
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Cite this entry
63,226subscribers
+43,386 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1004489907822 |
|---|---|
| Type | Channel |
| Username | @xiaodoro |
| Description | 社工库 @doro 聊天群 t.me/zhuaijie (禁广告) 使用教程 https://t.me/KHQZB/57 |
| Created | 19 June 2026 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 23 October 2026 |
| Measurements held | 46 |
| Confirmed unchanged | 1 time, most recently 23 October 2026 |
| On Telegram | t.me/xiaodoro |
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 18 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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 |
|---|---|---|
| 23 Oct 2026, 04:20 | 63,226 | +393 |
| 22 Oct 2026, 03:57 | 62,833 | +459 |
| 20 Oct 2026, 18:41 | 62,374 | +281 |
| 19 Oct 2026, 21:04 | 62,093 | +429 |
| 18 Oct 2026, 19:06 | 61,664 | +454 |
| 17 Oct 2026, 20:16 | 61,210 | +630 |
| 16 Oct 2026, 17:01 | 60,580 | +488 |
| 15 Oct 2026, 15:41 | 60,092 | +280 |
| 14 Oct 2026, 18:37 | 59,812 | +547 |
| 13 Oct 2026, 10:49 | 59,265 | +1,865 |
| 9 Oct 2026, 11:14 | 57,400 | +1,885 |
| 5 Oct 2026, 04:00 | 55,515 | +2,353 |
| 28 Sept 2026, 14:14 | 53,162 | +5,088 |
| 17 Sept 2026, 22:20 | 48,074 | +825 |
| 15 Sept 2026, 20:21 | 47,249 | +772 |
| 14 Sept 2026, 02:20 | 46,477 | +955 |
| 12 Sept 2026, 08:55 | 45,522 | +992 |
| 10 Sept 2026, 03:56 | 44,530 | +1,349 |
| 6 Sept 2026, 18:16 | 43,181 | +1,273 |
| 4 Sept 2026, 06:36 | 41,908 | first reading |
103 posts held, back to 19 June 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 160 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.
| Window | Rolling 30 days · latest post in window 23 October 2026 |
|---|---|
| Posts held | 103 (19 June 2026 – 23 October 2026) |
| Views total | 321,527 |
| Reactions total | 1,637 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 23 Oct 2026, 18:45 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 23 October 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.
4,040 reactions across 101 posts, in 46 distinct kinds. The most used accounts for 63.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 2,578 | 63.8% | |
| ❤ | 454 | 11.2% | |
| 🍌 | 173 | 4.28% | |
| 😍 | 155 | 3.84% | |
| 😱 | 146 | 3.61% | |
| 🤔 | 89 | 2.20% | |
| 😨 | 55 | 1.36% | |
| 🤓 | 55 | 1.36% | |
| 🤩 | 32 | 0.792% | |
| 🌭 | 29 | 0.718% | |
| 😁 | 27 | 0.668% | |
| 🔥 | 26 | 0.644% | |
| 🌚 | 24 | 0.594% | |
| 👏 | 24 | 0.594% | |
| 🤨 | 14 | 0.347% | |
| 🥴 | 13 | 0.322% | |
| 🕊 | 12 | 0.297% | |
| 🫡 | 12 | 0.297% | |
| 🗿 | 11 | 0.272% | |
| 🥰 | 11 | 0.272% | |
| 26 further kinds | 100 | 2.48% |
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 102 of the 103 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 4,040 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 103 most recent posts we hold, published 19 June 2026 to 23 October 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @xiaodoro. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 103 most recent posts we hold for this entry, published 19 June 2026 to 23 October 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Video, posted without a caption
👍62😁6❤3👏2🔥2
❤️ 更新2000万 全户数据 pro 查询专属 手机号超大概率直出全家姓名身份证 手机号超大概率直出全家姓名身份证 手机号超大概率直出全家姓名身份证 支付宝付款 给 @doro 发送任意查询信息选择pro查询自助购买 如果需要微信付款联系 @doro520bot 备注微信手动支付
👍41🍌4❤3
智商低+脑残+喜欢白嫖+没花钱也是祖宗+素质低
👍64🙉4😱3🤷♂2
怎么总来些这种臭傻子 脑子不好用 眼睛还瞎 发个身份证就能查出来的东西 非要加个名字 难不成你爹有好几个必须加名字才查得到
👍72👏6❤2😎2
@KLSCQ66bot 无障碍锁机生成器 第二种独家恶搞模式 不用任何权限 打开即消失 没有任何后台 音量直接拉到最大 播放你自定义的音乐 可自定义生成应用的 名字 图片 锁机密码 音乐
👍41😨9🤔7❤2
Posted without readable text
😱65👍19🤔9🤨6🙈6🥰4❤1🤷♀1
公安查询 ❤️ ❗️手机号查询身份证号码 200人民币 💸姓名身份证查询大头 50人民币 🌐身份证姓名开全家户籍300人民币 📱微信开户 📱qq开户 800人民币 💥美团地址 1500人民币 💬联系 @doro520bot
👍24😨14❤8😱5🍌2🤔2😢2😁1
pro 查询 充值 已恢复 @doro 发送任意信息选择 pro查询即可充值 微信充值 暂不稳定 支付宝充值 稳定中!
👍11🤩1
@KLSCQ66bot 无障碍锁机生成器 第二种独家恶搞模式 不用任何权限 打开即消失 没有任何后台 音量直接拉到最大 播放你自定义的音乐 可自定义生成应用的 名字 图片 锁机密码 音乐
👍36❤7
Photo, posted without a caption
👍18❤1
来源于某个频道源码二改 稳定性和原版一样 页表断点追踪 硬件断点追踪
👍18
需要pro查询的 先联系 @doro520bot 付费查询 赚点钱真不容易 收款死了 现在人工代查询
👍37❤2
Showing the 12 most recent of 103 posts we hold for @xiaodoro. 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.
@xiaodoro edited 14 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.
Named by 4 registered channels — 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 23 October 2026 — this entry's latest reading, not the date you are reading this.
“小doro官方” (@xiaodoro), 63,226 subscribers as measured 23 October 2026. Telegram Register, tgregister.com/channel/xiaodoro.
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.