一手ai: 1️⃣全球ai带取密24小时正常营业 2️⃣农业、邮政免密2万~20万 3️⃣地方农信、农商1-3码全额 4️⃣独家、任意3D、数字、云扣、 聚分期、美银宝一切渠道zc 点位山顶(可对接)永不罚站 24小时营业✈️@Cmq5588
Signed 沐秋(一手ai为爱卡扣)

Channel
@AW520000000
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
18,097subscribers
-21,195 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 |
| Description | 风花雪月负责人安稳 真名:朱天赐 身份证:420984200310053054 安稳老婆:王绮文 身份证:42098420041116444X |
| Created | Between 1 January 2022 and 31 March 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 60 |
| Confirmed unchanged | 1 time, most recently 6 November 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Nov 2026, 07:38 | 18,097 | -19 |
| 5 Nov 2026, 08:38 | 18,116 | -29 |
| 4 Nov 2026, 07:14 | 18,145 | -21 |
| 3 Nov 2026, 10:31 | 18,166 | -22 |
| 2 Nov 2026, 10:24 | 18,188 | -26 |
| 1 Nov 2026, 11:35 | 18,214 | -68 |
| 31 Oct 2026, 14:18 | 18,282 | -92 |
| 30 Oct 2026, 10:46 | 18,374 | -128 |
| 29 Oct 2026, 07:49 | 18,502 | -53 |
| 28 Oct 2026, 04:48 | 18,555 | -41 |
| 27 Oct 2026, 07:51 | 18,596 | -135 |
| 26 Oct 2026, 04:29 | 18,731 | -60 |
| 25 Oct 2026, 04:51 | 18,791 | -44 |
| 24 Oct 2026, 02:17 | 18,835 | -41 |
| 23 Oct 2026, 03:06 | 18,876 | -51 |
| 21 Oct 2026, 23:39 | 18,927 | -59 |
| 20 Oct 2026, 17:57 | 18,986 | -25 |
| 19 Oct 2026, 18:57 | 19,011 | -50 |
| 18 Oct 2026, 17:57 | 19,061 | -41 |
| 17 Oct 2026, 20:09 | 19,102 | first reading |
1,133 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 77 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 6 November 2026 |
|---|---|
| Posts held | 1,133 (7 August 2026 – 6 November 2026) |
| Views total | 2,369 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Nov 2026, 15:51 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 6 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 3 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.
9 reactions across 8 posts, in 2 distinct kinds. The most used accounts for 55.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 5 | 55.6% | |
| 👎 | 4 | 44.4% |
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 11 of the 1,000 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 9 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 9 August 2026 to 6 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: 0 of 120 posts 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).
一手ai: 1️⃣全球ai带取密24小时正常营业 2️⃣农业、邮政免密2万~20万 3️⃣地方农信、农商1-3码全额 4️⃣独家、任意3D、数字、云扣、 聚分期、美银宝一切渠道zc 点位山顶(可对接)永不罚站 24小时营业✈️@Cmq5588
Signed 沐秋(一手ai为爱卡扣)
邮政银行ai免密3码1-100w 🀄️🀄️🀄️🀄️建设银行ai四要素取款1-100w 独家5码1.5万不用删除大行卡来 任意银行3D境外一码五千免密 数字 聚分期、云扣 美银宝zc 24小时营业✈️@Cmq5588
Signed 沐秋(一手ai为爱卡扣)
分期定制4字ID 资金周转不用愁 属于自己独一无二的4字面子ID 4字ID 😁实力象征 @ntnt
Signed 男童
邮政银行ai免密3码1-100w 🀄️🀄️🀄️🀄️建设银行ai四要素取款1-100w 独家5码1.5万不用删除大行卡来 任意银行3D境外一码五千免密 数字 聚分期、云扣 美银宝zc 24小时营业✈️@Cmq5588
Signed 沐秋(一手ai为爱卡扣)
微店1-2码10000 邮政 删除秒 @ej8888
Signed 作家(招收远控盘口)
Channel name was changed to «@ck444 @ci111 @xu000»
支付宝必过通道,控死的 改密的 远控的都来 @LH8830
Signed 路虎
💰U兑换TRX :@TTRX88_BOT 🇺🇿大量出租/收购+888号码
Signed 作家(招收远控盘口)
邮政银行ai免密3码1-100w 🀄️🀄️🀄️🀄️建设银行ai四要素取款1-100w 独家5码1.5万不用删除大行卡来 任意银行3D境外一码五千免密 数字 聚分期、云扣 美银宝zc 24小时营业✈️@Cmq5588
Signed 沐秋(一手ai为爱卡扣)
🎉 NG娱乐集团 🎉 顶级娱乐平台 · 安全便捷 · 服务成就信赖 ♠️ 秒秒28极速玩法 🏀 全球顶级体育赛事 🎰 爆分霸屏电子游戏 🎮 电竞赛事激情开战 💃 真人视讯美女互动 🎯 各类热门彩票游戏 🀄️ 各类经典棋牌游戏 🐟 千炮捕鱼爽快刺激 ✨ 更多精彩等你探索 🔥 火爆活动 · 福利不断 🔥 🍀 新用户注册最高送 8888 元彩金 🍀 电子游戏周榜奖励最高 18888 元 🍀 充值提现无忧,延迟立马补贴 诚邀代理玩家入驻 💞 【玩家首存100送28起】 💎 【流水日结模式】1块流水0.5%起,最高返佣比例高达1% 💎 【人头费宝箱】下级累计充值1000,累计充值3天,累计有效投注5000,代理即可领取100-300奖励,最高可拿1500单个 💎 【代理日俸禄】当天佣金领取10000,额外领取加赠佣金888元,最高可达5888元。 NG娱乐集团,始终坚守“相信平台的力量”! 实力见…
分期定制4字ID 资金周转不用愁 属于自己独一无二的4字面子ID 4字ID 😁实力象征 @ntnt
Signed 男童
一手ai: 1️⃣全球ai带取密24小时正常营业 2️⃣农业、邮政免密2万~20万 3️⃣地方农信、农商1-3码全额 4️⃣独家、任意3D、数字、云扣、 聚分期、美银宝一切渠道zc 点位山顶(可对接)永不罚站 24小时营业✈️@Cmq5588
Signed 沐秋(一手ai为爱卡扣)
Showing the 12 most recent of 1,133 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.
@AW520000000 named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“风花雪月负责人安稳 真名:朱天赐 身份证:420984200310053054 安稳老婆:王绮文 身份证:42098420041116444X” (@AW520000000), 18,097 subscribers as measured 6 November 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.