Channel
@kk555pp
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
26subscribers
+1 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003297561917 |
|---|---|
| Type | Channel |
| Username | @kk555pp |
| Created | Between 1 October 2025 and 28 February 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 10 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 3 times, most recently 10 September 2026 |
| On Telegram | t.me/kk555pp |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Aug 2026, 05:17 | 26 | +2 |
| 18 Aug 2026, 05:52 | 24 | -1 |
| 11 Aug 2026, 09:31 | 25 | no change |
| 11 Aug 2026, 02:17 | 25 | first reading |
10 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 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 10 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.0% |
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 1 of the 10 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 5 August 2026 to 11 August 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.
🌸番號781 167cm●Eップ●48kg●22歲 ●出勤エリア： 東京 / tokyo 優しいお姉さん系の雰囲気で、普段は仕事で忙しくしています。 まだ知らないことも多く、これからいろいろな魅力を引き出していけそうなタイプ。 素直で聞き分けがよく、照れるとすぐ顔が赤くなるのがとても可愛いです。 色白で綺麗なルックスも魅力的。 親しみやすさと大人っぽい色気をあわせ持つ、魅力的な女の子です ⭐️Gleezy：yeee11 ⭐️ TG：@momo113 ⭐️ LINE： yee116 ✧⋄⋆⋅ ご案内・お問い合わせ ⋅⋆⋄✧ 総合窓口：@UZ_36365 東京の女の子：@kk555pp 大阪の女の子：@jp8889 小桜の日記：@yokotk85 新手の必看：@like86777
🌸番號782 156cm●Dップ●47kg●22歲 ●出勤エリア： 東京 / tokyo 近所のお姉さんのような親しみやすさが魅力の、可愛くて清楚なタイプ。 一緒にいると自然体でいられて、気取らない雰囲気がとても魅力的です。 小柄で抱きしめやすく、可愛らしい雰囲気の中にも女性らしい色気があります。 距離が縮まるほど、さらに魅力的な一面を見せてくれる女の子です ⭐️Gleezy：yeee11 ⭐️ TG：@momo113 ⭐️ LINE： yee116 ✧⋄⋆⋅ ご案内・お問い合わせ ⋅⋆⋄✧ 総合窓口：@UZ_36365 東京の女の子：@kk555pp 大阪の女の子：@jp8889 小桜の日記：@yokotk85 新手の必看：@like86777
🌸番號783 162cm●Dップ●50kg●25歲 ●出勤エリア： 東京 / tokyo 甘くて可愛らしい笑顔に思わず心を奪われる、魅力たっぷりの女の子。 どんな衣装もさらりと着こなし、しなやかで色気のある仕草がとても印象的です。 甘さと大人っぽさを兼ね備えた、惹きつけられるような魅力の持ち主。 どの角度から見ても絵になるほど魅力的で、ベッドではさらに大胆な一面を見せてくれます ⭐️Gleezy：yeee11 ⭐️ TG：@momo113 ⭐️ LINE： yee116 ✧⋄⋆⋅ ご案内・お問い合わせ ⋅⋆⋄✧ 総合窓口：@UZ_36365 東京の女の子：@kk555pp 大阪の女の子：@jp8889 小桜の日記：@yokotk85 新手の必看：@like86777
🌸番號784 162cm●Dップ●48kg●21歲 ●出勤エリア： 東京 / tokyo 優しいお姉さん系の雰囲気で、普段は仕事で忙しくしています。 まだ知らないことも多く、これからいろいろ開発していけそうなタイプ。 素直で聞き分けがよく、照れるとすぐ顔が赤くなるのがとても可愛いです。 色白で綺麗なルックスも魅力的な女の子です。 ちなみに、スタイルだけでなく、かなり魅力的だと評判ですよ ⭐️Gleezy：yeee11 ⭐️ TG：@momo113 ⭐️ LINE： yee116 ✧⋄⋆⋅ ご案内・お問い合わせ ⋅⋆⋄✧ 総合窓口：@UZ_36365 東京の女の子：@kk555pp 大阪の女の子：@jp8889 小桜の日記：@yokotk85 新手の必看：@like86777
🌸番號785 163cm●Eップ●49kg●26歲 ●出勤エリア： 東京 / tokyo スタイルのバランスが良く、色気のある魅力的な女性。 セクシーな雰囲気と華やかなルックスが印象的で、距離が縮まるほど魅力を感じられるタイプです。 積極的でノリも良く、一緒に楽しい時間を過ごせるのが魅力。 大人っぽい色気と可愛らしさを兼ね備えた、理想の恋人のような女の子です ⭐️Gleezy：yeee11 ⭐️ TG：@momo113 ⭐️ LINE： yee116 ✧⋄⋆⋅ ご案内・お問い合わせ ⋅⋆⋄✧ 総合窓口：@UZ_36365 東京の女の子：@kk555pp 大阪の女の子：@jp8889 小桜の日記：@yokotk85 新手の必看：@like86777
🌸番號786 160cm●Cップ●47kg●23歲 ●出勤エリア： 東京 / tokyo 見た目はとても素直で清純な雰囲気。性格も優しくて、素直に合わせてくれるタイプ。 でも、スイッチが入ると一気に甘えん坊になって、あなたにベッタリ♡ 普段とのギャップがたまらない、ちょっぴり小悪魔な女の子。 あなたにたっぷり可愛がってもらうのを待っています~ ⭐️Gleezy：yeee11 ⭐️ TG：@momo113 ⭐️ LINE： yee116 ✧⋄⋆⋅ ご案内・お問い合わせ ⋅⋆⋄✧ 総合窓口：@UZ_36365 東京の女の子：@kk555pp 大阪の女の子：@jp8889 小桜の日記：@yokotk85 新手の必看：@like86777
🌸番號779 158cm●Gップ●46kg●23歲 ●出勤エリア： 東京 / tokyo サービスにも積極的で、ノリも抜群 ちょっとムッツリな性格で、夜は一人でAVを観ながら楽しんでいることも…… ⭐️Gleezy：yeee11 ⭐️ TG：@momo113 ⭐️ LINE： yee116 ✧⋄⋆⋅ ご案内・お問い合わせ ⋅⋆⋄✧ 総合窓口：@UZ_36365 東京の女の子：@kk555pp 大阪の女の子：@jp8889 小桜の日記：@yokotk85 新手の必看：@like86777
🌸番號780 158cm●Dップ●46kg●24歲 ●出勤エリア： 東京 / tokyo 相手とのやり取りが上手で、積極的にリードしてくれるタイプ 上になると動きも上手で、耳元で優しく息を漏らす仕草も魅力的 英語も流暢で、コミュニケーションもスムーズです。 ⭐️Gleezy：yeee11 ⭐️ TG：@momo113 ⭐️ LINE： yee116 ✧⋄⋆⋅ ご案内・お問い合わせ ⋅⋆⋄✧ 総合窓口：@UZ_36365 東京の女の子：@kk555pp 大阪の女の子：@jp8889 小桜の日記：@yokotk85 新手の必看：@like86777
🌸番號778 167cm●Eップ●48kg●22歲 ●出勤エリア： 東京 / tokyo 吸うのも、咥えるのも、舐めるのもとっても上手♡ 初めて会ったときは少し恥ずかしがり屋だけど、ベッドに入ると一気に積極的になっちゃうタイプ ⭐️Gleezy：yeee11 ⭐️ TG：@momo113 ⭐️ LINE： yee116 ✧⋄⋆⋅ ご案内・お問い合わせ ⋅⋆⋄✧ 総合窓口：@UZ_36365 東京の女の子：@kk555pp 大阪の女の子：@jp8889 小桜の日記：@yokotk85 新手の必看：@like86777
🌸番號777 158cm●Eップ●46kg●23歲 ●出勤エリア： 東京 / tokyo 可愛らしいルックスに、小柄で愛嬌たっぷり。肌もきれいで、サービス精神も抜群です。 とても話しやすくて親しみやすく、リクエストにも柔軟に対応してくれる女の子です。 ⭐️Gleezy：yeee11 ⭐️ TG：@momo113 ⭐️ LINE： yee116 ✧⋄⋆⋅ ご案内・お問い合わせ ⋅⋆⋄✧ 総合窓口：@UZ_36365 東京の女の子：@kk555pp 大阪の女の子：@jp8889 小桜の日記：@yokotk85 新手の必看：@like86777
❤1
Showing the 10 most recent of 10 posts we hold for @kk555pp. 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 4 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.
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 25 August 2026 — this entry's latest reading, not the date you are reading this.
“夢色館|東京デリヘル|素人” (@kk555pp), 26 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/kk555pp.
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.