Channel
@JPescort
On this record: Growth · Engagement · Posts · Citations · Cite this entry
4subscribers
+2 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004441556745 |
|---|---|
| Type | Channel |
| Username | @JPescort |
| Created | Between 1 June 2026 and 1 August 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/JPescort |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 21:48 | 4 | +1 |
| 16 Aug 2026, 21:36 | 3 | +1 |
| 13 Aug 2026, 19:35 | 2 | no change |
| 8 Aug 2026, 18:16 | 2 | first reading |
14 posts held, back to 1 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 pageof 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 10 August 2026 |
|---|---|
| Posts held | 14 (1 August 2026 – 10 August 2026) |
| Views total | 112 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Aug 2026, 19:35 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.
Yui-chan ♡ #Tokyo Height: 158cm | Bust: D-cup | Age: 21 Soft and cute little rabbit type～ When she smiles her eyes curve, her voice is super sweet, and she obediently listens to you～ (´∀｀)♡ Gentle yet proactive, the type you just want to keep holding～ 🌟 @GEM816 | 🌟 GEM816 📖 Beginner @Tokyo6651 🌟 中文版：@GEM8166 🌟 日文版 @Oppai4 #TokyoDelivery #OsakaDelivery #TokyoEscort #OsakaEscort #JapanOutcall #TokyoDeriheru #OsakaDe…
Akari-chan ♡ #Osaka Height: 162cm | Bust: E-cup | Age: 23 Pure college-girl vibe. Soft fair skin, a smile that’s super healing, and she’s really good at being clingy～ 🌟 @GEM816 | 🌟 GEM816 📖 Beginner @Tokyo6651 🌟 中文版：@GEM8166 🌟 日文版 @Oppai4 #TokyoDelivery #OsakaDelivery #TokyoEscort #OsakaEscort #JapanOutcall #TokyoDeriheru #OsakaDeriheru #JapanDelive
Mio-chan ♡ #Tokyo Height: 155cm | Bust: C-cup | Age: 19 Petite beauty! Small and cute, yet surprisingly skilled at service～ (๑•̀ㅂ•́)و✧ Watery eyes, just like a clingy little kitten～ 🌟 @GEM816 | 🌟 GEM816 📖 Beginner @Tokyo6651 🌟 中文版：@GEM8166 🌟 日文版 @Oppai4 #TokyoDelivery #OsakaDelivery #TokyoEscort #OsakaEscort #JapanOutcall #TokyoDeriheru #OsakaDeriheru #JapanDelive
Sakura-chan ♡ #Osaka Height: 160cm | Bust: D-cup | Age: 20 A fresh girl like cherry blossoms. Super sweet smile, and her skin is so white it almost glows～ ♡(´ε｀ ) She’ll take your hand on her own and is great at creating a sweet atmosphere～ 🌟 @GEM816 | 🌟 GEM816 📖 Beginner @Tokyo6651 🌟 中文版：@GEM8166 🌟 日文版 @Oppai4 #TokyoDelivery #OsakaDelivery #TokyoEscort #OsakaEscort #JapanOutcall #TokyoDeriheru #OsakaDeriheru #Jap…
Hina-chan ♡ #Tokyo Height: 165cm | Bust: F-cup | Age: 24 Tall and curvy mature type. Elegant and refined, yet surprisingly playful～ (≧▽≦) Her low, sexy voice makes it easy to lose yourself～ 🌟 @GEM816 | 🌟 GEM816 📖 Beginner @Tokyo6651 🌟 中文版：@GEM8166 🌟 日文版 @Oppai4 #TokyoDelivery #OsakaDelivery #TokyoEscort #OsakaEscort #JapanOutcall #TokyoDeriheru #OsakaDeriheru #JapanDelive
Emi-chan ♡ #Osaka Height: 168cm | Bust: G-cup | Age: 25 A tall, busty overwhelming beauty… but her aura is surprisingly gentle～ (✧ω✧) She’ll wrap those long legs around you, and her service sense is incredibly strong～ 🌟 @GEM816 | 🌟 GEM816 📖 Beginner @Tokyo6651 🌟 中文版：@GEM8166 🌟 日文版 @Oppai4 #TokyoDelivery #OsakaDelivery #TokyoEscort #OsakaEscort #JapanOutcall #TokyoDeriheru #OsakaDeriheru #JapanDelive
Yuna-chan ♡ #Tokyo Height: 159cm | Bust: D-cup | Age: 21 Has that cute girl-next-door vibe, with a super sweet smile and great at chatting～ (｡•́︿•̀｡) A bit shy at first, but once she warms up she becomes really clingy～ 🌟 @GEM816 | 🌟 GEM816 📖 Beginner @Tokyo6651 🌟 中文版：@GEM8166 🌟 日文版 @Oppai4 #TokyoDelivery #OsakaDelivery #TokyoEscort #OsakaEscort #JapanOutcall #TokyoDeriheru #OsakaDeriheru #JapanDelive
Miyu-chan ♡ #Osaka Height: 167cm | Bust: E-cup | Age: 22 A tall beauty with a cool, aloof aura… but deep down she’s incredibly gentle～ ( ˘ω˘ ) She might seem a little distant at first, but once you get close, she’ll quietly take care of you～ 🌟 @GEM816 | 🌟 GEM816 📖 Beginner @Tokyo6651 🌟 中文版：@GEM8166 🌟 日文版 @Oppai4 #TokyoDelivery #OsakaDelivery #TokyoEscort #OsakaEscort #JapanOutcall #TokyoDeriheru #OsakaDeriheru #Ja…
Number: KRT-047 #Tokyo 22 years old/158cm/D cup Nibbles earlobes while tracing circles with her tongue tip, hands drifting down to cradle your tip in warm palms. 🌟 @GEM816 | 🌟 GEM816 📖 Beginner @Tokyo6651 🌟 中文版：@GEM8166 🌟 日文版 @Oppai4 #TokyoDelivery #OsakaDelivery #TokyoEscort #OsakaEscort #JapanOutcall #TokyoDeriheru #OsakaDeriheru #JapanDelive
MNL-183 #Tokyo 19 years old / 152cm / C cup First, have you lie on your back—she mounts and grinds slowly forward and backward with her moist privates, her clitoris repeatedly stroking your shaft until you're nearly ready to release. 🌟 @GEM816 | 🌟 GEM816 📖 Beginner @Tokyo6651 🌟 中文版：@GEM8166 🌟 日文版 @Oppai4 #TokyoDelivery #OsakaDelivery #TokyoEscort #OsakaEscort #JapanOutcall #TokyoDeriheru #OsakaDeriheru #JapanDeliv
YBH-029 #Osaka 24 years old / 165cm / E cup Kneeling at the bed edge, she lets you enter from behind—her own fingers teasing her clit below. 'Deeper,' she whispers mid-thrust, body trembling faintly with each impact as her tight entrance grips firmly. 🌟 @GEM816 | 🌟 GEM816 📖 Beginner @Tokyo6651 🌟 中文版：@GEM8166 🌟 日文版 @Oppai4 #TokyoDelivery #OsakaDelivery #TokyoEscort #OsakaEscort #JapanOutcall #TokyoDeriheru #OsakaDe…
FQX-156 #Osaka 21 years old / 160cm / E cup She presses you against the wall, unzipping your pants with soft cleavage rubbing up and down your shaft. 🌟 @GEM816 | 🌟 GEM816 📖 Beginner @Tokyo6651 🌟 中文版：@GEM8166 🌟 日文版 @Oppai4 #TokyoDelivery #OsakaDelivery #TokyoEscort #OsakaEscort #JapanOutcall #TokyoDeriheru #OsakaDeriheru #JapanDelive
Showing the 12 most recent of 14 posts we hold for @JPescort. 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 — 720,466 of 1,627,068entries 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.
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.
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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“TokyoOsakaDeliveryGirls🇯🇵” (@JPescort), 4 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/JPescort.
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.