Channel
@mudess2362
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
2,482subscribers
-1,966 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002474109494 |
|---|---|
| Type | Channel |
| Username | @mudess2362 |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 26 September 2026 |
| On Telegram | t.me/mudess2362 |
Other / unclassifiable — 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 15 September 2026 and assigned it the closest of 31 fixed categories, at 86% 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 |
|---|---|---|
| 26 Sept 2026, 10:42 | 2,482 | -102 |
| 17 Sept 2026, 14:20 | 2,584 | -70 |
| 13 Sept 2026, 15:18 | 2,654 | -475 |
| 9 Sept 2026, 15:00 | 3,129 | -1,480 |
| 4 Sept 2026, 16:00 | 4,609 | -117 |
| 31 Aug 2026, 17:34 | 4,726 | +6 |
| 29 Aug 2026, 00:54 | 4,720 | +5 |
| 26 Aug 2026, 07:54 | 4,715 | -124 |
| 23 Aug 2026, 05:35 | 4,839 | -678 |
| 19 Aug 2026, 06:53 | 5,517 | +515 |
| 16 Aug 2026, 17:27 | 5,002 | +174 |
| 13 Aug 2026, 06:49 | 4,828 | -193 |
| 9 Aug 2026, 21:12 | 5,021 | +562 |
| 6 Aug 2026, 21:54 | 4,459 | +11 |
| 6 Aug 2026, 20:45 | 4,448 | no change |
| 6 Aug 2026, 20:34 | 4,448 | first reading |
28 posts held, back to 4 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 9 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 28 posts for this entry, the most recent from 12 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 4 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.
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 1 of the 28 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 28 most recent posts we hold, published 4 August 2026 to 12 August 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.
广州高颜值区 如发现颜值低，报告假，服务态度差，货不对版，请在评论区留言反馈，切记任何定金不要去超过100块，不了解的老师不要去约夜课，切记！切记！ 中转其他资源榜 广州资源榜 https://t.me/miuort 广州视频榜 https://t.me/puoeuzk 广州高价榜 800到900以上 https://t.me/mdhtuzoso 广州低价榜 400到800 https://t.me/HYHgut
广州高颜值区 如发现颜值低，报告假，服务态度差，货不对版，请在评论区留言反馈，切记任何定金不要去超过100块，不了解的老师不要去约夜课，切记！切记！ 中转其他资源榜 广州资源榜 https://t.me/miuort 广州视频榜 https://t.me/puoeuzk 广州高价榜 800到900以上 https://t.me/mdhtuzoso 广州低价榜 400到800 https://t.me/HYHgut
广州高颜值榜 pinned a photo
💐💐💐开奖了💐💐💐 元宝口令红包优惠券，兑奖联系元宝 @bao1236666 开奖了! 本期总参与人数: 3477 1- 未被观测的粒子 获得:38.8口令红包 2- 湿透了ye 获得:100优惠券 3- 大碴子味儿 获得:100优惠券 4- 在曼谷的春 获得:100优惠券 5- 饼干 获得:100优惠券 6- 花开亦茉莉 获得:100优惠券 7- 毛利小五郎 获得:200pp优惠券 8- 平仄 获得:200pp优惠券 9- 配置卡洛斯 获得:200pp优惠券 10- 普通用户 获得:200pp优惠券 11- 无名之辈 获得:200pp优惠券 谨祝中奖用户大吉大利万事顺意
广州高颜值区 如发现颜值低，报告假，服务态度差，货不对版，请在评论区留言反馈，切记任何定金不要去超过100块，不了解的老师不要去约夜课，切记！切记！ 中转其他资源榜 广州资源榜 https://t.me/miuort 广州视频榜 https://t.me/puoeuzk 广州高价榜 800到900以上 https://t.me/mdhtuzoso 广州低价榜 400到800 https://t.me/HYHgut
🎰 暖暖口令优惠券，兑奖联系暧暖 @nuan66688 📮 抽奖条件: 🎫 加入-广州资源榜 🎫 加入-广州高颜值榜 🎫 加入-广州低价榜 🎫 加入-广州紫瑶宫🆑 🎫 加入-广州紫瑶宫推广群 🎫 加入-广州天河暖暖 🎁 奖品内容: 28口令红包 × 1 100优惠券 × 5 200pp优惠券 × 5 💡 活动说明: 暖暖口令优惠券，兑奖联系暧暖 @nuan66688 📅 开奖日期:(UTC+8) 2026年08月11日 17时24分08秒
🎰 小鱼菲菲双飞口令红包优惠券，兑奖联系小鱼菲菲双飞兑奖 @feifeibei 📮 抽奖条件: 🎫 加入-广州资源榜 🎫 加入-广州高颜值榜 🎫 加入-广州潮流一线 🎫 加入-广州潮流推广群 🎫 加入-小鱼菲菲的后花园💕 🎫 加入-广州抽奖导航公示 🎁 奖品内容: 18.8奶茶红包 × 1 200通用优惠券 × 6 💡 活动说明: 小鱼菲菲双飞口令红包优惠券，兑奖联系小鱼菲菲双飞兑奖 @feifeibei 📅 开奖日期:(UTC+8) 2026年08月11日 17时17分26秒
广州高颜值榜 pinned a photo
🎰 小玉口令红包优惠券，兑奖联系小玉 @ayuyu520 📮 抽奖条件: 🎫 加入-广州资源榜 🎫 加入-广州高颜值榜 🎫 加入-广州紫瑶宫🆑 🎫 加入-广州紫瑶宫推广群 🎫 加入-广州潮流一线 🎫 加入-小玉的窝窝❤️ 🎁 奖品内容: 18.8奶茶红包 × 1 100优惠券 × 5 200pp优惠券 × 5 💡 活动说明: 小玉口令红包优惠券，兑奖联系小玉 @ayuyu520 📅 开奖日期:(UTC+8) 2026年08月11日 15时59分12秒
广州高颜值区 如发现颜值低，报告假，服务态度差，货不对版，请在评论区留言反馈，切记任何定金不要去超过100块，不了解的老师不要去约夜课，切记！切记！ 中转其他资源榜 广州资源榜 https://t.me/miuort 广州视频榜 https://t.me/puoeuzk 广州高价榜 800到900以上 https://t.me/mdhtuzoso 广州低价榜 400到800 https://t.me/HYHgut
广州潮流广告群 https://t.me/GHKLROT 广州潮流轮播群 https://t.me/RGTREY 广州紫瑶宫广告群 https://t.me/GHWYJM 广州紫瑶宫轮播群 https://t.me/YMUHKR
广州潮流广告群 https://t.me/GHKLROT 广州潮流轮播群 https://t.me/RGTREY 广州紫瑶宫广告群 https://t.me/GHWYJM 广州紫瑶宫轮播群 https://t.me/YMUHKR
Showing the 12 most recent of 28 posts we hold for @mudess2362. 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.
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 10 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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“广州备用榜” (@mudess2362), 2,482 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/mudess2362.
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.