Telegram RegisterThe public register of Telegram
Telegram profile photo for 初音测评群

Channel

初音测评群

@chuyin123123123

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

103subscribers

-4 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1002776639064
TypeChannel
Username@chuyin123123123
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live3 October 2026
Measurements held6
Confirmed unchanged3 times, most recently 3 October 2026
On Telegramt.me/chuyin123123123

Topic

Adult — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 27 September 2026 and assigned it the closest of 31 fixed categories, at 53% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

1031071058 August 2026 — 107 subscribers9 August 2026 — 107 subscribers17 August 2026 — 105 subscribers25 August 2026 — 104 subscribers31 August 2026 — 105 subscribers9 September 2026 — 103 subscribers8 August 20269 September 2026
6 measurements spanning 32 days, net -4. 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 102–108 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 06:58103-2
31 Aug 2026, 04:33105+1
25 Aug 2026, 04:19104-1
17 Aug 2026, 10:48105-2
9 Aug 2026, 08:17107no change
8 Aug 2026, 03:16107first reading

Engagement

16 posts held, back to 7 December 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 16 posts for this entry, the most recent from 24 December 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
1m 26s
Average length
10s

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

6 reactions across 3 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤6100.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 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 6 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 7 December 2025 to 24 December 2025, 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

24 Dec 2025, 11:33 UTC≈1,120 views4 reactionsread 9 August 2026
Video

店铺:#初音 女仆:#妙妙 价格:600 班型:超大 出击人:#超超大哥哥 出击时间:12.23 首次服役时间:2025 环境:小区 颜值:人照8,真人7.5 身材: 有菜有肉 身高:165 体重:49 皮肤:滑 态度:开朗主动 抽烟:无 纹身:无 唇钉舌钉:无 【高端服务】:有的打✅ ① 舌吻 ✅ ② 摸胸✅ ③ 吃胸✅ ④情绪价值 ✅ 过程:初音自从挂了妙妙的模卡我就有想去的冲动,一眼女大甜妹风。跟客服小音约好时间,安排了主卧,到了小坐一会妹妹就进来了。 妙妙进来先是打招呼,然后看我很淡定的问我是不是常来这家店(最近点客服确实有点多。另外还是第一次有妹妹会主动上来帮忙脱鞋的,还是又被加菜了?妙妙ootd里的纱裙上身确实很仙,并且搭配长筒靴颇具御姐气质。我问妙妙为什么这么久不来店里,妹妹说之前因为学校忙所以很久之前来一次后就再也没来过,接下来可能会增加一些到店频率。聊…

❤4

20 Dec 2025, 10:07 UTC≈1,090 viewsread 9 August 2026
Video

【妹子花名】:#迟迟 【所属店铺】:#初音 【联系方式】:@chuyin999 【验证留名】:ggbb 【验证时间】:12月 【大概位置】:#东站元宝塘 【课程费用】:#超大班 【高端服务】:有的打✅ ① 舌吻 ✅ ② 摸胸✅ ③ 吃胸✅ ④情绪价值 ✅ 【人照相似】:8 【身高身材】:8 【凶器罩杯】:b 【个人标签】:情绪价值 女友感 【环境细节】:换了地方 感觉没之前好 但有一次性床单 卫生过关 评分标准:复刷 懂得都懂 【流程小文】:二刷迟迟,甜妹类型,大蟒蛇,小s,主动性高,情绪价值高。会不定期复刷的类型

10 Dec 2025, 05:50 UTC≈1,030 views0 reactionsread 9 August 2026
Video

店铺:#初音 女仆:#茵茵 价格:600 班型:单钟 出击人:#超超大哥哥 出击时间:12.08 首次服役时间:2025 环境: 居民区 颜值:人照8,真人7 身材: 少萝 身高:158 体重:84 皮肤:平滑 态度:比较配合 抽烟:无 纹身:无 唇钉舌钉:无 【高端服务】:有的打✅ ① 舌吻 ✅ ② 摸胸✅ ③ 吃胸✅ ④情绪价值 ✅ 门店综合评分(注明打分理由): ①门店位置(交通便利度,停车) ⭐️⭐️⭐️⭐️⭐️ 「东站,小区可停车」 ②门店公寓/小区环境(有无梯控,隐蔽性) ⭐️⭐️⭐️⭐️⭐️ 「无梯控,无门禁」 ③店内环境(是否脏乱差,有无烟味/异味) ⭐️⭐️⭐️⭐️⭐️ 「不抽烟,主卧有淋浴」 ④房间舒适度(床的舒适度,有无标配的用品) ⭐️⭐️⭐️ 「有大床,当天未铺床垫及缺货浴巾」 ⑤客服满意度(反馈效率,服务态度) ⭐️⭐️⭐️⭐️⭐️ 「客服反…

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

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

“初音测评群” (@chuyin123123123), 103 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/chuyin123123123.

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.