Channel
@one1812
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
59subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003754545995 |
|---|---|
| Type | Channel |
| Username | @one1812 |
| Description | #東京泡泡浴 #東京泡泡浴推薦 #東京成人按摩 #東京成人浴場 #新宿泡泡浴 #涉谷泡泡浴 #東京泡泡浴攻略 #東京泡泡浴必去 #東京泡泡浴新手指南 #東京性感按摩 |
| Created | Between 1 February 2026 and 11 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/one1812 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 05:30 | 59 | no change |
| 6 Aug 2026, 19:49 | 59 | first reading |
12 posts held, back to 11 May 2026 — 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.
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.
| Window | Rolling 30 days · latest post in window 10 August 2026 |
|---|---|
| Posts held | 12 (11 May 2026 – 10 August 2026) |
| Views total | 1 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Aug 2026, 05:30 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.
Lifetime counters from Telegram’s own channel header, read 10 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 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 1reactions 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 11 May 2026 to 10 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.
来自速搜推荐 @SSOU 📢碧海清波 📢欧博官网 亚星官网 欧博... 📢超粒方 📢亡灵大盗--双喜临门--... 📢AG私网 卡卡湾私网 万... 📢深圳修车 深圳外围 深圳... 📢抖音- 韩国- 深圳-日... 📢长青~中国传统文化 📢日本美女鉴赏大全|性感写... 📢赌球网站|开元棋牌 |德... 📢吃瓜 猎奇 黑料 📢皇冠私网🅱️皇冠登1�... 📢环球360网址 环球36... 📢欧博私网 欧博会员 亚星... 📢salena 👉流量互推规则介绍💥 以下是广告推荐 📢 飞驰号铺 [主营：飞机号 开会员 代充星星] 📢东南亚今日头条|新闻|爆料|悬赏|通缉|吃瓜缅甸妙瓦底大揭 📢专业Telegram账号交易平台🔥热门社交媒体账号交易 🥇西湖娱乐城✅老品牌包出款✅出款超10亿U 📢 全网最全面、最便宜的自助引流服务 🇨🇳 简体中文包 —————————-- 🔥将 @TonGroupHelpBot 设置为频道管理员
東京上門出勤情報|香奈 · 尋夢園 pinned a photo
🌸 貼心提醒 建議提前 1～3 天預約，女孩們都是利用空檔時間出勤，提前安排的話，也能讓她們更從容地調整行程。 另外，21:00 之後是最熱門的預約時段，常常會比較快額滿。 如果已經有預計的日期，歡迎提早告訴我，我會盡力幫您安排到理想的時間與喜歡的女孩。💕
📍 JP・東京 AA-2601101 📏 155cm｜21歲｜D罩杯 ✨ 甜美嬌小D罩杯女孩 可愛又親切的21歲小隻馬，講話軟軟的很有親和力。身材嬌小卻曲線玲瓏，互動起來溫柔舒服，讓人很容易放鬆，是那種可愛又討喜、會讓人想一直聊天疼愛的類型。 📲 Gleezy: hi77 🔗 https://gleezy.net/hi77 💌 TG 聯絡 @one181 📝 新手指南 @one1852 #日本泡泡浴 #美乳 #内射 #大阪上门 #东京外送
📍 JP・東京 AA-2601102 📏 160cm｜25歲｜G罩杯 ✨ 豐滿性感G罩杯姐姐 氣質溫柔又帶點成熟魅力的25歲女孩，160cm身高比例很好，擁有飽滿豐挺的G罩杯。互動時細心體貼，聲音柔軟舒服，是那種能讓人徹底放鬆、充滿女人味的療癒系類型。 📲 Gleezy: hi77 🔗 https://gleezy.net/hi77 💌 TG 聯絡 @one181 📝 新手指南 @one1852 #日本泡泡浴 #美乳 #内射 #大阪上门 #东京外送
📍 JP・東京 AA-2601103 📏 155cm｜24歲｜D罩杯 ✨ 清新可愛D罩杯女孩 24歲清純可愛風格的嬌小女孩，155cm的身材小巧精緻，D罩杯形狀漂亮。個性溫和親切，互動時會讓人感覺輕鬆愉悅，是那種笑容甜美、容易相處、想再見面的女孩。 📲 Gleezy: hi77 🔗 https://gleezy.net/hi77 💌 TG 聯絡 @one181 📝 新手指南 @one1852 #日本泡泡浴 #美乳 #内射 #大阪上门 #东京外送
📍 JP・東京 AA-2601104 📏 160cm｜23歲｜F罩杯 ✨ 活力甜美F罩杯女孩 23歲青春活潑又帶點甜美的女孩，160cm身材勻稱，擁有柔軟飽滿的F罩杯。講話節奏輕快舒服，互動過程很自然開心，是那種陽光又貼心、讓人感覺愉悅的類型。 📲 Gleezy: hi77 🔗 https://gleezy.net/hi77 💌 TG 聯絡 @one181 📝 新手指南 @one1852 #日本泡泡浴 #美乳 #内射 #大阪上门 #东京外送
📍 JP・東京 AA-2601105 📏 165cm｜21歲｜F罩杯 ✨ 高挑清新F罩杯女孩 21歲高挑修長的清新女孩，165cm身高比例出色，擁有形狀漂亮的F罩杯。氣質乾淨舒服，講話溫柔有禮，互動時給人放鬆且愉快的感覺，是那種氣質佳、讓人想多接觸的女孩。 📲 Gleezy: hi77 🔗 https://gleezy.net/hi77 💌 TG 聯絡 @one181 📝 新手指南 @one1852 #日本泡泡浴 #美乳 #内射 #大阪上门 #东京外送
❤1
Channel name was changed to «東京上門出勤情報|香奈 · 尋夢園»
📍 JP・東京25051104 📏 157cm｜24歲｜F罩杯 ✨ 嬌小反差感F罩杯女孩 身高雖然小隻，但身材非常有料，曲線感很突出。個性偏黏人可愛型，很會撒嬌，整體相處氛圍輕鬆又有親近感。 📲 Gleezy: hi77 🔗 https://gleezy.net/hi77 💌 TG 聯絡 @one181 📝 新手指南 @one1852 #日本泡泡浴 #美乳 #内射 #大阪上门 #东京外送
📍 JP・東京25051105 📏 166cm｜22歲｜D罩杯 ✨ 高個氣質型長腿女孩 整體比例很好，腿部線條特別漂亮。外型偏冷艷感，但熟了之後其實很好聊天，屬於越看越耐看的類型，很有成熟魅力。 📲 Gleezy: hi77 🔗 https://gleezy.net/hi77 💌 TG 聯絡 @one181 📝 新手指南 @one1852 #日本泡泡浴 #美乳 #内射 #大阪上门 #东京外送
📍 JP・東京25051106 📏 163cm｜22歲｜F罩杯 ✨ 溫柔系F罩杯女孩 講話輕聲細語，很有女友氛圍。身材勻稱漂亮，互動時給人很舒服放鬆的感覺，是那種會讓人想再見面的類型。 📲 Gleezy: hi77 🔗 https://gleezy.net/hi77 💌 TG 聯絡 @one181 📝 新手指南 @one1852 #日本泡泡浴 #美乳 #内射 #大阪上门 #东京外送
Showing the 12 most recent of 12 posts we hold for @one1812. 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 — 588,613 of 1,176,251entries 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 29 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“東京上門出勤情報|香奈 · 尋夢園” (@one1812), 59 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/one1812.
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.