抖音牛户正常 @LH8830
Signed 路虎

Channel
@AW520000000
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
23,369subscribers
-15,923 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001793329907 |
|---|---|
| Type | Channel |
| Username | @AW520000000 |
| Created | Between 1 January 2022 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 33 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/AW520000000 |
Ecommerce storefront — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 42% 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 |
|---|---|---|
| 19 Sept 2026, 17:01 | 23,369 | -1,076 |
| 17 Sept 2026, 04:40 | 24,445 | -603 |
| 15 Sept 2026, 04:01 | 25,048 | -3,222 |
| 13 Sept 2026, 11:18 | 28,270 | -1,355 |
| 11 Sept 2026, 15:40 | 29,625 | -1,364 |
| 8 Sept 2026, 21:57 | 30,989 | -1,771 |
| 5 Sept 2026, 17:57 | 32,760 | -1,065 |
| 3 Sept 2026, 15:20 | 33,825 | -437 |
| 2 Sept 2026, 11:26 | 34,262 | -467 |
| 1 Sept 2026, 09:44 | 34,729 | -894 |
| 31 Aug 2026, 11:03 | 35,623 | -1,784 |
| 30 Aug 2026, 07:34 | 37,407 | -636 |
| 29 Aug 2026, 04:34 | 38,043 | -164 |
| 28 Aug 2026, 06:34 | 38,207 | -77 |
| 27 Aug 2026, 08:14 | 38,284 | -29 |
| 26 Aug 2026, 06:42 | 38,313 | -43 |
| 25 Aug 2026, 05:53 | 38,356 | -49 |
| 24 Aug 2026, 02:43 | 38,405 | -72 |
| 22 Aug 2026, 10:08 | 38,477 | -65 |
| 21 Aug 2026, 02:34 | 38,542 | first reading |
945 posts held, back to 7 August 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 65 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. It is computed over the 5 of 520 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 8 September 2026 |
|---|---|
| Posts held | 945 (7 August 2026 – 8 September 2026) |
| Views total | 15,593 |
| Reactions total | 2 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Sept 2026, 19:34 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.
Measured directly from 2 videos 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.
6 reactions across 5 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 6 | 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 8 of the 945 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 6 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 945 most recent posts we hold, published 7 August 2026 to 8 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.
抖音牛户正常 @LH8830
Signed 路虎
分期定制4字ID 资金周转不用愁 属于自己独一无二的4字面子ID 4字ID 😁实力象征 @ntnt
Signed 风花男童
支付宝扫码单笔10000连刷 首次无视人脸必查!!!✈️ @MQMSJ86
Signed 文少(只做无视)
🀄️中国Ai 独家秘方 首次不出直接赔 地方银行 带取款 杀至限额 @Di8133
Signed 迪(专注大额Ai) 风花
📢全民k歌 星巴克 肯德基 必胜客 哔哩哔哩 👍一手话费电费贴户 引导小天才/杀手 链接付 24小时营业 ✈️ @CA_yozi
Signed 可乐 (没回复弹语音)24h
香港3D 任意卡 1码5000-10000 农业也杀 @SayHanxin
Signed 风花韩信
支付宝扫码单笔10000连刷 首次无视人脸必查!!!✈️ @MQMSJ86
Signed 文少(只做无视)
支付宝设置黑科技连刷支持花呗信用卡 正常 @FHXY07
Signed 风花跑街的(戒赌第一天)
目前丝滑在开 大额缴费 电力 物业费 超梦✈️ @V520
Signed 超梦 @v520
分期定制4字ID 资金周转不用愁 属于自己独一无二的4字面子ID 4字ID 😁实力象征 @ntnt
Signed 风花男童
🀄️中国Ai 独家秘方 首次不出直接赔 地方银行 带取款 杀至限额 @Di8133
Signed 迪(专注大额Ai) 风花
香港3D 任意卡 1码5000-10000 农业也杀 @SayHanxin
Signed 风花韩信
Showing the 12 most recent of 945 posts we hold for @AW520000000. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 2 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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“风花雪月业务通知频道-关注置顶” (@AW520000000), 23,369 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/AW520000000.
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.