Telegram RegisterThe public register of Telegram
Telegram profile photo for 南山 06 小V频道(红休中)

Channel

南山 06 小V频道(红休中)

@xiaoi3689

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

693subscribers

+0 since we began measuring on 25 September 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1004447998499
TypeChannel
Username@xiaoi3689
Description@xiaoi3875_bot 机器人 频道 https://t.me/xiaoi3689
First recorded25 September 2026
Last confirmed live25 September 2026
Measurements held2
On Telegramt.me/xiaoi3689

Growth

69325 Sept 2026, 16:47 — 693 subscribers25 Sept 2026, 17:22 — 693 subscribers25 Sept 2026, 16:4725 Sept 2026, 17: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 692–694 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Sept 2026, 17:22693no change
25 Sept 2026, 16:47693first reading

Engagement

16 posts held, back to 15 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
99.0%
avg views ÷ 693 subscribers
Avg views / post
686
13 posts measured
Reaction rate
0.282%
reactions ÷ views · ER floor
Posts in window
16
of 16 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 4 of 13 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 23 September 2026
Posts held16 (15 September 2026 – 23 September 2026)
Views total8,916
Reactions total8
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken25 Sept 2026, 17: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
19
Videos
4
Links
7

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

Video runtime
17s
Average length
17s

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.

Reaction mix

8 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 75.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤675.0%
👍225.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 4 of the 16 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 8 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 16 most recent posts we hold, published 15 September 2026 to 23 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.

Recent posts

22 Sept 2026, 09:30 UTC426 viewsread 25 September 2026

优质老师出击笔记模板 【出击报告】(REPORT @SHFriendsBG ) 位置坐标: #深圳 #南山 学生留名: #夜星 学生电报号: @nightstar1234 上课时间: 9月20日 老师花名: #小v 老师电报号: @sss7751 上课花费: 1p 老师质量: 人照相符8分,服务态度9分,服务技能8分,情绪价值9分 ,环境卫生8分,有无陪洗:有 ( PS: 按照1到10打分 ) 服务内容:XZC 大蟒蛇 69 上课过程:群友推的老師,看了各群都沒卷,就直接出擊了。 頻道的照片很多奇奇怪怪的,真人 人照8,是個短髮嫩妹,性格爽直 且有禮貌,不是i人,會大大列列的說話,給人開朗的感覺。高163左右,熊小c,胸是飽滿型很好摸,身材不錯,皮膚黃白偏白。 坐下聊一會去洗澡,有陪洗,洗完上閣樓 床上先蛇起來,大蟒蛇 主動蛇,拉妹子躺下 親熊時妹子已經發出點聲音,看看下面,…

22 Sept 2026, 09:27 UTC301 viewsread 25 September 2026

谢谢哥哥用心的小作文,给你一百万个小心心♥️

22 Sept 2026, 09:26 UTC303 views2 reactionsread 25 September 2026

优质老师出击笔记模板 【出击报告】(REPORT @SHFriendsBG ) 位置坐标: #深圳 #福田 学生留名: #脑瓜疼 学生电报号: @NKTJBA 上课时间: 9.13 老师花名: #小V 老师电报号: @sss7751 上课花费: 1300 老师质量: 人照相符9.5分,服务态度9.5分,服务技能9分,情绪价值9.8分 ,环境卫生9分,有无陪洗:有 ( PS: 按照1到10打分 ) 服务内容: 洗吹做舌吻69 上课过程: 看到新妹妹上榜,频道照片看起来有点御姐的感觉,怀着探雷的心态大雨天去现场探一下。见面就觉得这趟冒雨工兵之旅赚了,本人比照片好看多了,清新风的小美女稍微带一点小混血的感觉(问了妹妹实际是湖南人),小V脸大眼睛,说话软糯糯的还带一点呆萌,像是刚出社会那种不忍心欺负的小妹妹的感觉,主动递拖鞋递水也是热情周到,果断强压下激动的心情付了水费。…

👍2

17 Sept 2026, 12:33 UTC≈1,210 viewsread 25 September 2026
Forwarded from @baogaohuajianji

百花名录报告模板 { https://t.me/huaxufengnan } 位置坐标: #深圳 验证留名: @miyuki000 上课时间: 9月17日 老师名字: #小v 联系方式: @sss7751 上课花费: p-优惠券 颜值: 9/10 身材: 9/10 胸: 8/10 腰: 9/10 腿: 8/10 服务态度:10/10 爱爱体验: 10/10 情绪价值: 9/10 课室环境: 9/10 人照相似度:9/10 体验过程补充: 第二次约小v了,这次换了新的课室,见到小v还是熟悉的模样,甚是开心。先是一起共浴,看着美好的身躯又忍不住拥吻起来。今天小v穿了黑丝,来到床上后又是抱着大蟒蛇,直接亲的我血脉偾张,肉棒早已挺立。接着老师一口吞下,来回又是吞吐又是舔着,享受着老师的口活,已经按耐不住。接着戴上小☔️,小v…

Showing the 12 most recent of 16 posts we hold for @xiaoi3689. 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 25 September 2026 — this entry's latest reading, not the date you are reading this.

“南山 06 小V频道(红休中)” (@xiaoi3689), 693 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/xiaoi3689.

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.