Telegram RegisterThe public register of Telegram

Channel

天河 南伊

@xulaoshi81

On this record: Growth · Engagement · Posts · Citations · Cite this entry

738subscribers

+1 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1002516820737
TypeChannel
Username@xulaoshi81
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live11 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/xulaoshi81

Growth

737738737.510 Aug 2026, 06:15 — 737 subscribers11 Aug 2026, 05:56 — 738 subscribers10 Aug 2026, 06:1511 Aug 2026, 05:56
2 measurements taken within a single day, net +1. 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 737–738 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 05:56738+1
10 Aug 2026, 06:15737first reading

Engagement

20 posts held, back to 4 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
7.11%
avg views ÷ 738 subscribers
Avg views / post
52.5
2 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
2
of 20 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 30 July 2026
Posts held20 (4 June 202630 July 2026)
Views total105
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Aug 2026, 06:15 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.

Recent posts

30 Jul 2026, 02:52 UTC52 viewsread 10 August 2026
Photo

🈳人照合一 🉑舌吻🉑69🉑深喉🌹🌹 @xuning520 @xuning520bot

29 Jul 2026, 13:49 UTC53 viewsread 10 August 2026

🈳 🉑舌吻🉑69🉑深喉🌹🌹 @xuning520 @xuning520bot

12 Jul 2026, 02:05 UTC143 viewsread 10 August 2026
Photo

🈳人照合一 🉑舌吻🉑69🉑深喉🌹🌹 @xuning520 @xuning520bot

15 Jun 2026, 14:43 UTC417 viewsread 10 August 2026

🈳 🉑舌吻🉑69🉑深喉🌹🌹 @xuning520 @xuning520bot

15 Jun 2026, 14:16 UTC404 viewsread 10 August 2026
Forwarded from @yzzxin666

广州紫瑶宫报告模板 https://t.me/miuort 【所在位置】天河 【老师艺名】南伊 【联系方式】@xuning520 【验证留名】嘻嘻 【验证时间】周日 【上课价位】18pp 【颜值身材】高挑漂亮 【服务内容】课表 【服务态度】好 【优点缺点】皮肤滑嫩,漂亮 【推荐程度】10 【体验细节】心动再起,大雨也阻挡不了。冒雨前往进门,看到老师一个大大的拥抱和满足,但是我很贪婪,我觉得不够,我要索取,我要抱我要亲亲。狠狠贴贴真的满足开心啊,看着她的笑就很舒心,下雨淋了透心凉,直接冲个热水澡。我爱洗澡,老师皮肤好好洗完澡,爽爽,进入身体相拥相吻,真的太满足了见到老师都觉得好漂亮和魅魔一样勾引着我真的抵抗不了一点随即123出货,闲聊按摩聊聊人生,在战很快出货,不够爽。抱一抱亲亲不舍得走啊。攒够宝贝下次在冲 温馨提示 报告仅供参考 (上报须提供付款证明或聊天证明)

15 Jun 2026, 14:00 UTC281 viewsread 10 August 2026

10:30🈳人照合一 🉑舌吻🉑69🉑深喉🌹🌹 @xuning520 @xuning520bot

15 Jun 2026, 05:12 UTC288 viewsread 10 August 2026

🈳人照合一 🉑舌吻🉑69🉑深喉🌹🌹 @xuning520 @xuning520bot

12 Jun 2026, 01:34 UTC329 viewsread 10 August 2026
Photo

🈳人照合一 🉑舌吻🉑69🉑深喉🌹🌹 @xuning520 @xuning520bot

10 Jun 2026, 13:52 UTC330 viewsread 10 August 2026

🈳人照合一 🉑舌吻🉑69🉑深喉🌹🌹 @xuning520 @xuning520bot

10 Jun 2026, 04:23 UTC330 viewsread 10 August 2026
Photo

🈳人照合一 🉑舌吻🉑69🉑深喉🌹🌹 @xuning520 @xuning520bot

9 Jun 2026, 02:55 UTC323 viewsread 10 August 2026

🈳人照合一 🉑舌吻🉑69🉑深喉🌹🌹 @xuning520 @xuning520bot

8 Jun 2026, 07:27 UTC317 viewsread 10 August 2026

🈳人照合一 🉑舌吻🉑69🉑深喉🌹🌹 @xuning520 @xuning520bot

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

Citation-graph rank

Citation-graph rank — 880,116 of 1,340,412entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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.

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

“天河 南伊” (@xulaoshi81), 738 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/xulaoshi81.

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.