Telegram RegisterThe public register of Telegram
Telegram profile photo for 日本 東京大阪出張「初戀館」出勤名單

Channel

日本 東京大阪出張「初戀館」出勤名單

@KKTokyo

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

2,495subscribers

+55 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002350671484
TypeChannel
Username@KKTokyo
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 8 September 2026
On Telegramt.me/KKTokyo

Growth

2,4392,4952,4678 August 2026 — 2,440 subscribers8 August 2026 — 2,440 subscribers9 August 2026 — 2,439 subscribers11 August 2026 — 2,440 subscribers14 August 2026 — 2,442 subscribers17 August 2026 — 2,445 subscribers21 August 2026 — 2,448 subscribers24 August 2026 — 2,453 subscribers28 August 2026 — 2,460 subscribers30 August 2026 — 2,462 subscribers3 September 2026 — 2,493 subscribers8 September 2026 — 2,495 subscribers8 August 20268 September 2026
12 measurements spanning 31 days, net +55. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 2,431–2,503 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Sept 2026, 08:182,495+2
3 Sept 2026, 01:472,493+31
30 Aug 2026, 20:342,462+2
28 Aug 2026, 01:072,460+7
24 Aug 2026, 21:042,453+5
21 Aug 2026, 00:052,448+3
17 Aug 2026, 19:562,445+3
14 Aug 2026, 20:262,442+2
11 Aug 2026, 18:552,440+1
9 Aug 2026, 02:122,439-1
8 Aug 2026, 02:302,440no change
8 Aug 2026, 02:212,440first reading

Engagement

11 posts held, back to 28 July 2026the 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 11 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1100.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 3 of the 11 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 11 most recent posts we hold, published 28 July 2026 to 7 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.

Recent posts

7 Aug 2026, 11:16 UTC101 viewsread 8 August 2026
Photo

🇯🇵日本 【高級尤物出張】 編號:937 身材:162.47.E.22歲 價格:60,000 超正 皮膚白皙胸部挺拔 性格活潑 情趣十足的嫩妹 🤩 東京班表: @KKTokyo 🤩 大阪班表: @osay1 🌐 加 LINE: ky565 🌐 密Hitomi: @hitom59 ⭐ 加Gleezy: hitom59 🥰 網站班表: www.hitom59.com

29 Jul 2026, 09:45 UTC520 views1 reactionsread 8 August 2026
Forwarded from @osay1Photo

🇯🇵 大阪【出張服務】 編號:190 身材:165.50.F.24歲 價格:49,000 性格很活潑,笑起來也很可愛,服務很好哦,尺度也很大~~ 🤩🤩🤩🤩🤩🤩🤩🤩 🤩 東京班表: @KKTokyo 🤩 大阪班表: @osay1 🌐 加 LINE: ky565 ⭐ 加Gleezy: hitom59 🌐 密Hitomi: @hitom59

1

29 Jul 2026, 09:41 UTC416 viewsread 8 August 2026
Photo

🇯🇵 東京【出張服務】 編號:936 身材:162.47.C.22歲 價格:40,000 女大兼職 聲音好聽 穴緊水多 🤩🤩🤩🤩🤩🤩🤩🤩 🤩 東京班表: @KKTokyo 🤩 大阪班表: @osay1 🌐 加 LINE: ky565 ⭐ 加Gleezy: hitom59 🌐 密Hitomi: @hitom59

29 Jul 2026, 09:39 UTC≈1,410 viewsread 8 August 2026
Photo

🇯🇵 東京【出張服務】 編號:982 身材:160.50.F.23歲 價格:50,000 巨乳奶媽清純畢業生,長得漂亮身材好 🤩🤩🤩🤩🤩🤩🤩🤩 🤩 東京班表: @KKTokyo 🤩 大阪班表: @osay1 🌐 加 LINE: ky565 ⭐ 加Gleezy: hitom59 🌐 密Hitomi: @hitom59

28 Jul 2026, 09:23 UTC392 viewsread 8 August 2026

幫台灣的好朋友推薦一下 造福在台灣的哥哥們 她是專門做介紹台灣女生的 專業介紹的口碑茶姐👍 🎂 花名冊 https://t.me/+JPhKk9b1LKFjOGU1

28 Jul 2026, 08:21 UTC310 viewsread 8 August 2026
Forwarded from @osay1Photo

🇯🇵 大阪 【出張服務】 編號:154 身材:160.55.G.28 價格:39,000 氣質輕熟女 享受刺激感 會很主動的扒光你 主動刺激好玩 尺度大配合度高 大戰三百回合都不嫌夠 🤩 東京班表: @KKTokyo 🤩 大阪班表: @osay1 🌐 加 LINE: ky565 🌐 密Hitomi: @hitom59 ⭐ 加Gleezy: hitom59 🥰 網站班表: www.hitom59.com

28 Jul 2026, 07:59 UTC347 views0 reactionsread 8 August 2026
Photo

🇯🇵 東京【出張服務】 編號:931 身材:166.52.D.25歲 價格:35,000 高挑氣質 豐滿不胖 口技超級好妹妹 很喜歡上搖 🤩🤩🤩🤩🤩🤩🤩🤩 🤩 東京班表: @KKTokyo 🤩 大阪班表: @osay1 🌐 加 LINE: ky565 ⭐ 加Gleezy: hitom59 🌐 密Hitomi: @hitom59

Showing the 11 most recent of 11 posts we hold for @KKTokyo. 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.

Forward network

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.

Mentions

Named by 2 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.

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.

Cite this entry

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 September 2026 — this entry's latest reading, not the date you are reading this.

“日本 東京大阪出張「初戀館」出勤名單” (@KKTokyo), 2,495 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/KKTokyo.

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.