Channel
@KissMMK888
On this record: Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Citations · Cite this entry
8,140subscribers
-1,288 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002050418711 |
|---|---|
| Type | Channel |
| Username | @KissMMK888 |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/KissMMK888 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 18:55 | 8,140 | -652 |
| 13 Aug 2026, 15:34 | 8,792 | -410 |
| 10 Aug 2026, 11:51 | 9,202 | -188 |
| 7 Aug 2026, 04:52 | 9,390 | -38 |
| 6 Aug 2026, 20:30 | 9,428 | no change |
| 6 Aug 2026, 20:19 | 9,428 | first reading |
29 posts held, back to 5 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 17 pagesof 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.
| Window | Rolling 30 days · latest post in window 17 August 2026 |
|---|---|
| Posts held | 29 (5 August 2026 – 17 August 2026) |
| Views total | 14,709 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 18 Aug 2026, 05:05 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.
Lifetime counters from Telegram’s own channel header, read 18 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
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.
🐰 广州天河 · 珠村地铁站 KISS · mmk 🐰 ➡️➡️ 周二 8月18 日 ➡️➡️ 🐾 嘉嘉 🐾 魅恋 418/h 🈳 16-19, 23-24 （软萌小甜妹，宝藏女孩，i人福音~） 🐾 丸子 🐾 魅恋 418/h 🈳 18-19, 23-24 （大一学妹，07年小御姐） 🐾 岁岁 🐾 魅恋 418/h 🈳 18-23 （短发邻家小甜妹，C🐻超有料） 📱定位：点我即可查看详细位置 🔜 预约联系：@GZkiss888 📱预约微信：gzyoumi999 📱无法私信的机器人留言： @GZkiss_bot ✔️海量报告频道：https://t.me/mmkBaoGao 💬恋爱交流群： https://t.me/GZkiss 📱恋爱位置：天河区珠村地铁站
🐰 广州天河 · 珠村地铁站 KISS · mmk 🐰 ➡️➡️ 周一 8月17 日 ➡️➡️ 🐾丹丹 🐾 魅恋 448/h 🈳 20-21, 23-24 （18岁反差小御姐，短期兼职） 🐾 炸串 🐾 魅恋 418/h 🈳 18-24 （蛇饱饱，甜妹，夸夸流情绪价值高，态度好） 📱定位：点我即可查看详细位置 📱恋爱位置：天河区珠村地铁站
🐰 广州天河 · 珠村地铁站 KISS · mmk 🐰 ➡️➡️ 周日 8月16 日 ➡️➡️ 🐾 菜菜 🐾 魅恋 468/h 🈵 （高颜甜妹，白的发光，人间小“田曦薇”） 🐾 鱼鱼 🐾 魅恋 448/h 🈵 （白皮少御，高颜主动，鱼鱼的腿，塞纳河畔的春水～） 🐾丹丹 🐾 魅恋 448/h 🈳 18-20 22-24 （18岁反差小御姐，短期兼职） 🐾 炸串 🐾 魅恋 418/h 🈳 19-24 （蛇饱饱，甜妹，夸夸流情绪价值高，态度好） 📱定位：点我即可查看详细位置 📱恋爱位置：天河区珠村地铁站
🐰 广州天河 · 珠村地铁站 KISS · mmk 🐰 ➡️➡️ 周五 8月14 日 ➡️➡️ 🐾 菜菜 🐾 魅恋 468/h 🈵 （高颜甜妹，白的发光，人间小“田曦薇”） 🐾 嘉嘉 🐾 魅恋 418/h 🈳 18-19, 20-23 （软萌小甜妹，宝藏女孩，i人福音~） 🐾 岁岁 🐾 魅恋 418/h 🈵 （短发邻家小甜妹，C🐻超有料） 🐾 曼曼 🐾 魅恋 418/h 🈳 19:30-24 （18岁女高，真女高，D🐻很白很大很软，大蟒蛇） 🐾 叙叙🐾 魅恋 418/h 🈳 19-21 （纯素人，邻家小妹，态度好） 📱定位：点我即可查看详细位置 🔜 预约联系：@GZkiss888 📱预约微信：gzyoumi999 📱无法私信的机器人留言： @GZkiss_bot ✔️海量报告频道：https://t.me/mmkBaoGao 💬恋爱交流群： https://t.
☺️嘉嘉☺️今日穿搭
曼曼今日穿搭 🈳16.30-24.00
🐰 广州天河 · 珠村地铁站 KISS · mmk 🐰 ➡️➡️ 周三 8月12 日 ➡️➡️ 🔝新人米米🔝 魅恋 448/h 🈳 21.30-01.00 （新人报道，报告返 20🧧） 🔝新人小杏🔝 魅恋 448/h 🈳 24-1 （新人报道，报告返 20🧧） 🐾 菜菜 🐾 魅恋 468/h 🈳 18.40-19.40 22.30-24.00 （高颜甜妹，白的发光，人间小“田曦薇”） 🐾小虎牙🐾 魅恋 448/h 🈳 16-20 21-22 （18岁高颜甜妹，跳舞超带劲儿~） 🐾 曼曼 🐾 魅恋 418/h 🈳 17-24 （18岁女高，真女高，D🐻很白很大很软，大蟒蛇） 🐾 炸串🐾 魅恋 418/h 🈳 16-24 （蛇饱饱，甜妹，夸夸流情绪价值高，态度好） 🐾叙叙🐾 魅恋 418/h 🈳 18-22 （纯素人，邻家小妹，态度好） …
🐰 广州天河 · 珠村地铁站 KISS · mmk 🐰 ➡️➡️ 周三 8月12 日 ➡️➡️ 🔝新人米米🔝 魅恋 448/h 🈳 19-1 （新人报道，报告返 20🧧） 🔝新人小杏🔝 魅恋 448/h 🈳 19-20, 24-1 （新人报道，报告返 20🧧） 🐾 菜菜 🐾 魅恋 468/h 🈳 18-24 （高颜甜妹，白的发光，人间小“田曦薇”） 🐾小虎牙🐾 魅恋 448/h 🈳 16-22 （18岁高颜甜妹，跳舞超带劲儿~） 🐾 曼曼 🐾 魅恋 418/h 🈳 16-24 （18岁女高，真女高，D🐻很白很大很软，大蟒蛇） 🐾 炸串🐾 魅恋 418/h 🈳 16-24 （蛇饱饱，甜妹，夸夸流情绪价值高，态度好） 🐾叙叙🐾 魅恋 418/h 🈳 17-22 （纯素人，邻家小妹，态度好） 📱定位：点我即可查看详细位置 🔜 预约联系：@GZ…
☺️海苔☺️今日穿搭
广州东圃—kiss女仆私影 pinned a photo
🐰 广州天河 · 珠村地铁站 KISS · mmk 🐰 ➡️➡️ 周二 8月11日 ➡️➡️ 🔝新人米米🔝 魅恋 448/h 🈵 （新人报道，报告返 20🧧） 🔝新人小杏🔝 魅恋 448/h 🈵 （新人报道，报告返 20🧧） 🐾 小紫 🐾 魅恋 468/h 🈵 （童颜巨乳小萝莉，胸C+） 🐾 海苔 🐾 魅恋 448/h 🈳 18-19，20-1 （元气少女回归！） 🐾 嘉嘉 🐾 魅恋 418/h 🈳 21-23 （软萌小甜妹，宝藏女孩，i人福音~） 🐾 炸串🐾 魅恋 418/h 🈳 19:30-24 （蛇饱饱，甜妹，夸夸流情绪价值高，态度好） 📱定位：点我即可查看详细位置 🔜 预约联系：@GZkiss888 📱预约微信：gzyoumi999 📱无法私信的机器人留言： @GZkiss_bot ✔️海量报告频道：https://t.me/mmkBaoGao 💬…
广州东圃—kiss女仆私影 pinned a photo
Showing the 12 most recent of 29 posts we hold for @KissMMK888. 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.
@KissMMK888 edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Citation-graph rank — 271,803 of 1,549,704entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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 16 August 2026 — this entry's latest reading, not the date you are reading this.
“广州东圃—kiss女仆私影” (@KissMMK888), 8,140 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/KissMMK888.
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.