Telegram RegisterThe public register of Telegram
Telegram profile photo for 台湾UU直播裸聊聊天室

Channel

台湾UU直播裸聊聊天室

@uuchatroom

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

466subscribers

+48 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002480229777
TypeChannel
Username@uuchatroom
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live16 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/uuchatroom

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

4184664427 August 2026 — 418 subscribers8 August 2026 — 418 subscribers8 August 2026 — 421 subscribers16 August 2026 — 431 subscribers23 August 2026 — 434 subscribers30 August 2026 — 446 subscribers9 September 2026 — 457 subscribers16 September 2026 — 466 subscribers7 August 202616 September 2026
8 measurements spanning 40 days, net +48. 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 411–473 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 16:58466+9
9 Sept 2026, 13:59457+11
30 Aug 2026, 11:45446+12
23 Aug 2026, 22:38434+3
16 Aug 2026, 19:42431+10
8 Aug 2026, 13:46421+3
8 Aug 2026, 05:32418no change
7 Aug 2026, 18:17418first reading

Engagement

7 posts held, back to 7 August 2026the 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 7 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

7 Aug 2026, 08:21 UTC19 viewsread 8 August 2026
Photo

主播:Charlottea 区域:嘉義縣市 身高:159 体重:40 年龄:23 岁 颜值:❤️❤️❤️❤️❤️ 5.00分 身材:🔥🔥🔥🔥🔥 5.00分 表演:🌹🌹🌹🌹🌹 5.00分 下载APP马上观看 注册会员马上观看 进入直播间马上观看

7 Aug 2026, 08:19 UTC19 viewsread 8 August 2026
Photo

主播:王老師珺 区域:大陸地區 身高:167 体重:48 年龄:29 岁 颜值:❤️❤️❤️❤️ 4.43分 身材:🔥🔥🔥🔥 4.63分 表演:🌹🌹🌹🌹 4.43分 下载APP马上观看 注册会员马上观看 进入直播间马上观看

7 Aug 2026, 08:18 UTC13 viewsread 8 August 2026
Photo

主播:好玩嫂嫂 区域:大陸地區 身高:163 体重:49 年龄:28 岁 颜值:❤️❤️❤️❤️❤️ 5.00分 身材:🔥🔥🔥🔥🔥 5.00分 表演:🌹🌹🌹🌹🌹 5.00分 下载APP马上观看 注册会员马上观看 进入直播间马上观看

7 Aug 2026, 08:17 UTC9 viewsread 8 August 2026
Photo

主播:白日夢 区域:台北市 身高:162 体重:48 年龄:28 岁 颜值:❤️❤️❤️❤️❤️ 5.00分 身材:🔥🔥🔥🔥🔥 5.00分 表演:🌹🌹🌹🌹🌹 5.00分 下载APP马上观看 注册会员马上观看 进入直播间马上观看

7 Aug 2026, 08:16 UTC5 viewsread 8 August 2026
Photo

主播:希米 区域:台中市 身高:163 体重:43 年龄:28 岁 颜值:❤️❤️❤️❤️❤️ 5.00分 身材:🔥🔥🔥🔥🔥 5.00分 表演:🌹🌹🌹🌹🌹 5.00分 下载APP马上观看 注册会员马上观看 进入直播间马上观看

7 Aug 2026, 08:15 UTC3 viewsread 8 August 2026
Photo

主播:奶桃 区域:台北市 身高:166 体重:43 年龄:23 岁 颜值:❤️❤️❤️❤️❤️ 5.00分 身材:🔥🔥🔥🔥🔥 5.00分 表演:🌹🌹🌹🌹🌹 5.00分 下载APP马上观看 注册会员马上观看 进入直播间马上观看

7 Aug 2026, 08:14 UTC3 viewsread 8 August 2026
Photo

主播:曼俐 区域:大陸地區 身高:162 体重:49 年龄:28 岁 颜值:❤️❤️❤️❤️❤️ 5.00分 身材:🔥🔥🔥🔥🔥 5.00分 表演:🌹🌹🌹🌹🌹 5.00分 下载APP马上观看 注册会员马上观看 进入直播间马上观看

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

“台湾UU直播裸聊聊天室” (@uuchatroom), 466 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/uuchatroom.

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.