Channel
@emoxiaoaottii
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
282subscribers
+0 since we began measuring on 18 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003822503599 |
|---|---|
| Type | Channel |
| Username | @emoxiaoaottii |
| Created | Between 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 18 September 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/emoxiaoaottii |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 08:22 | 282 | no change |
| 18 Sept 2026, 07:47 | 282 | first reading |
18 posts held, back to 17 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 1 page 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 2 of 13 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 18 September 2026 |
|---|---|
| Posts held | 18 (17 August 2026 – 18 September 2026) |
| Views total | 8,447 |
| Reactions total | 4 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 18 Sept 2026, 08:22 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 18 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
10 reactions across 5 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 10 | 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 5 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 10 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 17 August 2026 to 18 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.
🎰 甜心少女✖️小桑福利活动 📮 参与条件： 🪪 必须设置用户名 🎫 加入-阿咩 🎫 加入-甜心|硅胶娃娃 🎫 加入-成都•洞友之家 🎁 奖品内容： 💰️ 88现金红包🧧 × 2 💰️ 小桑单P半价券 × 1 💰️ 甜心少女白嫖（价值468） × 1 ⚠️ 抽奖说明： ⚠️炸号，换号不予兑奖 ⚠️开奖后退出频道群组，不予兑奖 ⚠️开奖前需在 https://t.me/CDCshudonggushihui 任意帖子留有表情包点赞记录（无需刻意点赞，仅为鉴别机器人协议号恶意抽奖），否则只兑换8.8元口令红包🧧。 📅 开奖日期：(北京时间) 2026年09月21日 14时00分00秒
双人包天 24小时9k❤️🍎🌷 双人包天8小时6k🔡🔡 限6次🤌 （🔡九月限定活动🔡）
🔠活动双飞 🔠 14 p 限时1小时 （不换套）❤️ 22pp 限时 两小时 （不换套 ）🫶 有包时和包天请私信我哟🎭 哥哥需自己准备套套 和酒店房间哟 🔠不换套需准备传染病试纸🔠 （🈲桩机 🈲吃药 🈲偷拍）
排20号的课宝宝们
家人们 我18号之后再开啦 中间可以月我闺蜜哟宝宝们
闺蜜红休了
家人们 想约闺蜜的火速哟 差不多明天要来姨妈了
闺蜜今天有位 市区
闺蜜今天有位
Video, posted without a caption
❤2
闺蜜今天还有空噢😘
红了🥹
Showing the 12 most recent of 18 posts we hold for @emoxiaoaottii. 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 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“阿咩” (@emoxiaoaottii), 282 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/emoxiaoaottii.
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.