Telegram RegisterThe public register of Telegram
Telegram profile photo for Miko💞開心工作坊💞(長沙灣)

Channel

Miko💞開心工作坊💞(長沙灣)

@mikomass

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

704subscribers

+75 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-1001876896999
TypeChannel
Username@mikomass
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live3 October 2026
Measurements held9
Confirmed unchanged1 time, most recently 3 October 2026
On Telegramt.me/mikomass

Topic

Health & wellness — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 81% 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

6287046667 August 2026 — 629 subscribers8 August 2026 — 629 subscribers8 August 2026 — 628 subscribers15 August 2026 — 631 subscribers23 August 2026 — 642 subscribers31 August 2026 — 657 subscribers9 September 2026 — 669 subscribers18 September 2026 — 684 subscribers3 October 2026 — 704 subscribers7 August 20263 October 2026
9 measurements spanning 57 days, net +75. 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 617–715 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Oct 2026, 13:21704+20
18 Sept 2026, 04:21684+15
9 Sept 2026, 05:20669+12
31 Aug 2026, 03:08657+15
23 Aug 2026, 09:12642+11
15 Aug 2026, 10:27631+3
8 Aug 2026, 04:57628-1
8 Aug 2026, 02:50629no change
7 Aug 2026, 13:03629first reading

Engagement

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

What this channel posts

Video runtime
46s
Average length
23s

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.

Recent posts

7 Aug 2026, 01:09 UTC40 viewsread 8 August 2026
Photo

各位早上好🙋‍♀今天有開呀💪敬請提早預約呀💕🙇‍♀

5 Aug 2026, 02:51 UTC75 viewsread 8 August 2026
Photo

早上好呀🌻今天有開工呀,有需要养生按摩的可約我呀🙇‍♀

3 Aug 2026, 01:00 UTC122 viewsread 8 August 2026
Photo

各位帥哥們好呀💞本人是在香港桑拿大場出身,穴位按摩,踩背,拉筋,推前列腺,專業泰式抓龍筋,柔情掃股,狗仔式抓龍筋技术精湛好多客人都点贊👍按摩力度配合客人需求,肩頸不舒服,腰酸背痛,肩周炎痛,小腿累,推完全身每個酸累的地方,做事認真,待人热情,足時间,工作室乾淨整洁,所有客人都是一人一消毒一次性嘅用品,歡迎各位帅哥們当你感觉身體疲累時,需要给全身养生按摩時請提早預約Miko給你服务,☎️67307670或用TG联絡🫶工作室属于樓上骨地址長沙灣青山道277号三樓CI室,長沙灣地鉄CI出來直接行到第二路口7-11轉左行,楼下琪藝地產旁邊蓝色楼梯上三樓CI室🙇‍♀✨敬請留意各位帥哥們早段時間11點一3點要提早一天预约喔🙇‍♀🙏

2 Aug 2026, 03:24 UTC130 viewsread 8 August 2026

早上好呀🫶又要做牛馬的一天上班去💪有需要养生按摩的可以提早约我呀🥰🙇‍♀

28 Jul 2026, 04:34 UTC213 viewsread 8 August 2026
Photo

各位帥哥們中午好呀👋miko今天上班呀,歡迎预约🙇‍♀😊

Showing the 12 most recent of 20 posts we hold for @mikomass. 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 2 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 3 October 2026 — this entry's latest reading, not the date you are reading this.

“Miko💞開心工作坊💞(長沙灣)” (@mikomass), 704 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/mikomass.

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.