Channel
@xyjp991
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
341subscribers
+28 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003698287320 |
|---|---|
| Type | Channel |
| Username | @xyjp991 |
| Created | Between 1 December 2025 and 31 May 2026— 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 | 5 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/xyjp991 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 04:15 | 341 | +10 |
| 23 Aug 2026, 08:03 | 331 | +1 |
| 15 Aug 2026, 19:48 | 330 | +17 |
| 8 Aug 2026, 07:35 | 313 | no change |
| 7 Aug 2026, 10:32 | 313 | first reading |
8 posts held, back to 4 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 8 August 2026 |
|---|---|
| Posts held | 8 (4 August 2026 – 8 August 2026) |
| Views total | 200 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 07: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.
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.
回顧昨天做完睡不覺哈哈哈 因為女孩水太多太濕 沒有乾濕分離導致床濕濕的哈哈哈哈😝🙈 🌟細看一臉淫蕩 - 體質多水氾濫💦 🌟服務親親抱抱 - 敏感反饋超好💯 👧🏻 No. 148 ➡️ 女孩資料 #東京反饋報告 #本店預約制 🤣諮詢/預約請私訊惠子💋 📱 𝑇𝑒𝑙𝑒𝑔𝑟𝑎𝑚 ⭐️ @xyjp99 📱 @𝟐𝟎𝟑𝐲𝐬𝐢𝐬𝐮⭐️ ⭐ 𝐡𝐮𝐢𝟏𝟎 𝑱𝒂𝒑𝒂𝒏 🇯🇵 汐音高級出張導航🔎 🐾🖤🐾🖤 🖤 🖤🐾🖤🐾 🔍東京𝐠𝐢𝐫𝐥𝐬 🔍大阪𝐠𝐢𝐫𝐥𝐬 🔍新手指南 🔍 客評反饋 👉 日本風俗總站總覽 🇯🇵 #東京出張 #大阪外送 #大阪風俗 #日本外送 #東京男士娛樂 #日本修車服務 #日本旅遊風俗
🌟 解鎖戰鬥型甜美野獸 🌟 實力無需多言 - 全程高能電力滿格才是她的底牌 - 拒絕公式化客套服務 不冷場不敷衍 👧🏻 No.61 ➡️ 女孩資料 #東京反饋報告 #本店預約制 🤣諮詢/預約請私訊惠子💋 📱 𝑇𝑒𝑙𝑒𝑔𝑟𝑎𝑚 ⭐️ @xyjp99 📱 @𝟐𝟎𝟑𝐲𝐬𝐢𝐬𝐮⭐️ ⭐ 𝐡𝐮𝐢𝟏𝟎 𝑱𝒂𝒑𝒂𝒏 🇯🇵 汐音高級出張導航🔎 🐾🖤🐾🖤 🖤 🖤🐾🖤🐾 🔍東京𝐠𝐢𝐫𝐥𝐬 🔍大阪𝐠𝐢𝐫𝐥𝐬 🔍新手指南 🔍 客評反饋 👉 日本風俗總站總覽 🇯🇵 #東京出張 #大阪外送 #大阪風俗 #日本外送 #東京男士娛樂 #日本修車服務 #日本旅遊風俗
敢不敢直接空降過來當主力❔ -萬事俱備 就差你一咖 膽小別過來 這局玩很大 #日本3p #日本雙飛 💬 惠子唯一聯絡： 📱 𝑇𝑒𝑙𝑒𝑔𝑟𝑎𝑚 ⭐️ @xyjp99 📱 JP88y ⭐️ ⭐ 𝐡𝐮𝐢𝟏𝟎
🌟純欲小惡魔降臨 外表可愛甜美 💯 氣氛帶到最高 👧🏻 No. 306 ➡️ 女孩資料 #大阪反饋報告 #本店預約制 🤣諮詢/預約請私訊惠子💋 📱 𝑇𝑒𝑙𝑒𝑔𝑟𝑎𝑚 ⭐️ @xyjp99 📱 @𝟐𝟎𝟑𝐲𝐬𝐢𝐬𝐮⭐️ ⭐ 𝐡𝐮𝐢𝟏𝟎
🌟嬌小可愛的小手辦 服務不怯場 可親可舌可舔🌟 👧🏻 No.326 ➡️ 女孩資料 #東京反饋報告 #本店預約制 🤣諮詢/預約請私訊惠子💋 📱 𝑇𝑒𝑙𝑒𝑔𝑟𝑎𝑚 ⭐️ @xyjp99 📱 @𝟐𝟎𝟑𝐲𝐬𝐢𝐬𝐮⭐️ ⭐ 𝐡𝐮𝐢𝟏𝟎
🌟 以前足交從未射過,能射的她是第一個！ 🌟 絲足控終極福音✨帶你解鎖新世界 👧🏻 彩花 ➡️ 女孩資料 #東京反饋報告 #本店預約制 🤣諮詢/預約請私訊惠子💋 📱 𝑇𝑒𝑙𝑒𝑔𝑟𝑎𝑚 ⭐️ @xyjp99 📱 @𝟐𝟎𝟑𝐲𝐬𝐢𝐬𝐮⭐️ ⭐ 𝐡𝐮𝐢𝟏𝟎 𝑱𝒂𝒑𝒂𝒏 🇯🇵 汐音高級出張導航🔎 🐾🖤🐾🖤 🖤 🖤🐾🖤🐾 🔍東京𝐠𝐢𝐫𝐥𝐬 🔍大阪𝐠𝐢𝐫𝐥𝐬 🔍新手指南 🔍 客評反饋 👉 日本風俗總站總覽 🇯🇵 #東京出張 #大阪外送 #大阪風俗 #日本外送 #東京男士娛樂 #日本修車服務 #日本旅遊風俗
😍爽是真的！怕也是真的！ 肉食系天花板狂野御姐🪄 不給等CD的榨乾的榨精姬💘 - 首次體驗強姦💣3小時狂射3次 信惠惠的推薦 每次都解鎖不同的體驗 #東京反饋報告 #AV女優 #私房女孩 🤣諮詢/預約請私訊惠子💋 📱 𝑇𝑒𝑙𝑒𝑔𝑟𝑎𝑚 ⭐️ @xyjp99 📱 @𝟐𝟎𝟑𝐲𝐬𝐢𝐬𝐮⭐️ ⭐ 𝐡𝐮𝐢𝟏𝟎 𝑱𝒂𝒑𝒂𝒏 🇯🇵 汐音高級出張導航🔎 🐾🖤🐾🖤 🖤 🖤🐾🖤🐾 🔍東京𝐠𝐢𝐫𝐥𝐬 🔍大阪𝐠𝐢𝐫𝐥𝐬 🔍新手指南 🔍 客評反饋 👉 日本風俗總站總覽 🇯🇵 #東京出張 #大阪外送 #大阪風俗 #日本外送 #東京男士娛樂 #日本修車服務 #日本旅遊風俗
🌟 讓人直呼99分的夢幻尤物反差衝擊 🌟 這1分扣在絲襪沒玩上（怪惠怪惠） 👧🏻 No. 184 ➡️ 女孩資料 #東京反饋報告 #本店預約制 🤣諮詢/預約請私訊惠子💋 📱 𝑇𝑒𝑙𝑒𝑔𝑟𝑎𝑚 ⭐️ @xyjp99 📱 @𝟐𝟎𝟑𝐲𝐬𝐢𝐬𝐮⭐️ ⭐ 𝐡𝐮𝐢𝟏𝟎 𝑱𝒂𝒑𝒂𝒏 🇯🇵 汐音高級出張導航🔎 🐾🖤🐾🖤 🖤 🖤🐾🖤🐾 🔍東京𝐠𝐢𝐫𝐥𝐬 🔍大阪𝐠𝐢𝐫𝐥𝐬 🔍新手指南 🔍 客評反饋 👉 日本風俗總站總覽 🇯🇵 #東京出張 #大阪外送 #大阪風俗 #日本外送 #東京男士娛樂 #日本修車服務 #日本旅遊風俗
Showing the 8 most recent of 8 posts we hold for @xyjp991. 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 — 608,289 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.
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.
“日本老濕机🚗極上案內所” (@xyjp991), 341 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/xyjp991.
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.