Telegram RegisterThe public register of Telegram
Telegram profile photo for 小宝的频道

Channel

小宝的频道

@xiaobao121121

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

173subscribers

+18 since we began measuring on 30 September 2026

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

Register entry

Telegram ID-1004478843587
TypeChannel
Username@xiaobao121121
CreatedBetween 1 June 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded30 September 2026
Last confirmed live5 October 2026
Measurements held3
Confirmed unchanged1 time, most recently 5 October 2026
On Telegramt.me/xiaobao121121

Growth

15517316430 September 2026 — 155 subscribers30 September 2026 — 155 subscribers5 October 2026 — 173 subscribers30 September 20265 October 2026
3 measurements spanning 5 days, net +18. 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 152–176 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Oct 2026, 13:20173+18
30 Sept 2026, 16:22155no change
30 Sept 2026, 15:47155first reading

Engagement

20 posts held, back to 5 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
313.6%
avg views ÷ 173 subscribers
Avg views / post
542
17 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
17
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 September 2026
Posts held20 (5 September 2026 – 30 September 2026)
Views total9,222
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken30 Sept 2026, 16: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.

Recent posts

30 Sept 2026, 06:18 UTC131 viewsread 30 September 2026

💯 车评系统 | 评价模版 当前模版 【时间】:2026-09-30 【老师】:小宝 【留名】:1 3 【人照】:9 【颜值】:9 【身材】:8 【服务】:10 【态度】:10 【环境】:10 【报告出处】:重庆封神榜:https://t.me/fsbbyq666 【过程】:从上一个老师那里出来,本来想做pp,老师说后面排满了,只做了一次,意犹未尽,想到小宝老师也在附近,于是立刻联系,刚好有空,立刻前往。位置比较好找,一栋大楼的民宿,环境不错,进门会喊宝宝,态度非常好,然后寒暄一下开始洗澡,浴室服务第一次体验,胸和屁股在你打满沐浴露的身上蹭来蹭去,AV既视感,真的好爽,然后还有漱口水,洗完澡牵着你的手然后给你擦干,全程几乎不用自己动手,上床了先让你选衣服,然后开始服务,作为一个嫩妹服务这么好是我没想到的,毒龙的时候差点忍不住了,跟老师说,老师说会掌控好节奏的,继续正面服务,一摸老师下面好多水,开始69,然后戴套女上,紧,水多,…

29 Sept 2026, 03:12 UTC270 viewsread 30 September 2026
Photo

正常开课中,极品服务控等你来宠😍😍😍

25 Sept 2026, 09:42 UTC501 viewsread 30 September 2026
Forwarded from @FSB666Bot

💯 车评系统 | 评价模版 当前模版 【时间】:2026-09-25 【老师】:小宝 【留名】:匿名 【人照】:9 【颜值】:9 【身材】:8 【服务】:10 【态度】:10 【环境】:10 【报告出处】:重庆封神榜:https://t.me/fsbbyq666 【过程】:今天百无聊赖,不知道去谁突然看见小宝老师在群里说话,正好瞅见商城还有优惠券,于是乎换了券约好了老师。 进门老师就是给了一个大大的拥抱,慢慢的女友感,浅聊了一会儿,然后开始洗澡,老师态度是真的好,说话很温柔,体贴的递过来漱口水,是个爱干净的老师,洗澡也是非常得细心,全身上下都抹抹洗洗,还不时亲密互动,特别享受,洗完,正课开始,老师擦干净开始做服务,想得到一想不到的服务都有,特别是口的功夫,真的厉害,过程非常舒适,只要你不说停,会一直口,差点遭不住,连忙说开始,做的时候,老师也是非常配合,要求基本都能满足,做完了,也是会帮忙洗澡,只能说从进门到出门全…

24 Sept 2026, 02:43 UTC454 viewsread 30 September 2026
Photo

正常开课中,可包时,可包夜,可包天,可上门😍😍😍

23 Sept 2026, 02:55 UTC513 viewsread 30 September 2026
Photo

狠狠地大蟒蛇,一个可以抱起来艹的小妖精,主打服务,你确定不来试试😍😍😍

22 Sept 2026, 03:11 UTC544 viewsread 30 September 2026
Photo

可包时,可包夜,可包天,可上门,只要你有需求,我都尽量满足😍😍😍

21 Sept 2026, 03:24 UTC573 viewsread 30 September 2026
Photo

可包时,可包夜,可包天,可上门😍😍😍

20 Sept 2026, 03:07 UTC596 viewsread 30 September 2026
Photo

正常开课中,主打服务,真诚做口碑😍😍😍

19 Sept 2026, 03:07 UTC636 viewsread 30 September 2026
Photo

可包时,可包夜,可包天,主打服务😍😍😍

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

“小宝的频道” (@xiaobao121121), 173 subscribers as measured 5 October 2026. Telegram Register, tgregister.com/channel/xiaobao121121.

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.