Telegram RegisterThe public register of Telegram
Telegram profile photo for Miya大阪-東京外送茶|上門美女服務|外送🇯🇵 gleezy:ck71mv

Channel

Miya大阪-東京外送茶|上門美女服務|外送🇯🇵 gleezy:ck71mv

@Tokyomya

On this record: Growth · Engagement · Posts · Citations · Cite this entry

2,804subscribers

+85 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-1002810939925
TypeChannel
Username@Tokyomya
CreatedBetween 1 June 2025 and 30 September 2025— 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/Tokyomya

Growth

2,7192,8042,761.57 August 2026 — 2,719 subscribers7 August 2026 — 2,719 subscribers7 August 2026 — 2,721 subscribers11 August 2026 — 2,734 subscribers14 August 2026 — 2,724 subscribers17 August 2026 — 2,750 subscribers20 August 2026 — 2,754 subscribers23 August 2026 — 2,775 subscribers26 August 2026 — 2,784 subscribers29 August 2026 — 2,804 subscribers7 August 202629 August 2026
10 measurements spanning 22 days, net +85. 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 2,706–2,817 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 12:142,804+20
26 Aug 2026, 17:442,784+9
23 Aug 2026, 21:372,775+21
20 Aug 2026, 10:122,754+4
17 Aug 2026, 12:382,750+26
14 Aug 2026, 07:232,724-10
11 Aug 2026, 02:272,734+13
7 Aug 2026, 22:312,721+2
7 Aug 2026, 18:032,719no change
7 Aug 2026, 17:482,719first reading

Engagement

7 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 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
1.17%
avg views ÷ 2,804 subscribers
Avg views / post
32.9
7 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
7
of 7 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.

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

Recent posts

7 Aug 2026, 10:35 UTC21 viewsread 7 August 2026
Forwarded from @miyabao99Photo

時間雖然過得快 但內容充實到讓人完全沉浸在餘韻裡 謝謝哥哥信任 能得到哥哥下次的指名 就是Miya最大的成就感 🪽 Telegram:@ck659 🦋

7 Aug 2026, 10:34 UTC18 viewsread 7 August 2026
Forwarded from @miya1028Photo

*咪想要 咪可以得到嗎 TCVyransz2wZ8BeLcTLCQEkyKU5hh8oSnE

7 Aug 2026, 09:27 UTC22 viewsread 7 August 2026
Forwarded from @miyabao99Photo

*性福成功送達~ 🪽 Telegram:@ck659 🦋

7 Aug 2026, 04:15 UTC31 viewsread 7 August 2026
Photo

安藤 莉亞(Ando Ria) 年齡:20歲|罩杯:B|身高:160cm 三圍:75・59・91|星座:雙子座|性格:ESTJ ✧🤍🤍🤍Miya🐱delivery🤍🤍🤍 ✧。 打扮時尚前衛的酷妹子,私底下卻超怕寂寞。主動抱住你時的熱烈與羞澀,帶給你極具衝擊力的反差體驗 🪽 預約方式🦋 🎀Telegram:@ck659 🎀Gleezy ID:ck71mv 官方網站 👆 ⭐️ 查看東京美眉日常 ⭐️ 查看大阪美眉日常

7 Aug 2026, 04:14 UTC28 viewsread 7 August 2026
Photo

羽田 琉菜(Hada Runa) 年齡:23歲|罩杯:D|身高:161cm 三圍:81・57・89|星座:水瓶座|性格:INTP ✧🤍🤍🤍Miya🐱delivery🤍🤍🤍 ✧。 嘴上說著不要、身體卻很誠實的典型傲嬌。嘴硬地湊過來討摸摸,身體軟成一灘水時的模樣可愛爆表 🪽 預約方式🦋 🎀Telegram:@ck659 🎀Gleezy ID:ck71mv 官方網站 👆 ⭐️ 查看東京美眉日常 ⭐️ 查看大阪美眉日常

7 Aug 2026, 04:13 UTC31 viewsread 7 August 2026
Photo

淺倉 蓮(Asakura Ren) 年齡:23歲|罩杯:C|身高:165cm 三圍:78・60・92|星座:巨蟹座|性格:ISFP ✧🤍🤍🤍Miya🐱delivery🤍🤍🤍 ✧。 成熟優雅中帶著無微不至的照顧感。體貼入微的包容力,主動擁抱時那份綿軟與溫情,讓人流連忘返 🪽 預約方式🦋 🎀Telegram:@ck659 🎀Gleezy ID:ck71mv 官方網站 👆 ⭐️ 查看東京美眉日常 ⭐️ 查看大阪美眉日常

6 Aug 2026, 04:35 UTC79 viewsread 7 August 2026
Photo

井上 美咲(Inoue Misaki) 年齡:22歲|罩杯:D|身高:159cm 三圍:85・57・91|星座:雙子座|性格:ENFP ✧🤍🤍🤍Miya🐱delivery🤍🤍🤍 ✧。 脫光後卻極度放蕩,會自己掰開穴穴求深插,浪叫聲超有魅力,反差讓人血脈噴張 🪽 預約方式🦋 🎀Telegram:@ck659 🎀Gleezy ID:ck71mv 官方網站 👆 ⭐️ 查看東京美眉日常 ⭐️ 查看大阪美眉日常 #日本東京哪裡好玩 #日本東京 #日本東京約砲

Showing the 7 most recent of 7 posts we hold for @Tokyomya. 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 — 1,325,959 of 1,626,935entries 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

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 1 registered channel — 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.

“Miya大阪-東京外送茶|上門美女服務|外送🇯🇵 gleezy:ck71mv” (@Tokyomya), 2,804 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/Tokyomya.

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.