Telegram RegisterThe public register of Telegram
Telegram profile photo for U mi高端工作室 (觀塘)

Channel

U mi高端工作室 (觀塘)

@spaUmi

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

969subscribers

+277 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-1003948456765
TypeChannel
Username@spaUmi
CreatedBetween 1 April 2026 and 28 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live11 October 2026
Measurements held10
Confirmed unchanged1 time, most recently 11 October 2026
On Telegramt.me/spaUmi

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

692969830.57 August 2026 — 692 subscribers8 August 2026 — 692 subscribers8 August 2026 — 704 subscribers16 August 2026 — 748 subscribers24 August 2026 — 779 subscribers31 August 2026 — 795 subscribers9 September 2026 — 830 subscribers16 September 2026 — 847 subscribers2 October 2026 — 933 subscribers11 October 2026 — 969 subscribers7 August 202611 October 2026
10 measurements spanning 65 days, net +277. 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 650–1,011 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Oct 2026, 21:41969+36
2 Oct 2026, 01:56933+86
16 Sept 2026, 20:00847+17
9 Sept 2026, 02:17830+35
31 Aug 2026, 07:03795+16
24 Aug 2026, 19:43779+31
16 Aug 2026, 04:16748+44
8 Aug 2026, 18:22704+12
8 Aug 2026, 02:20692no change
7 Aug 2026, 19:29692first reading

Engagement

7 posts held, back to 28 July 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.

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 5 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
2m 40s
Average length
53s

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

4 reactions across 2 posts, in 1 kind.

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

Measured over the 7 most recent posts we hold, published 28 July 2026 to 5 August 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

5 Aug 2026, 17:08 UTC433 viewsread 8 August 2026
Photo

#Mia好評來啦❤️😍 哥哥们得闲過黎放鬆開心下 女女服務好态度好 素質高 環境好 衛生乾淨 私密度高 VIP大房 一次性浴巾 😍🥰🥰💋

4 Aug 2026, 01:38 UTC799 viewsread 8 August 2026
Photo

各位哥哥早晨🥰 今日#Mia返工啦 仲有空位可以約❤️ 歡迎哥哥們快啲預約啦💯

3 Aug 2026, 03:31 UTC848 views2 reactionsread 8 August 2026
Photo

♥️Umi工作室(最新精選推介)♥️ 地區: #觀塘 類型: #個人私密工作室 正妹囡囡 : #Mia Wow💓本周精選又有好野到啦😍 ❣️新人 #Mia 身高 156cm,體重 43kg 💗真人相對到相㗎☺️新移民初次下海 短期限定👍💘初下海賺下生活費😍 青春body皮膚白滑真波 三點粉pink 清純活潑可愛🥰笑容超甜美 可愛主動 淫底聽教聽話🌹 想睇更多??👇🏻👇🏻👇🏻👇🏻👇🏻👇🏻 TG預約號:@Umi_spa888 TG睇图號:https://t.me/spaUmi ☎️WhatsApp :65513357

❤2

2 Aug 2026, 10:04 UTC800 viewsread 8 August 2026
Video

瑜珈教練#依依,返工中 歡迎哥哥們預約啦🥰

2 Aug 2026, 02:29 UTC793 viewsread 8 August 2026

各位哥哥早晨🥰 今日依依返工啦 仲有空位可以約❤️ 歡迎哥哥們快啲預約啦💯

30 Jul 2026, 02:22 UTC968 views2 reactionsread 8 August 2026
Photo

Umi工作室 地區:《觀塘》 ⭐️新女推薦⭐️#依依 瑜珈教練🧘‍♀️ 身高155cm 體重40kg,胸圍34 B 自拍生活照片 清純,靚女💗 ✳️ A4小蛮腰 小蜜臀 絕對瘦底💗 ✳️ 哇 好誘惑好吸引😍 ✳️ 骨技精湛,按摩💆一流 ✳️ 體質敏感易出水💦 ✳️ 騎術技巧高,身體超柔軟 🉑 角色扮演,制服,絲襪誘惑 💖 觀塘區,鄰近地鐵站🚉 💖 獨立房間、附設浴室🛀,私隱度高 💖 一次性床單、浴巾,安全衛生 💖 房間每日清潔,每次用後消毒,不容細菌🦠 ❤️想睇更多??👇🏻👇🏻👇🏻👇🏻👇🏻👇🏻 TG預約號:@Umi_spa888 TG睇图號:https://t.me/spaUmi ☎️WhatsApp :65513357

❤2

28 Jul 2026, 19:12 UTC≈1,110 viewsread 8 August 2026
Video

瑜珈教練#依依,返工啦 歡迎哥哥們預約啦🥰

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

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

“U mi高端工作室 (觀塘)” (@spaUmi), 969 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/spaUmi.

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.