Yumi (ゆみ) 164CM 47KG Fcup 26y Japanese (日本) 🇯🇵 出勤地區:Tōkyō/東京 📆一對一專線 TG :@TOKYOyz Line:https://line.me/ti/p/rVqbPaYk_t Wechat:LINYUEN90 WhatsApp:+81 70-9200-9692
👍1

Channel
@JPCCha
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
1,238subscribers
-23 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002282072352 |
|---|---|
| Type | Channel |
| Username | @JPCCha |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 27 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 27 August 2026 |
| On Telegram | t.me/JPCCha |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Aug 2026, 21:24 | 1,238 | -3 |
| 25 Aug 2026, 04:16 | 1,241 | -6 |
| 22 Aug 2026, 00:14 | 1,247 | -3 |
| 18 Aug 2026, 08:12 | 1,250 | -1 |
| 15 Aug 2026, 03:16 | 1,251 | -3 |
| 11 Aug 2026, 22:11 | 1,254 | -5 |
| 8 Aug 2026, 13:11 | 1,259 | -2 |
| 7 Aug 2026, 22:48 | 1,261 | no change |
| 7 Aug 2026, 14:13 | 1,261 | first reading |
16 posts held, back to 28 April 2025 — 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 pageof 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 16 posts for this entry, the most recent from 10 November 2025. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
17 reactions across 8 posts, in 3 distinct kinds. The most used accounts for 47.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 8 | 47.1% | |
| 🥰 | 7 | 41.2% | |
| 👍 | 2 | 11.8% |
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 9 of the 16 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 17reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 28 April 2025 to 10 November 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Yumi (ゆみ) 164CM 47KG Fcup 26y Japanese (日本) 🇯🇵 出勤地區:Tōkyō/東京 📆一對一專線 TG :@TOKYOyz Line:https://line.me/ti/p/rVqbPaYk_t Wechat:LINYUEN90 WhatsApp:+81 70-9200-9692
👍1
Hazuki (はづき) 163CM 45KG Ecup 25y Japanese (日本) 🇯🇵 出勤地區:Tōkyō/東京 📆一對一專線 TG :@TOKYOyz Line:https://line.me/ti/p/rVqbPaYk_t Wechat:LINYUEN90 WhatsApp:+81 70-9200-9692
❤1
Today’s client was very polite and respectful. He mentioned that the girl looked even prettier in person, a bit shy at first but quickly warmed up — their time together was relaxing and sweet. He later messaged saying, “She was very gentle and made me feel relaxed.” Such kind feedback always makes us happy 💗
明日起大阪可約 Available for booking in Osaka starting tomorrow.
❤2
AV女優報班可預約~有興趣可問價!G奶緊穴 超高配合度~態度超讚可趴窗前抽插~ @TOKYOyz AV actress available for booking~ Ask for the price if interested! G-cup, tight pussy, extremely high cooperation~ Amazing attitude, can do thrusting by the window~
❤1🥰1
🇯🇵Tokyo-绅士约会🇯🇵 pinned «Available for delivery to: #Chiyoda Ward #Chūō Ward #Minato Ward #Shinjuku Ward #Bunkyo Ward #Shinagawa Ward #Meguro Ward #Shibuya Ward #Nakano Ward #Toshima Ward #Kita Ward #Taito Ward #Sumida Ward #Koto Ward #Arakawa Ward #Adachi Ward Not available: …»
Photo, posted without a caption
穿高跟鞋面試真的累死了🥲此刻隨地大小坐
❤2🥰2
猜猜我在哪里
想約晚上的 記得提前預約喲
https://t.me/TOKYOyz
營業中 14:00~23:30 Our business hours are from 2:00 PM to 11:30 PM. Feel free to contact me anytime during this period!
❤1
Showing the 12 most recent of 16 posts we hold for @JPCCha. 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 27 August 2026 — this entry's latest reading, not the date you are reading this.
“🇯🇵Tokyo-绅士约会🇯🇵” (@JPCCha), 1,238 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/JPCCha.
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.