Telegram RegisterThe public register of Telegram
Telegram profile photo for 欧美臀露露-🐍吻

Channel

欧美臀露露-🐍吻

@nixiaai

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

1,553subscribers

+0 since we began measuring on 6 October 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002368056004
TypeChannel
Username@nixiaai
Description简简单单生活,简简单单的我。
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 October 2026
Last confirmed live6 October 2026
Measurements held2
On Telegramt.me/nixiaai

Growth

1,5536 Oct 2026, 12:48 — 1,553 subscribers6 Oct 2026, 13:22 — 1,553 subscribers6 Oct 2026, 12:486 Oct 2026, 13:22
2 measurements taken within a single day. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,551–1,555 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Oct 2026, 13:221,553no change
6 Oct 2026, 12:481,553first reading

Engagement

17 posts held, back to 14 September 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 · 30 days
139.7%
avg views ÷ 1,553 subscribers
Avg views / post
2,170
17 posts measured
Reaction rate
0.111%
reactions ÷ views · ER floor
Posts in window
17
of 17 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 11 of 17 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 October 2026
Posts held17 (14 September 2026 – 6 October 2026)
Views total36,875
Reactions total28
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Oct 2026, 13: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.

What this channel posts

Photos
16
Videos
5
Links
3

Lifetime counters from Telegram’s own channel header, read 6 October 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.

Video runtime
24s
Average length
6s

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.

Reaction mix

28 reactions across 10 posts, in 3 distinct kinds. The most used accounts for 89.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤2589.3%
🔥27.14%
👏13.57%

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 17 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 28 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 17 most recent posts we hold, published 14 September 2026 to 6 October 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

4 Oct 2026, 06:08 UTC892 views1 reactionsread 6 October 2026
Photo

画个精致的妆,只为别人可以叫我一生美人😋

❤1

3 Oct 2026, 09:51 UTC964 views4 reactionsread 6 October 2026
Forwarded from @dgcjbg888

报告模板 反馈报告 上课时间:10-3 验证留名:喜蛋 所在位置:南城 老师名称:#璐璐 @liciajie 上课价格:500 妹子年龄:27 妹子容貌:人照9分 妹子身材:腰臀比一绝 服务态度:敬业 环境设备:公寓 自由评论:老师身材不错,人照也对版,毫不犹豫交水费,浴室就开始前戏.🐍吻,而且是很投入的大蟒蛇。感受着老师的舌尖,唇齿。来到🛏️服务特别认真,口活很舒服,无齿感,而且是持久口的那种, 伴随着轻微的嗯嗯的声音,很明显是在故意诱惑,服务不偷懒,主打一个敬业。享受的差不多了,到我发挥,开始提枪上马,长驱直入,冲进老师私处,紧致包裹性非常好,轻咬住老师的耳垂,反复刺激敏感地带。时不时的还用嘴照顾一下老师的小奶头,持续输出几分钟感觉要射。赶紧换个姿势,让老师趴着后入。老师的腰臀比简直绝了,典型的细腰巨臀,屁股好大好圆,画面太美,自行脑补,后入视觉享受爆棚,一波波臀浪刺激程度更大,实在是忍不了了,快速的撞击,在强烈的多重感官…

❤2🔥2

3 Oct 2026, 07:14 UTC961 views1 reactionsread 6 October 2026
Photo

单单看脸,你永远猜不到我是梨形身材🥰🥰🥰

👏1

22 Sept 2026, 06:45 UTC≈2,530 viewsread 6 October 2026
Video

这下臀控宝宝满足了吧,上课45分钟,拍臀玩臀半小时😂😂😂

21 Sept 2026, 12:29 UTC≈2,610 views5 reactionsread 6 October 2026
Forwarded from @dgcjbg888

报告模板 反馈报告 上课时间:9.21 验证留名:Sri 所在位置:南城 老师名称:#璐璐 @liciajie 上课价格:500 妹子年龄:28 妹子容貌:8 妹子身材:9 服务态度:9 环境设备:8 自由评论:看璐璐频道的照片,有感而约。出发前跟老师说好,提前换好喜欢的包臀牛仔裤,准时到达,就一眼,身体的多巴胺被激活,好美的腰臀比,丰满圆润的臀部在牛仔裤的包裹下有点跃跃欲出的气息,因为住的近,刻意洗了澡才过来的,洗浴环节直接跳过。付了课费.在沙发上开启🐍吻,抚摸大长腿,小腿到大腿根上下游离,璐璐舌吻很主动, 时不时吸吮我的舌头,🐍的饱饱的,随后拉掏出牛子,璐璐跪地嗦起来,嗯嗯作响,瞬间好硬好滑,然后我让璐璐站起来,拉着她走到窗边,示意她双手撑在窗台,腰微微弯曲,臀部的完美幅度彻底展现出来,👀不曾离开臀部半步,👐不停揉搓掐捏,手瘾过足了,二弟早已经硬的不行,慢慢的把璐璐的牛仔裤褪到大腿根部,带上套套摩擦片刻用力一顶,整根插入…

❤5

Showing the 12 most recent of 17 posts we hold for @nixiaai. 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.

Forward network

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.

Mentions

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.

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 6 October 2026 — this entry's latest reading, not the date you are reading this.

“欧美臀露露-🐍吻” (@nixiaai), 1,553 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/nixiaai.

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.