Telegram RegisterThe public register of Telegram
Telegram profile photo for 白月光业务频道

Channel

白月光业务频道

@baiyueguangyewu

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

152subscribers

+26 since we began measuring on 8 September 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003775605109
TypeChannel
Username@baiyueguangyewu
CreatedBetween 1 February 2026 and 23 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 September 2026
Last confirmed live25 September 2026
Measurements held4
Confirmed unchanged1 time, most recently 25 September 2026
On Telegramt.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 why it has no browse page of its own yet.

Growth

1261521398 September 2026 — 126 subscribers9 September 2026 — 126 subscribers11 September 2026 — 133 subscribers25 September 2026 — 152 subscribers8 September 202625 September 2026
4 measurements spanning 17 days, net +26. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 122–156 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Sept 2026, 10:00152+19
11 Sept 2026, 03:59133+7
9 Sept 2026, 18:23126no change
8 Sept 2026, 17:17126first reading

Engagement

20 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 1 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
52.0%
avg views ÷ 152 subscribers
Avg views / post
79.0
2 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
2
of 20 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 September 2026
Posts held20 (23 June 2026 – 7 September 2026)
Views total158
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Sept 2026, 18:23 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.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😢1100.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 2 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 1 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 23 June 2026 to 7 September 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

7 Sept 2026, 07:34 UTC62 viewsread 9 September 2026

微信2件套 😎😎😎 纯公网,现在条子在岗,发了就出

2 Sept 2026, 03:09 UTC96 viewsread 9 September 2026
Photo

司法原图 最快当天回单💯 价格:❤️❤️❤️ 提供资料:银行卡 查询结果:出默认最新结果 不要复查 批量可来、质量单来 来质量单 批量质量来 不和翻车比价 稳 才是王道 回单时间:隔天回单

28 Aug 2026, 08:18 UTC178 viewsread 9 September 2026

破解电百 ‼️❤️❤️ 空收 给名字生日位 破解电百 ‼️❤️❤️ 空收 给名字生日位 破解电百 ‼️❤️❤️ 空收 给名字生日位 破解电百 ‼️❤️❤️ 空收 给名字生日位

24 Aug 2026, 03:03 UTC316 viewsread 9 September 2026

机主1U 秒 法人2U 秒 卡反2U秒 剩菜卡反15U 工商全系15U 中国全系15U 破解支百5U 真支百12U 当天回 电百12U 联机7U 文全12U 补齐10 假地址4U 邮政快递5U 批量预留1U 单头全户15U 公司名下卡 45u 三合一公网名下卡25U

21 Aug 2026, 12:48 UTC174 views1 reactionsread 9 September 2026
Photo

高德出行记录 报单提供名字身份证手机号大头 录屏回单:所有去过地址 打车记录 机票记录 订酒店 酒店记录 旅游记录+时间 导航记录 注:登陆上号就收费 没注册不收 一手源头出单 有量有价 ❤️❤️❤️❤️

😢1

19 Aug 2026, 10:31 UTC121 viewsread 9 September 2026

中国银行柜台流水 一月100u 三月150u 六月200u 一年300u 两年400u 三年450u 开卡至今550u 保底十年 公户➕30u 批量谈价 柜台无遗漏!

17 Aug 2026, 06:07 UTC123 viewsread 9 September 2026
Photo

一页大档 ❤️❤️ 提供车牌 默认蓝牌,绿牌 黄牌货车,摩托车备注好 当隔回单 ⚠️条子出单空收给图

12 Aug 2026, 08:52 UTC183 viewsread 9 September 2026
Photo

公网名下卡 三合一版本 ❤️❤️❤️ 稳定当天隔天回单 保证不堵车 可以备注一张可以不出/可以排除已知卡 带名下公司 名下etc车辆 保真不保漏 同行代理来拿优势

10 Aug 2026, 03:09 UTC123 viewsread 9 September 2026

机主1U 秒 法人2U 秒 卡反2U秒 剩菜卡反15U 工商全系20U 中国全系20U 破解支百5U 真支百14U 当天回 电百12U 联机7U 文全12U 补齐10 假地址4U 邮政快递5U 批量预留1U 单头全户15U 公司名下卡 45u 三合一公网名下卡30U

4 Aug 2026, 05:25 UTC139 viewsread 9 September 2026
Photo

公网名下卡 三合一版本 ❤️❤️❤️ 稳定当天隔天回单 保证不堵车 可以备注一张可以不出/可以排除已知卡 带名下公司 名下etc车辆 保真不保漏 同行代理来拿优势

30 Jul 2026, 07:31 UTC125 viewsread 9 September 2026

京东三个月内所有地址 ❤️❤️ (快递外卖一体)带单号或单号反手机号地址

23 Jul 2026, 06:23 UTC166 viewsread 9 September 2026
Photo

公网名下卡 三合一版本 ❤️❤️❤️ 稳定当天隔天回单 保证不堵车 可以备注一张可以不出/可以排除已知卡 带名下公司 名下etc车辆 保真不保漏 同行代理来拿优势

Showing the 12 most recent of 20 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 25 September 2026 — this entry's latest reading, not the date you are reading this.

“白月光业务频道” (@baiyueguangyewu), 152 subscribers as measured 25 September 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.