Channel
@tokyy99
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
8subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002690317724 |
|---|---|
| Type | Channel |
| Username | @tokyy99 |
| Description | 👀看到這裡，代表你準備好了 約妹不求人、0經驗也能入門 🔔記得開通知，新手不走冤枉路！ 🌐私密TG ⭐️: @eyey285 ⭐️Gleezy ⭐️ :tokyy99 ✅テレグラム情報：t.me/jkf028 |
| Created | 24 June 2025 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 23 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/tokyy99 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 13:46 | 8 | no change |
| 8 Aug 2026, 10:16 | 8 | first reading |
10 posts held, back to 24 June 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 10 posts for this entry, the most recent from 25 January 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.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 1 of the 10 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 1reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 24 June 2025 to 25 January 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.
#为什么要提前预约女孩？ 很多哥哥会问：「临时约不行吗？」 其实提前预约真的差很多，能让整体体验更顺、更安心 ① 热门女孩排程很快满 优质、服务好的女孩常常一上班就被预约额满，提前订位才能确保你想见的那位一定留给你 ② 能帮你挑到最适合你的类型 提前告诉我你的喜好，我能从出勤名单里替你挑到更符合偏好的女孩，不用靠运气 ③ 时间更弹性、不用等 临时约可能刚好碰上女孩在赶场，提前预约能让时间更准、不延误 ④ 女孩能提前准备好状态 提早安排让女孩有时间整理仪态，以最好状态接待你 ⑤ 整体体验更稳定、避免踩雷 越早预约，选择越多、品质越稳，避免只能临时排到不适合的时间或类型 👉🇯🇵Angle東京/大阪外送🥰👈 🌐私密TG ⭐: @eyey285 ⭐Gleezy ⭐ :tokyy99 ✅Angle东京情报：t.me/jkf028 ✅Angle大阪情报：t.me/jkf996 ✅Angle新手上路：t.me/tokyy99…
Signed 🇯🇵LoveAngle東京♥ で「ふうぞくてん
Angle🌸东京/大阪外约新手上路 pinned «👉🇯🇵Angle派送區域 & 車資資訊 🌍 東京都內派送區域 🚗 東京15區內 車資：3,000円 新宿區、豐島區、中央區 千代田區、荒川區、北區 港區、台東區、墨田區 目黑區、品川區、澀谷區 中野區、江東區、文京區 🌍 大阪市派送區域 大阪市內 🚗 車資：4,000円 此花區、福島區、 北區 港區、 西淀川區、西成區 大正區、中央區、 西區 天王寺區、浪速區、都島區 阿倍野區、城東區、東成區 生野區 大阪市外及部分周邊區域 🚗 車資：6,000円 東大阪市、平野區、淀川區…»
👉🇯🇵Angle派送區域 & 車資資訊 🌍 東京都內派送區域 🚗 東京15區內 車資：3,000円 新宿區、豐島區、中央區 千代田區、荒川區、北區 港區、台東區、墨田區 目黑區、品川區、澀谷區 中野區、江東區、文京區 🌍 大阪市派送區域 大阪市內 🚗 車資：4,000円 此花區、福島區、 北區 港區、 西淀川區、西成區 大正區、中央區、 西區 天王寺區、浪速區、都島區 阿倍野區、城東區、東成區 生野區 大阪市外及部分周邊區域 🚗 車資：6,000円 東大阪市、平野區、淀川區 旭區、鶴見區、住之江區 住吉區、東住吉區、東淀川區 🏨 外約說明 外約酒店／飯店（東京可送住家） 確認見到女孩本人滿意後再付款 僅接受現金（日元）交易 不接受微信、支付寶、轉帳或匯款付款 若不確定地點是否在派遣範圍內 歡迎私下詢問Angle確認@eyey285 👉🇯🇵Angle東京/大阪外送🥰👈 🌐私密TG ⭐: …
Signed 🇯🇵LoveAngle東京♥ で「ふうぞくてん
Angle🌸东京/大阪外约新手上路 pinned «✨🇯🇵日本Angle外送地区 配送范围：东京｜大阪 东京外送地区：【23区送16区】 #荒川区 #北区 #墨田区 #台东区 #品川区 #江东区 #丰岛区 #文京区 #千代田区 #中央区 #新宿区 #港区 #中野区 #涩谷区 #目黑区 大阪外送地区： 【外+3000车资】 #福岛区 #此花区 #北区 #港区 #西区 #中央区 #都岛区 #城东区 #大正区 #浪速区 #天王寺区 #西成区 #阿倍野区 #生野区 #城东区 【外+5000车资】…»
✨🇯🇵日本Angle外送地区 配送范围：东京｜大阪 东京外送地区：【23区送16区】 #荒川区 #北区 #墨田区 #台东区 #品川区 #江东区 #丰岛区 #文京区 #千代田区 #中央区 #新宿区 #港区 #中野区 #涩谷区 #目黑区 大阪外送地区： 【外+3000车资】 #福岛区 #此花区 #北区 #港区 #西区 #中央区 #都岛区 #城东区 #大正区 #浪速区 #天王寺区 #西成区 #阿倍野区 #生野区 #城东区 【外+5000车资】 #西淀川区 #淀川区 #东淀川区 #旭区 #鹤见区 #东大阪市 #平野区 #住之江区 #住吉区东 #住吉区 👉🇯🇵Angle東京/大阪外送🥰👈 🌐私密TG ⭐: @eyey285 ⭐Gleezy ⭐ :tokyy99 ✅Angle东京情报：t.me/jkf028 ✅Angle大阪情报：t.me/j…
❤1
Channel name was changed to «Angle🌸东京/大阪外约新手上路»
Angle东京外约初次教学： Angle东京外约常见问题集（价格.服务.及其他游玩细节） Angle东京外约的规矩向来透明，以下整理新客常问的问题，希望能够解答您的疑惑。 Q.1: Angle东京外约的服务范围在哪里？消费价格是否一致？ A.1: 目前主要服务范围东京、23区域 东京23区起跳价为30,000日元起........ Q.2: 支付方式如何？加时间怎么计算？ A.2: 一律现金交易，直接交付予小姐即可。 加时间是服务以原本/1小时计算 Q.3: 是否有额外收费项目？ A.3: 交通费/特殊服务费 如：无套 内射 肛交等等特殊服务 Q.4: 旅馆费用由谁支付？ A.4: 客人自行负担，本Angle东京外约仅负责安排小姐。 可为客人推荐安全的旅馆/情侣酒店/饭店等..... Q.5: 可否事先查看小姐的照片？ A.5: 因隐私考量，Telegram频道仅提供相似照.有诚意者可私密@eyey285看本人…
Channel name was changed to «Angle🌸东京外约💥はじめる»
Channel photo updated
Channel created
Showing the 10 most recent of 10 posts we hold for @tokyy99. 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 — 162,533 of 1,622,561entries 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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Angle🌸东京/大阪外约新手上路” (@tokyy99), 8 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/tokyy99.
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.