Telegram RegisterThe public register of Telegram

Channel

🇯🇵 Misaki 東京・大阪案內所|日本外送資訊服務

@p965286

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

115subscribers

+1 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1004270586962
TypeChannel
Username@p965286
CreatedBetween 1 May 2026 and 9 August 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live9 August 2026
Measurements held3
On Telegramt.me/p965286

Growth

114115114.58 Aug 2026, 02:34 — 114 subscribers9 Aug 2026, 01:31 — 115 subscribers9 Aug 2026, 05:47 — 115 subscribers8 Aug 2026, 02:349 Aug 2026, 05:47
3 measurements spanning 1 day, net +1. 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 114–115 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 05:47115no change
9 Aug 2026, 01:31115+1
8 Aug 2026, 02:34114first reading

Engagement

9 posts held, back to 9 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.45%
avg views ÷ 115 subscribers
Avg views / post
1.7
9 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
9
of 9 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 9 August 2026
Posts held9 (9 August 20269 August 2026)
Views total15
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 05:47 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

Photos
657
Videos
21
Links
247

Lifetime counters from Telegram’s own channel header, read 9 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.

Video runtime
1m 01s
Average length
1m 01s

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.

Recent posts

9 Aug 2026, 04:42 UTC3 viewsread 9 August 2026
Video

性愛需要滿足雙方❤️ 你今日做愛了嗎 如果沒有做 那就來吧❤️

9 Aug 2026, 04:27 UTC3 viewsread 9 August 2026
Photo

💋番號:JP-AV134 🌱條件:162,24 ,50kg ,G 特點:童顏G奶小美女,臉蛋可愛、身材超有料 粉嫩感滿滿、配合溫柔,剛開始沒多久 ~ 互動細膩、反應超純情,緊實又帶感 目前因生活關係出來兼職,希望哥哥們多多支持~ ⭐Gleezy密我 TeA88K 🪜TG約妹聯絡 t.me/JPFB34 🪜TG雙向聯絡 t.me/jpfb88 📱Line約妹聯絡 TeA88K 💚新手約妹流程 快速上手 💜加入Gleezy色色圖片群 日本出差 東京出差 大阪出差 日本旅遊 東京旅遊 大阪旅遊 東京自由行 大阪自由行日本中文服務 東京中文服務 大阪中文服務 日本華人旅遊 東京華人旅遊 大阪華人旅遊 東京中文攻略 大阪中文攻略

9 Aug 2026, 04:27 UTC2 viewsread 9 August 2026
Photo

💋番號:JP-AV133 🌱條件:158,25 ,47kg ,F 特點:這位甜美護理師好胸…真是辛苦啦!雖然不會過份賣弄性感,但看著也魅力十足,如此清秀可人的優質女孩,真的很難得 喜歡的卡緊私訊小傾呦 ⭐Gleezy密我 TeA88K 🪜TG約妹聯絡 t.me/JPFB34 🪜TG雙向聯絡 t.me/jpfb88 📱Line約妹聯絡 TeA88K 💚新手約妹流程 快速上手 💜加入Gleezy色色圖片群 日本出差 東京出差 大阪出差 日本旅遊 東京旅遊 大阪旅遊 東京自由行 大阪自由行日本中文服務 東京中文服務 大阪中文服務 日本華人旅遊 東京華人旅遊 大阪華人旅遊 東京中文攻略 大阪中文攻略

9 Aug 2026, 04:26 UTC2 viewsread 9 August 2026
Photo

💋番號:JP-AV132 🌱條件:166,26 ,50kg ,G 特點:氣質大奶 汁水很多 穴穴還非常緊,服務很騷 可以配合做愛 口交 按摩 幫洗 乳交 69 螞蟻上樹 水中蕭 泡澡 火車便當等服務 ~ ⭐Gleezy密我 TeA88K 🪜TG約妹聯絡 t.me/JPFB34 🪜TG雙向聯絡 t.me/jpfb88 📱Line約妹聯絡 TeA88K 💚新手約妹流程 快速上手 💜加入Gleezy色色圖片群 日本出差 東京出差 大阪出差 日本旅遊 東京旅遊 大阪旅遊 東京自由行 大阪自由行日本中文服務 東京中文服務 大阪中文服務 日本華人旅遊 東京華人旅遊 大阪華人旅遊 東京中文攻略 大阪中文攻略

9 Aug 2026, 04:26 UTC1 viewsread 9 August 2026
Photo

💋番號:JP-AV131 🌱條件:164,24 ,46kg ,E 特點:床上十足野性 主動服務你 挑逗到你凍未條~~正年輕 態度好 可親.摸.舔..水多 騷 配合度非常高很活躍 保證你滿意唷 ⭐Gleezy密我 TeA88K 🪜TG約妹聯絡 t.me/JPFB34 🪜TG雙向聯絡 t.me/jpfb88 📱Line約妹聯絡 TeA88K 💚新手約妹流程 快速上手 💜加入Gleezy色色圖片群 日本出差 東京出差 大阪出差 日本旅遊 東京旅遊 大阪旅遊 東京自由行 大阪自由行日本中文服務 東京中文服務 大阪中文服務 日本華人旅遊 東京華人旅遊 大阪華人旅遊 東京中文攻略 大阪中文攻略

9 Aug 2026, 04:26 UTC1 viewsread 9 August 2026
Photo

💋番號:JP-AV130 🌱條件:163,25 ,48kg ,F 特點:細節服務到位,溫柔又有女人味白皙長腿,氣質優雅,帶點御姐氣息 共浴、女上位、愛愛、69、LG、奶泡、舌吻 ⭐Gleezy密我 TeA88K 🪜TG約妹聯絡 t.me/JPFB34 🪜TG雙向聯絡 t.me/jpfb88 📱Line約妹聯絡 TeA88K 💚新手約妹流程 快速上手 💜加入Gleezy色色圖片群 日本出差 東京出差 大阪出差 日本旅遊 東京旅遊 大阪旅遊 東京自由行 大阪自由行日本中文服務 東京中文服務 大阪中文服務 日本華人旅遊 東京華人旅遊 大阪華人旅遊 東京中文攻略 大阪中文攻略

9 Aug 2026, 04:26 UTC1 viewsread 9 August 2026
Photo

💋番號:JP-AV125 🌱條件:156,20 ,44kg ,D+ 特點:鮑魚水多緊緻 很會夾 喜歡玩後背式有“啪啪啪”撞擊聲胸部柔軟天然的 甜甜的很有女友感覺在床上活似小騷包 ⭐Gleezy密我 TeA88K 🪜TG約妹聯絡 t.me/JPFB34 🪜TG雙向聯絡 t.me/jpfb88 📱Line約妹聯絡 TeA88K 💚新手約妹流程 快速上手 💜加入Gleezy色色圖片群 日本出差 東京出差 大阪出差 日本旅遊 東京旅遊 大阪旅遊 東京自由行 大阪自由行日本中文服務 東京中文服務 大阪中文服務 日本華人旅遊 東京華人旅遊 大阪華人旅遊 東京中文攻略 大阪中文攻略

9 Aug 2026, 04:26 UTC1 viewsread 9 August 2026
Photo

💋番號:JP-AV129 🌱條件:164,24 ,50kg ,G 特點:性感火辣 性慾旺盛到不行! 她約會時會自備情趣按摩棒 需求極其旺盛,床上的叫床聲既大且淫蕩,讓人難以抗拒她的熱情! ⭐Gleezy密我 TeA88K 🪜TG約妹聯絡 t.me/JPFB34 🪜TG雙向聯絡 t.me/jpfb88 📱Line約妹聯絡 TeA88K 💚新手約妹流程 快速上手 💜加入Gleezy色色圖片群 日本出差 東京出差 大阪出差 日本旅遊 東京旅遊 大阪旅遊 東京自由行 大阪自由行日本中文服務 東京中文服務 大阪中文服務 日本華人旅遊 東京華人旅遊 大阪華人旅遊 東京中文攻略 大阪中文攻略

9 Aug 2026, 04:26 UTC1 viewsread 9 August 2026
Photo

💋番號:JP-AV128 🌱條件:160,25 ,48kg ,E 特點:外型清秀,帶點文靜卻又藏不住的小性感 完全是小欲女 身材棒棒der 床上功夫超好喲~可深喉嚨 冰火等服務 奶子大 很挺 看到就讓你雞雞硬硬的 ⭐Gleezy密我 TeA88K 🪜TG約妹聯絡 t.me/JPFB34 🪜TG雙向聯絡 t.me/jpfb88 📱Line約妹聯絡 TeA88K 💚新手約妹流程 快速上手 💜加入Gleezy色色圖片群 日本出差 東京出差 大阪出差 日本旅遊 東京旅遊 大阪旅遊 東京自由行 大阪自由行日本中文服務 東京中文服務 大阪中文服務 日本華人旅遊 東京華人旅遊 大阪華人旅遊 東京中文攻略 大阪中文攻略

Showing the 9 most recent of 9 posts we hold for @p965286. 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 — 124,490 of 1,169,250entries 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 5 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 9 August 2026 — this entry's latest reading, not the date you are reading this.

“🇯🇵 Misaki 東京・大阪案內所|日本外送資訊服務” (@p965286), 115 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/p965286.

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.