Telegram RegisterThe public register of Telegram
Telegram profile photo for 裸聊选妃

Channel

裸聊选妃

@yujie1v1

2 usernames

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

7,040subscribers

+965 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002596923632
TypeChannel
Usernames@aiaipwd1 @yujie1v1
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live16 September 2026
Measurements held44
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/yujie1v1

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 12 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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

5,93311,1388,535.57 August 2026 — 6,075 subscribers8 August 2026 — 5,933 subscribers11 August 2026 — 11,138 subscribers12 August 2026 — 11,058 subscribers12 August 2026 — 11,058 subscribers13 August 2026 — 10,943 subscribers14 August 2026 — 10,921 subscribers14 August 2026 — 10,913 subscribers15 August 2026 — 10,876 subscribers16 August 2026 — 10,709 subscribers17 August 2026 — 10,694 subscribers17 August 2026 — 10,694 subscribers18 August 2026 — 10,636 subscribers18 August 2026 — 10,606 subscribers19 August 2026 — 10,551 subscribers19 August 2026 — 10,551 subscribers20 August 2026 — 10,486 subscribers20 August 2026 — 10,485 subscribers21 August 2026 — 10,487 subscribers21 August 2026 — 10,484 subscribers22 August 2026 — 10,476 subscribers23 August 2026 — 10,478 subscribers24 August 2026 — 10,459 subscribers24 August 2026 — 10,459 subscribers25 August 2026 — 10,441 subscribers25 August 2026 — 10,402 subscribers26 August 2026 — 10,398 subscribers26 August 2026 — 10,398 subscribers27 August 2026 — 10,393 subscribers27 August 2026 — 10,393 subscribers29 August 2026 — 10,377 subscribers29 August 2026 — 10,377 subscribers30 August 2026 — 10,071 subscribers30 August 2026 — 10,071 subscribers31 August 2026 — 9,932 subscribers31 August 2026 — 9,848 subscribers3 September 2026 — 9,010 subscribers4 September 2026 — 8,798 subscribers8 September 2026 — 8,134 subscribers8 September 2026 — 8,134 subscribers12 September 2026 — 7,786 subscribers13 September 2026 — 7,667 subscribers16 September 2026 — 7,222 subscribers16 September 2026 — 7,040 subscribers7,0407 August 202616 September 2026
44 measurements spanning 40 days, net +965. 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 5,152–11,919 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 44
Measured (UTC)SubscribersChange
16 Sept 2026, 17:407,040-182
16 Sept 2026, 04:387,222-445
13 Sept 2026, 04:567,667-119
12 Sept 2026, 19:597,786-348
8 Sept 2026, 23:198,134no change
8 Sept 2026, 19:378,134-664
4 Sept 2026, 01:158,798-212
3 Sept 2026, 18:569,010-838
31 Aug 2026, 16:089,848-84
31 Aug 2026, 13:129,932-139
30 Aug 2026, 13:1110,071no change
30 Aug 2026, 12:4210,071-306
29 Aug 2026, 15:4410,377no change
29 Aug 2026, 15:1510,377-16
27 Aug 2026, 18:1710,393no change
27 Aug 2026, 10:4210,393-5
26 Aug 2026, 19:4410,398no change
26 Aug 2026, 10:0410,398-4
25 Aug 2026, 20:2310,402-39
25 Aug 2026, 08:0410,441first reading

Engagement

9 posts held, back to 12 March 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 32 pages 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 9 posts for this entry, the most recent from 19 May 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
55s
Average length
11s

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

2,402 reactions across 7 posts, in 9 distinct kinds. The most used accounts for 12.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤩29012.1%
😍28211.7%
👍27111.3%
❤‍🔥26411.0%
🔥26411.0%
🥰26110.9%
25810.7%
💯25710.7%
🎉25510.6%

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 8 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 2,402 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 12 March 2026 to 19 May 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

19 May 2026, 11:59 UTC≈4,050 views5 reactionsread 29 August 2026
Photo

今日推荐: #小惜 邻家小妹类型,颜值清纯可爱,服务好,态度好,不稳定在线,喜欢的哥哥现在速D~ 🙏注:大家有任何问题以及下单请联系老板娘! 初恋 id:@zhuyu1 双向机器人: @yujieIbot

5

25 Apr 2026, 15:06 UTC≈5,520 views4 reactionsread 29 August 2026
Photo

今日推荐: #勾勾 漂亮女明星氛围感十足的顶流接单妹妹 喜欢的务必速速私我~ 🙏注:大家有任何问题以及下单请联系老板娘! 初恋 id:@zhuyu1 双向机器人: @yujieIbot

4

8 Apr 2026, 12:08 UTC≈5,530 views3 reactionsread 29 August 2026
Photo

今日推荐: id:#心凌 裸聊界舞蹈老师心凌也在了~超绝一字马展示粉穴 长腿细腰 头牌妹妹不多介绍了 哥哥们都知道~ 🙏注:大家有任何问题以及下单请联系老板娘! 初恋 id:@zhuyu1 双向机器人: @yujieIbot

3

24 Mar 2026, 16:38 UTC≈5,310 views2 reactionsread 29 August 2026
Photo

今日推荐: id:#麦当劳 超漂亮的妹妹 态度好接单非常认真 项目齐全 网图制造机 36D 白🐯嫩穴~水多可潮喷~喜欢的哥哥私 🙏注:大家有任何问题以及下单请联系老板娘! 初恋 id:@zhuyu1 双向机器人: @yujieIbot

2

20 Mar 2026, 16:44 UTC≈10,200 views6 reactionsread 29 August 2026
Photo

私密靠谱: 1. 只用QQ或微信进行服务,不需要下载软件 2. 不需要开启摄像头,只需指挥享受, 剩下 的交给妹妹 支付方式:👍微信/👍支付宝/🧐USDT 怀疑妹妹不真实,担心有套路的哥哥 首单可验证妹妹,验证单30元可抵扣下单 下单客服:@zhuyu1 下单机器人:@yujieIbot

6

17 Mar 2026, 11:52 UTC≈4,170 views1 reactionsread 29 August 2026
Photo

今日推荐: #美沅 头牌妹妹,车模 人美声甜、天花板颜值、身材极品,黑长直、叫声s,项目齐全,活好服务号,爆火的顶级妹妹,晚上在线,需要提前预约排队,喜欢的板板的私我~| 美沅营业时间19:00-02:00 支持📏📖📔 初恋 id:@zhuyu1 双向机器人: @yujieIbot

1

13 Mar 2026, 16:41 UTC≈11,500 views2,381 reactionsread 29 August 2026

以下评论是每天实时在线 持续更新 上一个发一个⬇️ 接单图是露脸就接露脸 不露脸就是不漏的 可能有漏发 频道有喜欢 别的妹妹的咨询客服是否在线

🤩290😍282👍271❤‍🔥264🔥264🥰261💯257🎉255

12 Mar 2026, 05:57 UTC≈4,500 viewsread 29 August 2026
Photo

今日推荐: #杯杯 超绝的露脸妹妹 颜值高 极致腰臂比 自嫩多水 三点粉 足控福音 骚得没边悶望披开发的母狗 可双,三女 好评多多 喜欢的板板私我~

12 Mar 2026, 05:48 UTC≈3,720 views0 reactionsread 29 August 2026
Photo

今日推荐: id:#裕娜 项目:露脸

Showing the 9 most recent of 9 posts we hold for @yujie1v1. 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 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 16 September 2026 — this entry's latest reading, not the date you are reading this.

“裸聊选妃” (@yujie1v1), 7,040 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/yujie1v1.

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.