30 Jul 2026, 02:34 UTC46 viewsread 8 August 2026
Video
Video, posted without a caption
Channel
🇯🇵日本Tokyo & Osaka外送茶外卖上门服务
@jpasaka
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
1,026subscribers
-1 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 | -1002834520441 |
|---|---|
| Type | Channel |
| Username | @jpasaka |
| Created | Between 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/jpasaka |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 11:44 | 1,026 | +1 |
| 27 Aug 2026, 17:24 | 1,025 | -1 |
| 25 Aug 2026, 00:15 | 1,026 | +2 |
| 15 Aug 2026, 18:58 | 1,024 | -2 |
| 11 Aug 2026, 22:22 | 1,026 | -1 |
| 8 Aug 2026, 21:20 | 1,027 | no change |
| 8 Aug 2026, 00:31 | 1,027 | first reading |
Engagement
14 posts held, back to 27 June 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 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 14 posts for this entry, the most recent from 30 July 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 13s
- Average length
- 13s
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.
Recent posts
30 Jul 2026, 02:34 UTC46 viewsread 8 August 2026
螃蟹夾到他的奶子 好痛唷~
30 Jul 2026, 02:34 UTC46 viewsread 8 August 2026
Sticker
Sticker, posted without a caption
30 Jul 2026, 02:34 UTC37 viewsread 8 August 2026
Photo
怎麼說的這麼棒呢 ~ 果然是星家軍
30 Jul 2026, 02:34 UTC42 viewsread 8 August 2026
Photo
第一次配合的弟弟 從剛開始說想要體驗一小時 因為相信星星直接兩小時安排 又是收穫滿滿的一天 謝謝弟弟的信任❤️
30 Jul 2026, 02:34 UTC36 viewsread 8 August 2026
Photo
从去年认识到现在，因为各种原因一直没能成功预约。 一年后，他终于来到日本。等待了这么久，这次终于成功见面，当然要安排双飞，给这段等待画上一个完美的句号 #日本外送茶 #東京外送茶 #日本暗黑外送 #東京外約 #東京風俗 #東京デリヘル
30 Jul 2026, 02:34 UTC32 viewsread 8 August 2026
Photo
星VIP俱樂部預約流程 ① 告知需求 提供所在城市、國家、喜歡的女孩類型、預約時間及預算。 ② 提供酒店資訊 確認人選後，提供酒店名稱、地址及房號（未訂酒店可協助推薦）。 ③ 確認預約 確認女孩檔期，並發送預約確認。如需更換人選或調整時間，可於此階段提出。 ④ 入住通知 請於預約前完成入住，並提供房號及入住證明（房卡或酒店外觀照片）。 ⑤ 女孩出發 女孩抵達酒店後會通知您；如酒店需接送，請至大廳迎接。 ⑥ 現場付款 確認無誤後，以現金（日幣）付款，即可開始服務。 全程無訂金｜無隱藏費用｜安全保密 #東京デリヘル #東京叫小姐 #東京援交 #東京出張 #東京デリヘル派遣 #東京外送小姐 #外送茶 #外送小姐 #真人照片
30 Jul 2026, 02:34 UTC34 viewsread 8 August 2026
Photo
星VIP俱樂部｜店長星星想跟大家說 星VIP俱樂部的每位女生，都是本人實拍照片，不會使用假照片或盜圖來欺騙客人。當然，女生每天的穿搭、妝容、髮型都可能不同，所以實際見面時，多少會和照片有些自然的差異，但本人絕對就是本人，這點請大家放心。 很多哥哥會問星星，為什麼要提供房卡、房號、入住照片、飯店外觀等資訊？ 其實這並不是不信任客人，而是希望在保障客人安全的同時，也能保障女生的安全。星星希望每一次安排都是真實、安全、安心的，讓雙方都能放心赴約。 不少加進來的客人因為信任星星，都會主動配合提供入住資訊，我們也會嚴格保護所有客人的個人隱私，不會外流任何資料，請大家放心。 信任是雙向的。 星星會盡全力保障每一位客人的權益，也希望哥哥們能給女生一份安心與尊重。只有彼此理解、互相配合，才能擁有一次愉快又美好的約會體驗。 🙏 謝謝每一位支持與信任星VIP俱樂部的哥哥，星星會繼續秉持誠信經營，為大家提供更安心、更優質的服務。 #東京デリヘル…
29 Jun 2026, 13:07 UTC113 viewsread 8 August 2026
https://t.me/JPCNV
29 Jun 2026, 08:53 UTC105 viewsread 8 August 2026
本频道的哥哥们 能不能主动私信星星 星星有个秘密要跟你们说 @jpkai7
28 Jun 2026, 08:43 UTC59 viewsread 8 August 2026
Forwarded from @jpkai8Photo
哥哥上个月就和星星约好这个月来东京，没想到到了月中又因为工作安排突然被打乱，一度还以为这次见不到了🥺。好在经历了一波三折，最后还是顺利来到东京啦！ 真的很开心哥哥一直都没有忘记星星，每次来日本都会提前联系、提前预约 也希望这次能再次给哥哥留下美好的回忆。 中國語|日本語|English ⭐Gleezy：JP88 📱Telgram：jpkai7 📱Discord：jpkai7 頻道總覽 🎀官方網站
28 Jun 2026, 08:43 UTC97 viewsread 8 August 2026
Forwarded from @jpkai8Photo
关于「星VIP俱乐部」的几点说明，哥哥们看过来 🙋♂️ 🟥Q1：星VIP俱乐部会有外籍冒充日本女生的情况吗？ 星星这边跟各位哥哥们说一下唷～星VIP俱乐部只有正宗的日本女生，没有任何外籍冒充的情况。非常理解有些哥哥之前在别家店或者被拉客的骗过，说好是日本人，结果到了发现不是，这种感受真的很差！星VIP俱乐部保证，全部都是日本女生兼职，没有外籍，请哥哥们放心。 🟥Q2：需要付定金或预约金吗？ 星星可以很明确地告诉各位：完全不用！ 在见到女生之前，不需要预付任何一分钱。见到女生本人后，满意了再现金交易。相反的，如果哪家店要求先付预约金或定金的，哥哥们一定要认真筛选，千万不要钱付了结果被人封锁——之前也有哥哥遇到过这种情况。星VIP俱乐部是线上直接选妹，喜欢就下单，女生直接过去，方便又安心。 🟥Q3：付款方式是什么？ 只接受日元现金交易，不接受其他国家的纸币，也不支持转账或刷卡，请哥哥们提前准备好哦～ 中國語|日本語|En…
Showing the 12 most recent of 14 posts we hold for @jpasaka. 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.
Citation-graph rank
Citation-graph rank — 76,276 of 1,627,445entries 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.
Forward network
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.
Mentions
Named by 3 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.
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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“🇯🇵日本Tokyo & Osaka外送茶外卖上门服务” (@jpasaka), 1,026 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/jpasaka.
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.