Telegram RegisterThe public register of Telegram
Telegram profile photo for 日本汐音閣外送茶|🇯🇵東京・大阪汐音閣高級出張 | Tokyo&Osaka Shione Delivery Escort

Channel

日本汐音閣外送茶|🇯🇵東京・大阪汐音閣高級出張 | Tokyo&Osaka Shione Delivery Escort

@Tokyov16

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

1,951subscribers

+40 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001964947763
TypeChannel
Username@Tokyov16
CreatedBetween 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live29 August 2026
Measurements held10
Confirmed unchanged1 time, most recently 29 August 2026
On Telegramt.me/Tokyov16

Growth

1,9111,9511,9317 August 2026 — 1,911 subscribers7 August 2026 — 1,911 subscribers8 August 2026 — 1,914 subscribers10 August 2026 — 1,921 subscribers14 August 2026 — 1,926 subscribers17 August 2026 — 1,934 subscribers20 August 2026 — 1,938 subscribers23 August 2026 — 1,939 subscribers26 August 2026 — 1,943 subscribers29 August 2026 — 1,951 subscribers7 August 202629 August 2026
10 measurements spanning 22 days, net +40. 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 1,905–1,957 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 05:241,951+8
26 Aug 2026, 13:571,943+4
23 Aug 2026, 21:251,939+1
20 Aug 2026, 03:361,938+4
17 Aug 2026, 12:281,934+8
14 Aug 2026, 03:481,926+5
10 Aug 2026, 21:421,921+7
8 Aug 2026, 01:411,914+3
7 Aug 2026, 10:311,911no change
7 Aug 2026, 10:261,911first reading

Engagement

12 posts held, back to 6 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
4.34%
avg views ÷ 1,951 subscribers
Avg views / post
84.6
12 posts measured
Reaction rate
1.37%
reactions ÷ views · ER floor
Posts in window
12
of 12 held

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. It is computed over the 2 of 12 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held12 (6 August 20267 August 2026)
Views total1,015
Reactions total2
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 17:15 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.

What this channel posts

Video runtime
51s
Average length
51s

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.

Reaction mix

2 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
150.0%
👍150.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 2 of the 12 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 2reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 12 most recent posts we hold, published 6 August 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:33 UTC84 viewsread 7 August 2026
Photo

🌟 解鎖戰鬥型甜美野獸 🌟 實力無需多言 - 全程高能電力滿格才是她的底牌 - 拒絕公式化客套服務 不冷場不敷衍 👧🏻 No.61 ➡️ 女孩資料 #東京反饋報告 #本店預約制 🤣諮詢/預約請私訊惠子💋 📱 𝑇𝑒𝑙𝑒𝑔𝑟𝑎𝑚 ⭐️ @xyjp99 📱 @𝟐𝟎𝟑𝐲𝐬𝐢𝐬𝐮⭐️ ⭐ 𝐡𝐮𝐢𝟏𝟎 𝑱𝒂𝒑𝒂𝒏 🇯🇵 汐音高級出張導航🔎 🐾🖤🐾🖤 🖤 🖤🐾🖤🐾 🔍東京𝐠𝐢𝐫𝐥𝐬 🔍大阪𝐠𝐢𝐫𝐥𝐬 🔍新手指南 🔍 客評反饋 👉 日本風俗總站總覽 🇯🇵 #東京出張 #大阪外送 #大阪風俗 #日本外送 #東京男士娛樂 #日本修車服務 #日本旅遊風俗

7 Aug 2026, 08:31 UTC59 viewsread 7 August 2026
Photo

♡ 雜誌封面御用 ‧ 奇蹟寫真新星 ♡ ☆頂級神顏騷女 私底下的純白初戀☆ 🪦🪦 #東京出勤 👑 🪦🪦 姓名💓 白石魅兒 年齡💓 23歲 三圍💓 166cm・F杯・47kg 🪦🪦 14萬/60分 🪦🪦 ▫️眼神自帶高冷感,是廣告商口中的神級天菜‼️卸下所有繁華的偽裝,交付百分之百的純真 🤣𝐂𝐨𝐧𝐭𝐚𝐜𝐭&預約🤍惠子店長💋 ✨🤍✨ ✨🤍✨ ✨🤍✨ 📱 𝑇𝑒𝑙𝑒𝑔𝑟𝑎𝑚 ⭐️ @xyjp99 📱 @𝟐𝟎𝟑𝐲𝐬𝐢𝐬𝐮⭐️ ⭐ 𝐡𝐮𝐢𝟏𝟎 ✨🤍✨ ✨🤍✨ ✨🤍✨

7 Aug 2026, 07:50 UTC58 views1 reactionsread 7 August 2026
Video

敢不敢直接空降過來當主力❔ -萬事俱備 就差你一咖 膽小別過來 這局玩很大 #日本3p #日本雙飛 💬 惠子唯一聯絡: 📱 𝑇𝑒𝑙𝑒𝑔𝑟𝑎𝑚 ⭐️ @xyjp99 📱 JP88y ⭐️ ⭐ 𝐡𝐮𝐢𝟏𝟎

1

7 Aug 2026, 07:40 UTC88 views1 reactionsread 7 August 2026
Photo

🌟 本想當個高冷的專業女孩,又被客人的好評反饋和信任打回原形。沒辦法,實力與趣味並存的我,就是這麼讓人放心。 -正是藏不住心事的年紀哈哈哈🕶️ 被好評的gilr- 莫娜 🌟【點擊跳轉資料】 💬 惠子唯一聯絡: 📱 𝑇𝑒𝑙𝑒𝑔𝑟𝑎𝑚 ⭐️ @xyjp99 📱 @𝟐𝟎𝟑𝐲𝐬𝐢𝐬𝐮⭐️ ⭐ 𝐡𝐮𝐢𝟏𝟎

👍1

7 Aug 2026, 07:14 UTC51 viewsread 7 August 2026
Photo

👍 東京熱熱熱 大阪也熱熱熱 熱怎麽辦?去love hotel享受呀🤔 💬 惠子唯一聯絡: 📱 𝑇𝑒𝑙𝑒𝑔𝑟𝑎𝑚 ⭐️ @xyjp99 📱 @𝟐𝟎𝟑𝐲𝐬𝐢𝐬𝐮⭐️ ⭐ 𝐡𝐮𝐢𝟏𝟎

7 Aug 2026, 07:10 UTC50 viewsread 7 August 2026
Photo

✦ 同志社大學大一甜心女友 #限定兼職 ✦ 😀 #大阪 ⭐⭐ 307 🤩🤩 𝑻𝒊𝒆𝒓 ❤️🤩🤩 🤩 關西私大現役生🤩 ⭐年齢:19歲 ⭐163cm・43kg・D杯 ▫️ 7萬/60分 18萬/180分 ▪️甜美精緻的嫩妹臉蛋 光是視覺效果就超級色 ▪️講話有一點大阪腔的羞澀✌ 女大學生特有的生疏與純真 🤣𝐂𝐨𝐧𝐭𝐚𝐜𝐭&預約🤍惠子店長💋 ✨🤍✨ ✨🤍✨ ✨🤍✨ 📱 𝑇𝑒𝑙𝑒𝑔𝑟𝑎𝑚 ⭐️ @xyjp99 📱 @𝟐𝟎𝟑𝐲𝐬𝐢𝐬𝐮⭐️ ⭐ 𝐡𝐮𝐢𝟏𝟎

7 Aug 2026, 07:10 UTC48 viewsread 7 August 2026
Photo

✦ 氣質OL 撕裂辦公室制服的絕對反差 ✦ ⭐⭐ #東京 ⭐⭐ 329 🤩🤩 𝑻𝒊𝒆𝒓 💜🤩🤩 🤍 氣質OL 🤍 😀159cm・44kg・D杯・24歲 ▫️ 4.5萬/60分 8萬/120分 ▫️ 白天穿著窄裙正裝端莊知性,關上房門會帶著迷離渴望的眼神,主動奉獻最私密粉嫩的絕對領域。 🤣𝐂𝐨𝐧𝐭𝐚𝐜𝐭&預約🤍惠子店長💋 ✨🤍✨ ✨🤍✨ ✨🤍✨ 📱 𝑇𝑒𝑙𝑒𝑔𝑟𝑎𝑚 ⭐️ @xyjp99 📱 @𝟐𝟎𝟑𝐲𝐬𝐢𝐬𝐮⭐️ ⭐ 𝐡𝐮𝐢𝟏𝟎

7 Aug 2026, 07:10 UTC52 viewsread 7 August 2026
Photo

☆2.5次元動漫姬!舞台上的奇蹟美少女 ☆ ☆甜美可愛很有女友感 服務不制式☆ 🪦🪦 #東京出勤 ❤️ 🪦🪦 編號 💓 328 年齡💓 19歲 三圍💓 156cm・D杯・43kg 🪦🪦 12萬/120分 🪦🪦 🤣𝐂𝐨𝐧𝐭𝐚𝐜𝐭&預約🤍惠子店長💋 ✨🤍✨ ✨🤍✨ ✨🤍✨ 📱 𝑇𝑒𝑙𝑒𝑔𝑟𝑎𝑚 ⭐️ @xyjp99 📱 @𝟐𝟎𝟑𝐲𝐬𝐢𝐬𝐮⭐️ ⭐ 𝐡𝐮𝐢𝟏𝟎 ✨🤍✨ ✨🤍✨ ✨🤍✨

6 Aug 2026, 17:02 UTC349 viewsread 7 August 2026
Photo

🎀🎀🎀 滿分零負評・萬中選一的極致稀缺🎀 -在Nana的身上,藏著稀缺的頂級女友感。 -不只溫柔到了骨子裡,更是懂你所有疲憊的解語花 💯 👧🏻 Nana ‹なな› ➡️ 女孩資料 #東京反饋報告 #本店預約制 🤣諮詢/預約請私訊惠子💋 📱 𝑇𝑒𝑙𝑒𝑔𝑟𝑎𝑚 ⭐️ @xyjp99 📱 @𝟐𝟎𝟑𝐲𝐬𝐢𝐬𝐮⭐️ ⭐ 𝐡𝐮𝐢𝟏𝟎 𝑱𝒂𝒑𝒂𝒏 🇯🇵 汐音高級出張導航🔎 🐾🖤🐾🖤 🖤 🖤🐾🖤🐾 🔍東京𝐠𝐢𝐫𝐥𝐬 🔍大阪𝐠𝐢𝐫𝐥𝐬 🔍新手指南 🔍 客評反饋 👉 日本風俗總站總覽 🇯🇵 #東京出張 #大阪外送 #大阪風俗 #日本外送 #東京男士娛樂 #日本修車服務 #日本旅遊風俗

Showing the 12 most recent of 12 posts we hold for @Tokyov16. 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 — 425,045 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.

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.

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

“日本汐音閣外送茶|🇯🇵東京・大阪汐音閣高級出張 | Tokyo&Osaka Shione Delivery Escort” (@Tokyov16), 1,951 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/Tokyov16.

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.