哈喽,哥哥,福永新上线老师啦🏋♂️🏋♂️🏋♂️,胸型白嫩,非常给力哦,喜欢的哥哥直接约哈🎟🎟🎟
Signed 深圳泡澡 半裸抓龙筋工作室

Channel
@shiya666
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
5,291subscribers
-210 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001927689630 |
|---|---|
| Type | Channel |
| Username | @shiya666 |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 8 November 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 8 November 2026 |
| On Telegram | t.me/shiya666 |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 86% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Nov 2026, 23:56 | 5,291 | -5 |
| 6 Nov 2026, 02:37 | 5,296 | -5 |
| 2 Nov 2026, 23:55 | 5,301 | -13 |
| 30 Oct 2026, 20:27 | 5,314 | -6 |
| 28 Oct 2026, 02:46 | 5,320 | -6 |
| 25 Oct 2026, 12:46 | 5,326 | -9 |
| 22 Oct 2026, 10:56 | 5,335 | -4 |
| 19 Oct 2026, 08:06 | 5,339 | -5 |
| 16 Oct 2026, 04:00 | 5,344 | -5 |
| 13 Oct 2026, 08:00 | 5,349 | -21 |
| 6 Oct 2026, 18:36 | 5,370 | -11 |
| 29 Sept 2026, 16:39 | 5,381 | -29 |
| 16 Sept 2026, 05:18 | 5,410 | -8 |
| 12 Sept 2026, 09:19 | 5,418 | -11 |
| 8 Sept 2026, 12:18 | 5,429 | -2 |
| 3 Sept 2026, 08:58 | 5,431 | -2 |
| 31 Aug 2026, 01:34 | 5,433 | -8 |
| 27 Aug 2026, 16:57 | 5,441 | -7 |
| 25 Aug 2026, 00:57 | 5,448 | -10 |
| 21 Aug 2026, 21:08 | 5,458 | first reading |
7 posts held, back to 24 June 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 6 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 7 posts for this entry, the most recent from 30 July 2026. An engagement rate over an empty window would be a number about nothing.
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.
9 reactions across 6 posts, in 2 distinct kinds. The most used accounts for 88.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🥰 | 8 | 88.9% | |
| ❤ | 1 | 11.1% |
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 6 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 9 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 24 June 2026 to 30 July 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.
哈喽,哥哥,福永新上线老师啦🏋♂️🏋♂️🏋♂️,胸型白嫩,非常给力哦,喜欢的哥哥直接约哈🎟🎟🎟
Signed 深圳泡澡 半裸抓龙筋工作室
🚊🚊🚊各位哥哥,周末愉快!宝安中心宝民一路喜来登酒店新上任两位老师非常给力😊😊😊喜欢的哥哥可以直接约哈,瑶浴泡澡搓澡,抓龙筋养护🏋♂️🏋♂️🏋♂️
❤1
Signed 深圳泡澡 半裸抓龙筋工作室
🚊🚊🚊好消息,各位哥哥福永龙筋馆做一个星期7天活动啦🏋♂️🏋♂️🏋♂️时间(7月19日-7月25日止)为期七天活动,活动期间全场项目8折优惠🎟🎟🎟有在宝安福永附近的哥哥可以直接预定啦🧀🧀🧀
🥰3
Signed 深圳泡澡 半裸抓龙筋工作室
😊)宝安福永新人上线,零零后静静老师身材棒👍🏻妥妥的大长腿🦵🏻,再加上两颗圆韵丰满的凶器,非常给力,喜欢的哥哥直接约哈🤠🤠龙筋走起👌🏻
🥰1
Signed 深圳泡澡 半裸抓龙筋工作室
😊😊😊哈喽,哥哥,新人报道,双双老师在宝安洪浪北上课啦🍕🍕🍕双双老师身材给力,肤白貌美🎢🎢🎢
🥰2
Signed 深圳泡澡 半裸抓龙筋工作室
混血儿倩倩老师今天回来上课啦😊😊😊倩倩老师在宝安区宝民一路喜来登酒店上课哈🎢🎢🎢喜欢的直接约哟🍕🌭🌊🍝🥫
🥰1
Signed 深圳泡澡 半裸抓龙筋工作室
哈喽,哥哥,工作愉快,下班晚饭后直接约个龙筋保养哈😊😊😊
🥰1
Signed 深圳泡澡 半裸抓龙筋工作室
Showing the 7 most recent of 7 posts we hold for @shiya666. 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.
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 8 November 2026 — this entry's latest reading, not the date you are reading this.
“宝安💕00后抓龙筋.丝足.丝袜龟责” (@shiya666), 5,291 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/shiya666.
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.