💎消耗70%返还 报名时间:收到此活动即可报名,报名人数:50人❗️ 活动时间:香港时间2026年8月13日5:00-7:00 发奖时间:香港时间2026年8月13日7:00 活动内容:活动期间,聊指定角色卡达成目标消耗10000💎(上限❗️),即完成可返还70%的🟡7000 参与活动的5个必要条件 1、仅💎可参加,目标消耗10000内先用💎,结束后先用🟡 2、报名方式:在活动消息发出后,点击小程序、TG直聊即可参加❗️ 3、聊指定角色卡:所有公开的角色卡 4、聊天模型:流光、魅惑、千幻 5、领取奖励:自动发放到账户(TG直聊查询余额、TG小程序-我的-充值消费-充值记录) ⚠️看到推送的活动消息、报名入口,都可报名参加❗️ 本次活动会产生1名幸运用户,可以获得80%返还❗️❗️ 🔗通过小程序Bot报名👈 🔗通过TG直聊Bot报名👈

Channel
幻梦AI官方福利频道|记住@huanmeng_ai永久域名|官网huanmeng.ai
@huanmeng_ai
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
162,862subscribers
-164 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
Register entry
| Telegram ID | -1002174362633 |
|---|---|
| Type | Channel |
| Username | @huanmeng_ai |
| Description | 官方福利频道,不定期发布最新福利活动。 记住唯一官方域名 @huanmeng_ai,防走失 官网地址:huanmeng.ai 小程序: @FancyAIChatBot TG直聊: @HMChatAIBot 角色世界: @juseshijiequn 官方群: @HMAIMate 客服妹: @ai_x01_bot |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/huanmeng_ai |
Topic
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 58% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 09:13 | 162,862 | -17 |
| 11 Aug 2026, 11:03 | 162,879 | -56 |
| 10 Aug 2026, 10:32 | 162,935 | -71 |
| 9 Aug 2026, 08:50 | 163,006 | -31 |
| 8 Aug 2026, 06:45 | 163,037 | +11 |
| 7 Aug 2026, 15:16 | 163,026 | first reading |
Engagement
57 posts held, back to 5 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 25 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 0.434%
- avg views ÷ 162,862 subscribers
- Avg views / post
- 708
- 56 posts measured
- Reaction rate
- 0.239%
- reactions ÷ views · ER floor
- Posts in window
- 57
- of 57 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. It is computed over the 31 of 56 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 12 August 2026 |
|---|---|
| Posts held | 57 (5 August 2026 – 12 August 2026) |
| Views total | 39,621 |
| Reactions total | 54 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 21:30 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
- ≈1
- Links
- ≈1,650
Lifetime counters from Telegram’s own channel header, read 12 August 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.
Reaction mix
54 reactions across 29 posts, in 5 distinct kinds. The most used accounts for 68.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 37 | 68.5% | |
| ❤ | 13 | 24.1% | |
| 🥰 | 2 | 3.70% | |
| 🎉 | 1 | 1.85% | |
| 👏 | 1 | 1.85% |
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 31 of the 57 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 54reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 57 most recent posts we hold, published 5 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.
Recent posts
🎉🎉活动提前预热: 迎接夏日,重量级消耗10000💎70%返7000🟡活动来了❗️❗️ 所有公开的角色卡聊天消耗💎,都会记录到目标消耗的积分哦❗️❗️ ⚠️关注福利频道 @huanmeng_ai 消耗活动会第一时间发布(活动开启时,福利频道会发出活动信息并带有活动入口) 说明: 1、本次活动时间:香港时间2026年8月13日5:00-7:00,限时2小时❗️ 2、奖励发放时间:香港时间8月13日7:00 3、领取奖励:自动发放到账户(TG直聊查询余额、TG小程序-我的-充值消费-充值记录)
👍1
🎉🎉恭喜以下用户完成香港时间2026年08月12日19:30-2026年08月13日04:00消耗💎返还🟡活动,奖励名单:(不分先后顺序) 1. 刘亦童,获得7000🟡 2. Jack Tony,获得8000🟡(大奖) 3. 泠 宸兮,获得7000🟡 4. 彳 亍,获得7000🟡 5. 雨 夜,获得7000🟡 6. 洛风,获得7000🟡 7. Ssss Ffff,获得7000🟡 8. 曾偉,获得7000🟡 9. 家慶,获得7000🟡 10. Z,获得7000🟡 11. 大饼,获得7000🟡 12. 我,获得7000🟡 13. 周予,获得7000🟡 14. 拾肆 贰,获得7000🟡 15. 徐盛锋,获得7000🟡 16. 吉米,获得7000🟡 17. 雷鈞,获得7000🟡 18. 沈凪,获得7000🟡 19. 白洛,获得7000🟡 20. 辰,获得7000🟡 21. 000 000,获得7000🟡 22. nsa ks,获得70…
👍2
热度冲榜赛 · 榜单揭晓 🎉🎉🎉 感谢各位创作者的热情参与,本次「热度冲榜赛」已圆满结束!😎😎 经过最终热度统计,获奖名单如下: ━━━━━━━━━━━━━━━ 🏆 热度榜 TOP 10 ━━━━━━━━━━━━━━━ 🥇 第一名:蔷薇【全能型主】|89515🟡 🥈 第二名:炎焱|27875🟡 🥉 第三名:张展|18340🟡 🏅 第四名:苏源|17115🟡 🏅 第五名:Cordia P|16349🟡 🏅 第六名:金|13286🟡 🏅 第七名:黄丰|11511🟡 🏅 第八名:海|11325🟡 🏅 第九名:fggg f t f r|4924🟡 🏅 第十名:张兆麟 |4668🟡 ━━━━━━━━━━━━━━━ 🤩 其他上榜作者 ━━━━━━━━━━━━━━━ Benjamin 4616🟡,李筱 4490🟡,雪 4374🟡,北崮山 4242🟡,guge 4178🟡,Bokun 4084🟡,高 3630🟡,yeee 3414🟡…
🥰1
💎消耗70%返还 报名时间:收到此活动即可报名,报名人数:100人❗️ 活动时间:香港时间2026年8月12日19:30-7月22日04:00 发奖时间:香港时间2026年8月13日04:00 活动内容:活动期间,聊指定角色卡达成目标消耗10000💎(上限❗️),即完成可返还70%的🟡7000 参与活动的5个必要条件 1、仅💎可参加,目标消耗10000内先用💎,结束后先用🟡 2、报名方式:在活动消息发出后,点击小程序、TG直聊即可参加❗️ 3、聊指定角色卡:所有公开的角色卡 4、聊天模型:流光、魅惑、千幻 5、领取奖励:自动发放到账户(TG直聊查询余额、TG小程序-我的-充值消费-充值记录) ⚠️看到推送的活动消息、报名入口,都可报名参加❗️ 本次活动会产生1名幸运用户,可以获得80%返还❗️❗️ 🔗通过小程序Bot报名👈 🔗通过TG直聊Bot报名👈
👍4
🎉🎉活动提前预热: 迎接夏日,重量级消耗10000💎70%返7000🟡活动来了❗️❗️ 所有公开的角色卡聊天消耗💎,都会记录到目标消耗的积分哦❗️❗️ ⚠️关注福利频道 @huanmeng_ai 消耗活动会第一时间发布(活动开启时,福利频道会发出活动信息并带有活动入口) 说明: 1、本次活动时间:香港时间2026年8月12日19:30-7月22日04:00,限时8.5个小时❗️ 2、奖励发放时间:香港时间8月13日04:00 3、领取奖励:自动发放到账户(TG直聊查询余额、TG小程序-我的-充值消费-充值记录)
👍1
🎉🎉恭喜以下用户完成香港时间2026年08月12日11:00-2026年08月12日14:00消耗💎返还🟡活动,奖励名单:(不分先后顺序) 1. 彳 亍,获得7000🟡 2. 好哥哥,获得7000🟡 3. 草莓,获得7000🟡 4. 吉米,获得7000🟡 5. 离恋前朝,获得7000🟡 6. 000 000,获得7000🟡 7. 基拉的神,获得7000🟡 8. 檸樂,获得8000🟡(大奖) 9. yxz,获得7000🟡 10. 恩玥,获得7000🟡 11. 段誉--,获得7000🟡 12. 雪,获得7000🟡 13. 楠 辞,获得7000🟡 14. 小迪,获得7000🟡 15. vid Da,获得7000🟡 16. hu hu,获得7000🟡 17. 宋少,获得7000🟡 18. 主人,获得7000🟡
👍4
💎消耗70%返还 报名时间:收到此活动即可报名,报名人数:50人❗️ 活动时间:香港时间2026年8月12日11:00-14:00 发奖时间:香港时间2026年8月12日14:00 活动内容:活动期间,聊指定角色卡达成目标消耗10000💎(上限❗️),即完成可返还70%的🟡7000 参与活动的5个必要条件 1、仅💎可参加,目标消耗10000内先用💎,结束后先用🟡 2、报名方式:在活动消息发出后,点击小程序、TG直聊即可参加❗️ 3、聊指定角色卡:所有公开的角色卡 4、聊天模型:流光、魅惑、千幻 5、领取奖励:自动发放到账户(TG直聊查询余额、TG小程序-我的-充值消费-充值记录) ⚠️看到推送的活动消息、报名入口,都可报名参加❗️ 本次活动会产生1名幸运用户,可以获得80%返还❗️❗️ 🔗通过小程序Bot报名👈 🔗通过TG直聊Bot报名👈
👍1
🎉🎉活动提前预热: 迎接夏日,重量级消耗10000💎70%返7000🟡活动来了❗️❗️ 所有公开的角色卡聊天消耗💎,都会记录到目标消耗的积分哦❗️❗️ ⚠️关注福利频道 @huanmeng_ai 消耗活动会第一时间发布(活动开启时,福利频道会发出活动信息并带有活动入口) 说明: 1、本次活动时间:香港时间2026年8月12日11:00-14:00,限时3小时❗️ 2、奖励发放时间:香港时间8月12日14:00 3、领取奖励:自动发放到账户(TG直聊查询余额、TG小程序-我的-充值消费-充值记录)
👍1
🎉🎉恭喜以下用户完成香港时间2026年08月12日05:00-2026年08月12日07:00消耗💎返还🟡活动,奖励名单:(不分先后顺序) 1. 弟弟,获得7000🟡 2. 灰灰,获得8000🟡(大奖) 3. 包达铭,获得7000🟡 4. 韓雨,获得7000🟡 5. 段誉--,获得7000🟡 6. 小迪,获得7000🟡 7. 肥猪 好色,获得7000🟡 8. 十一,获得7000🟡 9. hongjian zheng,获得7000🟡
💎消耗70%返还 报名时间:收到此活动即可报名,报名人数:50人❗️ 活动时间:香港时间2026年8月12日5:00-7:00 发奖时间:香港时间2026年8月12日7:00 活动内容:活动期间,聊指定角色卡达成目标消耗10000💎(上限❗️),即完成可返还70%的🟡7000 参与活动的5个必要条件 1、仅💎可参加,目标消耗10000内先用💎,结束后先用🟡 2、报名方式:在活动消息发出后,点击小程序、TG直聊即可参加❗️ 3、聊指定角色卡:所有公开的角色卡 4、聊天模型:流光、魅惑、千幻 5、领取奖励:自动发放到账户(TG直聊查询余额、TG小程序-我的-充值消费-充值记录) ⚠️看到推送的活动消息、报名入口,都可报名参加❗️ 本次活动会产生1名幸运用户,可以获得80%返还❗️❗️ 🔗通过小程序Bot报名👈 🔗通过TG直聊Bot报名👈
🎉🎉活动提前预热: 迎接夏日,重量级消耗10000💎70%返7000🟡活动来了❗️❗️ 所有公开的角色卡聊天消耗💎,都会记录到目标消耗的积分哦❗️❗️ ⚠️关注福利频道 @huanmeng_ai 消耗活动会第一时间发布(活动开启时,福利频道会发出活动信息并带有活动入口) 说明: 1、本次活动时间:香港时间2026年8月12日5:00-7:00,限时2小时❗️ 2、奖励发放时间:香港时间8月12日7:00 3、领取奖励:自动发放到账户(TG直聊查询余额、TG小程序-我的-充值消费-充值记录)
Showing the 12 most recent of 57 posts we hold for @huanmeng_ai. 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
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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“幻梦AI官方福利频道|记住@huanmeng_ai永久域名|官网huanmeng.ai” (@huanmeng_ai), 162,862 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/huanmeng_ai.
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.