新增自动查群注册时间机器人,使用方法看上面两条。
Signed 邦少

Channel
@o520925
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
300subscribers
+0 since we began measuring on 3 November 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001970919076 |
|---|---|
| Type | Channel |
| Username | @o520925 |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 3 November 2026 |
| Last confirmed live | 12 November 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 2 times, most recently 12 November 2026 |
| On Telegram | t.me/o520925 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Nov 2026, 03:28 | 300 | no change |
| 3 Nov 2026, 10:22 | 300 | first reading |
20 posts held, back to 7 December 2023 — 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.
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 1 November 2026 |
|---|---|
| Posts held | 20 (7 December 2023 – 1 November 2026) |
| Views total | 90 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Nov 2026, 10:22 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.
2 reactions across 2 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 100.0% |
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 5 of the 20 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 2 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 7 December 2023 to 1 November 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.
Telegram’s own ‘edited’ marker: 1 of 2 posts held from the last 30 days (50.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
新增自动查群注册时间机器人,使用方法看上面两条。
Signed 邦少
需要查群注册时间: @CQQZBOT (查群结果直接转发不用修改) —————————— 结果: 收费:一号一积分 文本1(群数量+群号) 文本2(群数量) 文本3(群全部信息)
Signed 邦少
需要群注册时间如图 查完群的文本转发过去:@CQQZBOT
Signed 邦少
查Q号内自建群号(无需密码/号码就行) 已经更新查群最新数据 可以查到2026年的自建群 查群机器人:@ZYchaqunBot
Signed 邦少
免密查询QQ业务 pinned a photo
查Q号内自建群号(无需密码/号码就行) 查群机器人:@ZYchaqunBot 现在外面不少在收老群的
❤1
Signed 邦少
查询QQ业务 查Q号内自建群号(无需密码/号码就行) 现在外面不少在收老群的 可批量查询老绑老密(也可以手机号查Q的老绑)
❤1
Signed 邦少
查群机器人:@ZYchaqunBot 查老绑机器人:@ChalaobangdBot 查老密机器人:@CXLMBABot (可手机号反查QQ) U自助充值机器人:@FhkmjqrBot 购买成功复制文本里面卡密,发到本机器人就自动换取次数 支付宝微信充值联系客服:@CL925
Signed 邦少
一切正常 有问题联系客服:@CL925
Signed 邦少 没回请弹语音
查Q号内自建群号(无需密码/号码就行) 现在外面不少在收老群的 查询Q群的信息或资料的业务都可以咨询我
Signed 邦少 没回请弹语音
新业务:筛选入群方式----群活跃度----群多少人数(都可以查)
Signed 邦少 没回请弹语音
查群:因客户反馈部分号码会没群 机器人查完结果转发给我查群注册时间 (我这边就可以排除转让出去的群跟被封的群) 这样子做到百分百有群,也是一群一次。
Showing the 12 most recent of 20 posts we hold for @o520925. 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.
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.
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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“免密查询QQ业务” (@o520925), 300 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/o520925.
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.