Telegram RegisterThe public register of Telegram
Telegram profile photo for 桃宮の烏托邦|東京 大阪外送茶|日本風俗店泡泡浴|上門服務

Channel

桃宮の烏托邦|東京 大阪外送茶|日本風俗店泡泡浴|上門服務

@miji61

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

2,255subscribers

-89 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-1002765923432
TypeChannel
Username@miji61
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 held9
Confirmed unchanged1 time, most recently 29 August 2026
On Telegramt.me/miji61

Growth

2,2522,5672,409.57 August 2026 — 2,344 subscribers7 August 2026 — 2,344 subscribers10 August 2026 — 2,319 subscribers13 August 2026 — 2,255 subscribers16 August 2026 — 2,567 subscribers19 August 2026 — 2,471 subscribers23 August 2026 — 2,294 subscribers26 August 2026 — 2,252 subscribers29 August 2026 — 2,255 subscribers2,2557 August 202629 August 2026
9 measurements spanning 22 days, net -89. 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,205–2,614 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 15:052,255+3
26 Aug 2026, 20:252,252-42
23 Aug 2026, 12:152,294-177
19 Aug 2026, 23:122,471-96
16 Aug 2026, 19:052,567+312
13 Aug 2026, 02:352,255-64
10 Aug 2026, 12:012,319-25
7 Aug 2026, 21:262,344no change
7 Aug 2026, 17:332,344first reading

Engagement

6 posts held, back to 7 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 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.11%
avg views ÷ 2,255 subscribers
Avg views / post
25.0
6 posts measured
Reaction rate
2.94%
reactions ÷ views · ER floor
Posts in window
6
of 6 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 1 of 6 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 held6 (7 August 20267 August 2026)
Views total150
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 17:33 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.

Reaction mix

1 reaction across 1 post, in 1 kind.

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

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

⭐哥哥們如果想要當天預約女孩的話最好提前 2-3個小時預約喲 女孩才好配合哥哥想要的時間喲⭐ 📱LINE 88uki 📱 TG @uki37 ⭐Gleezy jk37

7 Aug 2026, 11:04 UTC19 viewsread 7 August 2026
Photo

感謝各位哥哥的無條件信任,這份安心只有我們能給! 想體驗專屬的貼心服務?馬上私訊桃桃下單!💬 📱LINE 88uki 📱 TG @uki37 ⭐Gleezy jk37

7 Aug 2026, 11:00 UTC17 viewsread 7 August 2026
Photo

【老客回購就是最好的名片!價格透明不坑人】 感謝哥哥再次支持!老客預約就是這麼乾脆爽快~✨ 📱LINE 88uki 📱 TG @uki37 ⭐Gleezy jk37

7 Aug 2026, 04:48 UTC34 views1 reactionsread 7 August 2026
Photo

⭐今日出勤特推⭐ 早苗(さなえ ) 💭159cm / 20歲 / D罩杯💭 番號: 441 出勤時間:19:09 / 00:39 🌸➖➖➖🤩🤩➖➖➖🌸 🎀深夜限定的 20 歲發情小母貓,深諳各種敏感帶,最愛全裸貼身磨蹭,一邊迎合你的巨大撞擊一邊放聲浪叫,爽到你頭皮發麻🎀 ✧ 𝓓𝓮𝓽𝓪𝓲𝓵𝓼 𝓐𝓫𝓸𝓾𝓽 𝓜𝓮 ✧ 📱LINE 88uki 📱 TG @uki37 ⭐Gleezy jk37 日記 @moji63jk37 東京 @miji61 大阪 @moji613 客評:@F87ok 日本東京大阪:@hki37 🤍🤍🤍🤍🤩🤩🤍🤍🤍🤍 #大阪安全叫小姐 #日本新手叫小姐 #東京首次叫小姐

1

7 Aug 2026, 04:46 UTC30 viewsread 7 August 2026
Photo

⭐今日出勤特推⭐ 初音(はつね ) 💭164cm / 22歲 / E罩杯💭 番號: 923 出勤時間:17:51 / 23:21 🌸➖➖➖🤩🤩➖➖➖🌸 🎀164公分身材高挑的 22 歲 E 乳極品,跨坐上來時一邊放浪搖擺,一邊用緊緻的水蜜桃肉穴死死咬住你不放,把你榨乾到一滴不剩。🎀 ✧ 𝓓𝓮𝓽𝓪𝓲𝓵𝓼 𝓐𝓫𝓸𝓾𝓽 𝓜𝓮 ✧ 📱LINE 88uki 📱 TG @uki37 ⭐Gleezy jk37 日記 @moji63jk37 東京 @miji61 大阪 @moji613 客評:@F87ok 日本東京大阪:@hki37 🤍🤍🤍🤍🤩🤩🤍🤍🤍🤍 #大阪首次叫小姐 #日本叫小姐價格 #日本小姐評價

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

⭐今日出勤特推⭐ 雅美(みやび ) 💭156cm / 19歲 / E罩杯💭 番號: 684 出勤時間:15:53 / 21:23 🌸➖➖➖🤩🤩➖➖➖🌸 🎀19歲清純與淫亂兼具的 E 乳爆乳尤物!挺拔的 E 罩杯豪乳能把你整根夾沒,最愛一邊乳交一邊放浪呻吟,帶你衝上雲端🎀 ✧ 𝓓𝓮𝓽𝓪𝓲𝓵𝓼 𝓐𝓫𝓸𝓾𝓽 𝓜𝓮 ✧ 📱LINE 88uki 📱 TG @uki37 ⭐Gleezy jk37 日記 @moji63jk37 東京 @miji61 大阪 @moji613 客評:@F87ok 日本東京大阪:@hki37 🤍🤍🤍🤍🤩🤩🤍🤍🤍🤍 #東京上門小姐推薦 #大阪上門小姐推薦

Showing the 6 most recent of 6 posts we hold for @miji61. 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,102,352 of 1,629,452 entries 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.

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.

“桃宮の烏托邦|東京 大阪外送茶|日本風俗店泡泡浴|上門服務” (@miji61), 2,255 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/miji61.

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.