Channel
@LoveClub999
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
889subscribers
+772 since we began measuring on 12 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004313580300 |
|---|---|
| Type | Channel |
| Username | @LoveClub999 |
| Created | Between 1 June 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 September 2026 |
| Last confirmed live | 28 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 28 September 2026 |
| On Telegram | t.me/LoveClub999 |
Other / unclassifiable — 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 28 September 2026 and assigned it the closest of 31 fixed categories, at 77% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Sept 2026, 12:15 | 889 | +754 |
| 14 Sept 2026, 07:00 | 135 | +18 |
| 12 Sept 2026, 21:22 | 117 | first reading |
13 posts held, back to 3 September 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.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 1 of 5 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 12 September 2026 |
|---|---|
| Posts held | 13 (3 September 2026 – 12 September 2026) |
| Views total | 2,112 |
| Reactions total | 0 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Sept 2026, 21:22 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Measured directly from 10 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.
🫠周六小周末，给自己的身心放个假！ 30多位高质量佳丽在线待命，沉浸式角色场景模拟，情绪价值瞬间拉满！妹子技术好、姿势到位，温柔体贴包您满意。 现场自由度高，看中哪个选哪个。周六黄金档期，好妹子不等人，今晚赶紧约上兄弟一起来！ 👠#广州会所#广州水会#广州水汇#广州93场#广州94场#全裸 📍(地址：广州北站&花都站附近 ————————— 电报预约：@JimTonyOK 双向联系：@KeXin9966_bot ☎️预约：15622843508
即使您为了一时的妥协，选择了其他技师，但终有一天，你也可以听到属于您的那一句： 尊贵的客人，88号技师很高兴为你服务，愿我们的号码手牌抚慰你的身体与精神 一按解百泛，二柔抚干愁，三推清万优 愿你归来仍是少年，无论你归来的路多么坎坷，您无需多言，忘却身外事 88号懂你 #广州会所#广州花都#广州北站#广州水汇#广州94 ❤️预约享优惠: @JimTonyOK 🌍：KEXIN9988996688 ☎️：15622843508
#广州会所#广州花都#广州北站#广州水汇#广州94 自己躺在床上，硬的睡不着，那就不要硬睡了 妹子在房间等你来谈大项目呢，好几亿的那种，想单独邀你参加！ 项目内容丰富，全裸艳舞，莞式水疗一条龙服务，让你物超所值，回味无穷 ❤️预约享优惠: @JimTonyOK 🌍：KEXIN9988996688 ☎️：15622843508
周二晚上，给自己的身心放个假！ 【豪华实体大店】为您打造专属温柔乡，环境私密安全靠谱不踩坑。 30多位高质量佳丽在线待命，沉浸式角色场景模拟，情绪价值瞬间拉满！妹子技术好、姿势到位，温柔体贴包您满意。 现场海选自由度高，看中哪个选哪个。好妹子不等人，今晚赶紧约上兄弟一起来！ #广州 #广州花都 #广州北站 #广州94 #花都94#广州会所 🐱电报预约：@JimTonyOK 🐱电话预约：15622843508
💆♂️服务内容: 9⃣️3⃣️👉泰式按摩，👙诱惑，调情，🐻推，👄吸，漫游，高山流💦，🐻出。 9⃣️4⃣️…5⃣️👉泰式按摩，👙诱惑，全 luo 舞㊙️，调情，🐻推，👄吸，漫游，高山流💦，69互动，👄🥚，👄棍，🦵夹，老汉推🚗，🐻出。 预约联系：@JimTonyOK ☎️：15622843508
💡学会享受放松，才是对自己最好的爱！💆♂️ 🏢 【广州核心大店 · 业界标杆】 我们始终坚守三大核心原则： 🔒 安全第一 —— 隐私保障，靠谱不踩坑！ 🌟 质量第一 —— 萝莉御姐，各种类型任君选择！ 🤝 客户第一 —— 【选好满意再消费】！ 专属管家全程跟进安排到位，技术过硬，情绪价值拉满！ 🔒 靠谱指数：⭐️⭐️⭐️⭐️⭐️ 💗 治愈指数：⭐️⭐️⭐️⭐️⭐️ 👇 *今晚过来，享受属于你的尊贵犒劳~* #广州 #广州94 #花都94#广州水会 详情预约：@JimTonyOK 客服在线时间：下午14点-凌晨3点（需提前预约）
Photo, posted without a caption
「 工作很忙 ｜ 别忘了及时回血 」 结束了一周的忙碌 焦躁、烦闷、不顺心？ 今夜Call 我让生活重新回到巅峰状态😍😍😍 💋预约联系：@JimTonyOK
广州首家94.5会所 pinned a photo
会所设施齐全，24小时免费提供停车过夜，提供大型恒温泡池、干蒸汗蒸，一天4顿自助餐+水果饮料、网吧、桌球室、乒乓球，2人以上预约可免费享受VIP休息室&棋牌室 预约联系：@JimTonyOK
#广州会所 #广州水疗 #广州94 #花都会所#花都94#广州北站#广州白云机场 城市车马喧嚣，总要有一处只属于自己的静谧包厢。特调天然精油缓缓浸润肌理，恰到好处的力道揉开紧绷的筋骨，关掉外界所有消息提醒，这一刻，只取悦自己 。 最好的犒赏，从来不是奢侈品堆砌，而是留一段完整时间，在私密SPA空间里，让紧绷的神经慢慢舒展，身心被温柔包裹，重启满格状态。 暖光、静音地毯、专属香氛、独立泡池……隔绝所有纷扰，沉浸式疗愈，把连日积攒的压力尽数释放。 😜咨询预约客服: @JimTonyOK
所有上钟客户可免费享受会所全部设施💋
Showing the 12 most recent of 13 posts we hold for @LoveClub999. 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.
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.
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 28 September 2026 — this entry's latest reading, not the date you are reading this.
“广州首家94.5会所” (@LoveClub999), 889 subscribers as measured 28 September 2026. Telegram Register, tgregister.com/channel/LoveClub999.
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.