纯公网微反2件套 😎😎😎 回姓名身份证 包过验证 1-2回
Channel
白月光业务频道
@baiyueguangyewu
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
18,707subscribers
+18,581 since we began measuring on 8 September 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1003775605109 |
|---|---|
| Type | Channel |
| Username | @baiyueguangyewu |
| Created | Between 1 February 2026 and 23 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 September 2026 |
| Last confirmed live | 16 November 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 16 November 2026 |
| On Telegram | t.me/baiyueguangyewu |
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 25 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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 |
|---|---|---|
| 16 Nov 2026, 13:09 | 18,707 | -1,273 |
| 12 Nov 2026, 22:57 | 19,980 | -364 |
| 10 Nov 2026, 14:44 | 20,344 | -34 |
| 9 Nov 2026, 01:08 | 20,378 | -5 |
| 7 Nov 2026, 17:15 | 20,383 | +1 |
| 6 Nov 2026, 13:25 | 20,382 | +1 |
| 5 Nov 2026, 12:17 | 20,381 | +1 |
| 2 Nov 2026, 15:50 | 20,380 | +3 |
| 1 Nov 2026, 13:06 | 20,377 | +1 |
| 31 Oct 2026, 12:56 | 20,376 | -1 |
| 29 Oct 2026, 12:56 | 20,377 | +3 |
| 28 Oct 2026, 15:16 | 20,374 | +2 |
| 27 Oct 2026, 12:35 | 20,372 | +1 |
| 24 Oct 2026, 09:50 | 20,371 | +1 |
| 23 Oct 2026, 06:27 | 20,370 | -1 |
| 22 Oct 2026, 09:05 | 20,371 | -1 |
| 19 Oct 2026, 22:28 | 20,372 | +3 |
| 19 Oct 2026, 00:41 | 20,369 | +1 |
| 17 Oct 2026, 22:56 | 20,368 | +1 |
| 16 Oct 2026, 04:20 | 20,367 | first reading |
Engagement
40 posts held, back to 23 June 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 32 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 0.968%
- avg views ÷ 18,707 subscribers
- Avg views / post
- 181
- 1 post measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 1
- of 40 held
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 22 October 2026 |
|---|---|
| Posts held | 40 (23 June 2026 – 22 October 2026) |
| Views total | 181 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 18 Nov 2026, 04:43 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.
What this channel posts
- Photos
- 121
- Links
- 4
Lifetime counters from Telegram’s own channel header, read 18 November 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.
Reaction mix
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😢 | 1 | 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 3 of the 40 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 40 most recent posts we hold, published 23 June 2026 to 22 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.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 1 post held from the last 30 days (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).
停车场监控、实时定位 😎😎😎 抓车抓人 比定位更加准确 提供车牌报单,车刚进场或者已经在场内,就给位置 可预约未来10天内出实时 空不收 由于停车场协议原因,极个别添加不进去,极个别没有车辆进场图片
警务通人脸点射😎😎😎 独家线 不定时秒 包精准 包核验 已打假部分五头人脸 包核验 可带备注出 默认过核验算单 独家线 一个不准赔十倍 警务通五头😎😎😎 只需要一张照片 不看备注不接指定 只要一张照片 出五头 出五头 出五头 过90相似度以上包括90算单 过90不扯皮
原图司法 😎😎😎😎 还有车 今天回
白月光业务频道 pinned «每日最新稳定可交付业务及价格 需要什么自主查看后联系我们下单 尽量减少无效沟通 模版没有的就代表全网没开 不用继续问 只要开的业务都会更新在模版频道 其次不光要对比价格还看看回单真实度以及是否稳定 以免被骗或伤下面代理 希望在查档的道路上一起成长 共同进步 祝所有客户2026年龙马精神 财源广进💰 个人信息类目 小 关 联 个人户籍 全家户籍 婚姻记录 学籍学历 医保记录 …»
降价 移动名字 14u 移动生日 14u 破解移百 28u 百分百35u
重磅消息全网首发❗️❗️❗️ 破解移百 全网唯一 移动机主名字 ❤️❤️❤️ 移动机主前6后4 ❤️❤️❤️ 破解移百❤️❤️❤️脱库回名字以及身份证号前6后4 移动现任机主百分百 ❤️❤️❤️ 专吃外面出不来的烂菜/垃圾菜 全部瞬秒通杀
三网通话记录开 一月 ❤️❤️❤️ 三月 ❤️❤️❤️ 六月 ❤️❤️❤️ 一年 ❤️❤️❤️❤️ 两年 ❤️❤️❤️❤️ 移动联通电信 三大运营商直出 无遗漏 当天隔天出
每日最新稳定可交付业务及价格 需要什么自主查看后联系我们下单 尽量减少无效沟通 模版没有的就代表全网没开 不用继续问 只要开的业务都会更新在模版频道 其次不光要对比价格还看看回单真实度以及是否稳定 以免被骗或伤下面代理 希望在查档的道路上一起成长 共同进步 祝所有客户2026年龙马精神 财源广进💰 个人信息类目 小 关 联 个人户籍 全家户籍 婚姻记录 学籍学历 医保记录 医疗记录 名下资产 大数据征信 名下手机号 个人名下卡 个人名下房 个人所得税 强登12306 人行征信报告 房屋抵押状态 法院诉讼+判决 名下护照+出入境 公司信息类目 公司档案 公司发票 营业执照 公司名下卡 公户银行流水 公司名下卡余额 车辆信息类目 车辆信息 …
源头警务通人脸识别 😙😚 提供照片+名字:对上默认出 提供照片+名字+地区:对上一条默认出 提供照片+名字+地区+年龄:对上一条默认出 敏感收费不给单 图片回单基本当天最晚隔天 有备注不对可以不出 不出不收费 ⚠️美颜 照片不清晰 可能会识别错误 出单不扯皮 接受了报
历史购物记录 ❤️❤️ 提供手机号出各大电商购物记录 买过什么 给谁买过什么,可做情况分析 还有关联地址都会有 注意是历史记录 2019年到2023年 在线秒
刑侦地址 ❤️❤️ 提供证件号码或手机号出现居住地址 户籍地址 活动地址 公安登记联系方式 名下个人关联所有电话 社会背景人员分类 证件照片 家庭关联人员 出工作单位 名下微信号 名下支付宝账号等等 包真不包漏
Showing the 12 most recent of 40 posts we hold for @baiyueguangyewu. 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.
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.
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 16 November 2026 — this entry's latest reading, not the date you are reading this.
“白月光业务频道” (@baiyueguangyewu), 18,707 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/baiyueguangyewu.
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.