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

Channel

小丸子的频道

@xwz11228

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

64subscribers

+30 since we began measuring on 10 November 2026

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

Register entry

Telegram ID-1004336367275
TypeChannel
Username@xwz11228
Created9 November 2026 — measured — dated from the channel’s first post
First recorded10 November 2026
Last confirmed live11 November 2026
Measurements held3
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/xwz11228

Growth

34644910 Nov 2026, 11:47 — 34 subscribers10 Nov 2026, 12:22 — 34 subscribers11 Nov 2026, 07:05 — 64 subscribers10 Nov 2026, 11:4711 Nov 2026, 07:05
3 measurements taken within a single day, net +30. 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 30–69 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Nov 2026, 07:0564+30
10 Nov 2026, 12:2234no change
10 Nov 2026, 11:4734first reading

Engagement

8 posts held, back to 9 November 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
167.0%
avg views ÷ 64 subscribers
Avg views / post
107
7 posts measured
Reaction rate
1.32%
reactions ÷ views · ER floor
Posts in window
8
of 8 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 5 of 7 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 10 November 2026
Posts held8 (9 November 2026 – 10 November 2026)
Views total748
Reactions total5
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Nov 2026, 12: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

Video runtime
11s
Average length
4s

Measured directly from 3 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

5 reactions across 5 posts, in 1 kind.

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

Measured over the 8 most recent posts we hold, published 9 November 2026 to 10 November 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

Telegram’s own ‘edited’ marker: 0 of 8 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

10 Nov 2026, 09:05 UTC28 views1 reactionsread 10 November 2026

【广深报告】[https://t.me/QMqun] 【所在位置】:天河 【老师艺名】:樱桃小丸子 【联系方式】:@wanzi6790 【验证留名】:and the 【验证时间】:11.10 【课程打赏】:1课500米 【颜值身材】:清秀耐看,气质干净舒服,和照片相似度真的很高👍 【服务内容】:表现优秀,流程自然流畅,该有的都给到位了 【服务态度】:热情体贴,沟通轻松愉快,完全没有新人的生疏感😊 【优点缺点】:暂时没感觉到明显短板,整体体验感很完整 【推荐程度】:9 【体验细节】:看到新老师上榜,第一时间就约了过去。到了指定位置,老师遥控带上楼,推门看见本人的时候还是有点小惊喜的——照片还原度大概有90%,比最近见过的很多新人都真实太多了👀 果断交了水费,一起洗完澡之后老师就开始服务。课表上的项目一个不落,全部认真做完了,服务真的很到位,没得挑。 老师下面紧致又水多,皮肤白嫩有弹性,整体感觉很舒服。这个价格能碰到这样的,感觉完全…

❤1

10 Nov 2026, 08:59 UTC28 views1 reactionsread 10 November 2026
Photo

哥哥太猛了,又要换🛏️单了💕💕💕💕

❤1

10 Nov 2026, 07:32 UTC30 views1 reactionsread 10 November 2026
Forwarded from @GZNMMTL

【嫩妹报告】https://telegram.me/GZNMHEJI 【老师艺名】樱桃小丸子 【联系方式】@wanzi6790 【所在位置】天河 【验证留名】凯撒 【验证时间】11月10 【修车费用】500p 【颜值身材】同价位中属顶尖水准,清丽可人,曲线丰盈有致 【服务内容】完整课表 【服务态度】温柔热情,善于营造轻松氛围 【优点缺点】几乎无短板,新人却已具备成熟的服务意识 【推荐程度】9 【体验细节】午后空闲,刷到嫩妹频道新上的老师,便即刻预约。 课室干净整洁,位置也很好找。推门而入的瞬间,便确认自己没走错地方——老师容貌清秀,胸前丰满,气质温柔又不失俏皮。 简单聊了几句,得知她是刚入行的新人。随后一起沐浴,鸳鸯浴中水中互动细腻而自然,身体与情绪都在热水中慢慢放松。 进入主题后,节奏把控得当,过程舒缓却又不失激情,双方都沉浸其中,结束后都觉得酣畅而满足。整场体验毫无生疏感,像是一次彼此契合的相遇。 还会再约。这样的老师,值得…

❤1

9 Nov 2026, 08:35 UTC195 views1 reactionsread 10 November 2026
Video

绽放是我的姿态,娇艳是我的底色,骚穴为你失禁的的每一次,是我无法自持的沉溺,宝贝!你总是那么优秀,能让我欲仙欲死,情不自禁的被你征服,刚来广州,第一天开课有宝宝来嘛

❤1

9 Nov 2026, 08:00 UTC99 views1 reactionsread 10 November 2026
Forwarded from @GCCITYPhoto

地区:#天河 艺名:樱桃小丸子 验证:视频报日期验证 课表:500/1 TG :@wanzi6790 标签:#嫩妹 #制服 #鸳鸯浴 PS:课后请在下方评论反馈 👉点此预约樱桃小丸子 报告奖励:200 分

❤1

Showing the 8 most recent of 8 posts we hold for @xwz11228. 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 3 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.

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

“小丸子的频道” (@xwz11228), 64 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/xwz11228.

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.