Telegram RegisterThe public register of Telegram
Telegram profile photo for 少女萝莉

Channel

少女萝莉

@shaonvrz

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

6,353subscribers

+0 since we began measuring on 16 November 2026

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

Register entry

Telegram ID-1003457099117
TypeChannel
Username@shaonvrz
Created26 November 2025 — measured — dated from the channel’s first post
First recorded16 November 2026
Last confirmed live16 November 2026
Measurements held2
On Telegramt.me/shaonvrz

Growth

6,35316 Nov 2026, 14:47 — 6,353 subscribers16 Nov 2026, 15:22 — 6,353 subscribers16 Nov 2026, 14:4716 Nov 2026, 15: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 6,347–6,359 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Nov 2026, 15:226,353no change
16 Nov 2026, 14:476,353first reading

Engagement

9 posts held, back to 26 November 2025 — 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
36.5%
avg views ÷ 6,353 subscribers
Avg views / post
2,320
8 posts measured
Reaction rate
0.045%
reactions ÷ views · ER floor
Posts in window
8
of 9 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 8 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 11 November 2026
Posts held9 (26 November 2025 – 11 November 2026)
Views total18,559
Reactions total7
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Nov 2026, 15: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
4
Videos
2
Links
1

Lifetime counters from Telegram’s own channel header, read 16 November 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
25s
Average length
13s

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

7 reactions across 4 posts, in 1 kind.

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

Measured over the 9 most recent posts we hold, published 26 November 2025 to 11 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: 1 of 8 posts held from the last 30 days (12.5%) 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).

11 Nov 2026, 13:50 UTC618 views1 reactionsread 16 November 2026
Photo

長相和胸針一樣的8菲🐇 🍫 TG: @Steve_6e 雙向进群: @luoliquanrenzheng

❤1

4 Nov 2026, 10:38 UTC≈1,130 views1 reactionsread 16 November 2026
Video

⟡ · ⊹ · 🍫 · ⊹ · ⟡ 哥哥覺得貴都是因為‘好’才覺得貴 決定價格的不是我 是價值 是品質 是服務態度 誰家的錢不是真金白銀 花錢仔細一點沒關係寶寶 物美價廉只是商家最愛用的一種營銷手段 不止是Kitty家 從古至今都是一分錢拿一分貨 但是我能做到的就是 盡最大的努力 幫你省更多的錢讓你選擇心儀的小姐 🪽TG: @Steve_6e🦋

❤1

3 Nov 2026, 00:07 UTC≈1,220 views3 reactionsread 16 November 2026
Photo

身为一个专业且合格的妈妈桑,到底需要具备哪些条件?🤔 ① 记性要好 客人的喜好、预约时间、指定要求、上次的体验感受,都要尽可能记在心里。毕竟客人是来放松的,不是来参加记忆力测验的(笑)。 ② 眼光要好,不能什么都说好 推荐女生不是把名单丢给客人,然后说一句「自己挑喔」。了解客人的需求,认真筛选、如实介绍,不夸大、不乱吹捧,比什么都重要。适合的才是最好的,不是价格最高的才叫推荐。 ③ 情绪要稳,遇事不能装死 预约顺利的时候,大家都是好朋友。但真正考验妈妈桑专业度的,是遇到临时变动、沟通误会或突发状况的时候。该处理的事情不推卸,该负责的地方不逃避。讯息可以晚几分钟回,但责任不能已读不回(笑)。 ④ 细节控,最好还有一点强迫症 时间、地点、酒店、预约内容、双方确认事项,每一个细节都不能马虎。客人不一定看得见我们背后做了多少准备,但每一次顺利的安排,都离不开这些小细节。 ⑤ 嘴巴可以甜,但做人一定要真 不需要把每个女孩都形容成…

❤3

2 Nov 2026, 05:26 UTC≈11,400 views0 reactionsread 16 November 2026
Photo

✨全网萝莉少女圈✨ ❤️群内文明发言,自由平等 ❤️群内禁止,言语低俗, ❤️禁止刷屏广告,链接引流 ❤️禁止发送血腥·暴力·wcn·等 ❤️禁止辱骂女性,恶意造谣 黑地域 禁止谈论政治 ❤️如有问题,可联系群主协商 @Steve_6e ❤️上榜认证 管理员 投稿 请联系群主 @Steve_6e 进群的人先点击下方按钮进入主群,更多福利都在这里

2 Nov 2026, 04:58 UTC≈1,060 viewsread 16 November 2026

打炮規矩 1:如果不耐操 就別來 做不爽再也不跟你約 2:我說穿什麼就穿什麼 給老子騷一點 不騷我直接打車回家 3:到了床上不要給我甩臉色 不主動的自己回家 🪽TG: @Steve_6e🦋

1 Nov 2026, 22:48 UTC≈1,020 views2 reactionsread 16 November 2026

✨ 全网萝莉少女圈 · 正式邀请 ✨ 喜欢甜软、元气、粉嫩少女感的你,这里刚刚好。 我们是一群热爱可爱日常、清新穿搭、软萌氛围的小伙伴。 ✨全网萝莉少女圈·聊天群✨ ✨少女认证·公开榜✨ 没有压力,只有轻松分享和温柔陪伴。 无论你是想晒今天的粉色穿搭,还是单纯想找人聊聊少女心,都欢迎加入~ 感兴趣的话,随时来找我,带你进圈。 一起变可爱,一起被温柔包围吧。

❤2

1 Nov 2026, 14:44 UTC961 viewsread 16 November 2026

蓓蓓的夢想就是讓全世界的男人都有愛做呀 🪽TG: @Steve_6e 🦋

Showing the 9 most recent of 9 posts we hold for @shaonvrz. 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

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

“少女萝莉” (@shaonvrz), 6,353 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/shaonvrz.

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.