Channel
@leikuncom
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Cite this entry
1,005subscribers
-1 since we began measuring on 16 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1004291654629 |
|---|---|
| Type | Channel |
| Username | @leikuncom |
| Created | Between 1 May 2026 and 18 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 15 September 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 11 October 2026 |
| On Telegram | t.me/leikuncom |
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 19 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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 |
|---|---|---|
| 11 Oct 2026, 07:16 | 1,005 | -2 |
| 4 Oct 2026, 23:59 | 1,007 | -1 |
| 25 Sept 2026, 15:00 | 1,008 | -2 |
| 15 Sept 2026, 16:22 | 1,010 | no change |
| 11 Sept 2026, 12:56 | 1,010 | +3 |
| 30 Aug 2026, 16:29 | 1,007 | +1 |
| 16 Aug 2026, 16:00 | 1,006 | first reading |
5 posts held, back to 18 August 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 5 posts for this entry, the most recent from 1 September 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.
🫣深圳顶级娱乐推荐😀 营业预约中 深圳会所全区 94-95-96预约安排 #罗湖 #福田 #宝安 #龙华 #龙岗 #光明 #南山 #深圳 在线预约中 🔥94服务流程：🐻推，👋推，🦶推，果冻漫游，吸皮过水，👅漫，鼻吸，海底捞月，等等项目流程，小妹🉑亲，🉑揉，🉑摸下路，👋🦶🐻出，价格：398-498 🔥95水会、会所：无套👄爆，花式毒龙，吃舔🥚🥚，玉指柔情，丝袜诱惑，无限挑逗，👅漫全身，🐻推全身，深🐒👄爆，等等项目内容，价格550-598 🔥96会所、公寓：梦幻联动，艳舞挑逗，吸🥚👅🥚，👄罐拔痧，美式、日式、英式毒🐉，倒挂金钩，🧊🔥吐珠，👅扫禁区，爱的魔力转圈圈，6️⃣9️⃣吃鲍，操盘花式👄爆出💦，价格750-800 选择佳丽：到现场选，不满意可以换，换到满意为止 以上服务时间94/60分钟95/70分钟96/80分钟（时间内都可出💦两次需提前跟客服 @leizongzai
Photo, posted without a caption
Video, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Showing the 5 most recent of 5 posts we hold for @leikuncom. 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 11 October 2026 — this entry's latest reading, not the date you are reading this.
“深圳全区最牛95” (@leikuncom), 1,005 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/leikuncom.
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.