Channel
@huanxi2221
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
5,615subscribers
+3,311 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002675221525 |
|---|---|
| Type | Channel |
| Username | @huanxi2221 |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/huanxi2221 |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 31% 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 |
|---|---|---|
| 16 Sept 2026, 19:16 | 5,615 | -7 |
| 12 Sept 2026, 22:37 | 5,622 | +3 |
| 9 Sept 2026, 07:17 | 5,619 | -1 |
| 4 Sept 2026, 08:20 | 5,620 | +1 |
| 1 Sept 2026, 03:07 | 5,619 | -1 |
| 29 Aug 2026, 02:35 | 5,620 | +8 |
| 26 Aug 2026, 06:02 | 5,612 | +14 |
| 23 Aug 2026, 09:26 | 5,598 | -417 |
| 19 Aug 2026, 16:42 | 6,015 | +8 |
| 16 Aug 2026, 16:06 | 6,007 | +2,632 |
| 12 Aug 2026, 23:34 | 3,375 | +1,071 |
| 12 Aug 2026, 03:00 | 2,304 | no change |
| 12 Aug 2026, 02:48 | 2,304 | first reading |
18 posts held, back to 7 July 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 18 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
22 reactions across 10 posts, in 4 distinct kinds. The most used accounts for 86.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 19 | 86.4% | |
| 👀 | 1 | 4.55% | |
| 🔥 | 1 | 4.55% | |
| 🥰 | 1 | 4.55% |
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 18 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 22 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 7 July 2026 to 10 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.
🎟️ 抽奖标题：红粉青楼×龟男×夜生活重磅联名，携手优质老师七夕福利大放送！ 📪抽奖说明：中奖者机器人会发送中奖信息 开奖后48小时内兑换，逾期作废 🎫 参与条件: 🎫 必须有用户名 🎫 加入-红粉青楼 🎫 加入-青楼精选 🎫 加入-青楼简报 🎫 加入-深圳别做龟男3.0 🎫 加入-龟不语2.0 🎫 加入-大学毕业生林雪 🎫 加入-E奶欢喜朋友圈⭕ 开课 🎫 加入-民乐 程澄🎀（野生 神木丽) 🎫 加入-困困的小🛏 🎁 奖品内容: 💰️ 500 现金🧧，中奖联系 @kghat × 1 💰️ 500 现金🧧，中奖联系 @linxueii × 1 💰️ 500 现金🧧，中奖联系 @kkqq12121 × 1 💰️ 500 现金🧧，中奖联系 @huanxi22212 × 1 📅 开奖时间：2026-08-14 20:00自动开奖 👉 参与抽奖链接: https://t.me/XGCJ_bot?start=join-
开课喔 有教室 不外出
❤2👀1
Sticker, posted without a caption
❤1
我要的是偏爱
❤5
派大星出击报告（ https://t.me/+2Kbp7dDZd904ZDBk ） 验证留名：垂顺 验证时间：2026.8.6 老师花名：#欢喜 城市坐标：#深圳 #福田 上课花费：900p 颜值身材：大眼睛可爱圆脸，大灯超晃眼 服务内容：课表都有，外加很多细节自行体会 出击体验：早早就关注老师了，碰巧今天有空老师又在，果断约好cj；科室位置好找方便，要说一进门先看到的是大眼睛那是骗人的，肯定是先看到明晃晃的大灯哈哈，一出声整个人都酥了，老师声音也好好听；更衣洗浴，不得不说老师是微胖界的一枚天花板，身材特别喜欢，主动让你摸摸也会撩，洗完迫不及待躺着开始。老师的技术也没得说，口活一流，舌头也超软，不一会就忍不住想进去了，但是今天状态不太好，老师也没催，耐心弄硬后带帽直入。下面水也好多，123就被老师秒了哈哈，完事也不催，躺下来又跟老师聊了许久。总而言之是一次满意的cj，聊得过程很开心，对了老师也很有品味用的tempo纸巾哈哈，广东…
给我们一次相会 我还你晴空万里
❤3
800群出击报告（ https://t.me/CAT800fx ） 工兵留名:企好 出击时间：8 月 5 日 老师花名：#欢喜 地理位置：#福田区#新洲 上课支出：900p 颜值身材：丰满可爱型，胸大屁股大 服务内容：课表内容 出击体验：聊的比较开心，服务过程舒适，有女朋友的感觉，恋爱的感觉 优点缺点：皮肤很白，性格很好很温柔 联系方式： @huanxi22212 推荐程度：/满分10.0分 群收录评级： （提交报告需要提供相关资料，如聊天记录，付款记录等，记录不会公开） 1、尽量写的客观一些，过于夸张吹捧或者字数太长会拒收； 2、免责声明：以上报告内容为当事人主观感受，并不构成出击建议；出击有风险，来都来了需谨慎。
❤2
你主动点 我再懂事点 我们的故事不就开始了吗
今天开课，宝宝们，福田新洲
Channel name was changed to «E奶欢喜朋友圈⭕ 开课»
拜拜👋🏻 下次见
Channel name was changed to «E奶欢喜朋友圈⭕ 休息»
Showing the 12 most recent of 18 posts we hold for @huanxi2221. 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.
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 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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“E奶欢喜朋友圈⭕ 休息” (@huanxi2221), 5,615 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/huanxi2221.
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.