Channel
@XTM667
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
117subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001904839302 |
|---|---|
| Type | Channel |
| Username | @XTM667 |
| Created | Between 1 March 2023 and 31 January 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 23 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 23 August 2026 |
| On Telegram | t.me/XTM667 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 23 Aug 2026, 21:13 | 117 | +1 |
| 9 Aug 2026, 05:17 | 116 | no change |
| 7 Aug 2026, 14:14 | 116 | first reading |
14 posts held, back to 1 December 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.
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 6 August 2026 |
|---|---|
| Posts held | 14 (1 December 2025 – 6 August 2026) |
| Views total | 13 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 05:17 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.
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 2 of the 14 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 14 most recent posts we hold, published 1 December 2025 to 6 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.
關於偷拍這件事情 ⚠️ 重要提醒：請務必注意❗️ 1️⃣ 不能偷拍❗️ 2️⃣ 不能偷拍❗️ 3️⃣ 真的不能偷拍❗️ 這絕對不是單純的店規或限制，而是因為在日本法律中，偷拍本身就是違法行為。一旦觸犯，後果非常嚴重，不僅會影響到你個人，甚至可能會帶來法律責任。 如果你真的有拍攝的需求，請一定要提前告訴我。因為我們這邊確實有部分女孩是可以接受、也願意配合拍攝的，但前提是需要事前溝通與同意。這樣既能保護你自己，也能保障女孩子的感受與權益。 請大家一定要明白 • 凡攜帶或使用任何攝影器材（如智慧眼鏡、智慧手錶、微型攝影機、攝影筆等），一律視同偷拍處理。 • 如女孩發現，拍攝設備將予以沒收，並依女孩要求需賠償 20～30萬日圓 給女孩本人。 最後再次強調，如果真發現有偷拍的情況，除了法律責任外，還會有 20-30萬日幣的賠償。這不僅是保護女生，也是保護的整個環境。 請大家一定要遵守，互相理解與尊重，才能開心、安心地享受這段…
東京大阪美月夢華坊🇯🇵新手指南 pinned a photo
關於提前預約 為什麼提前預約 有什麼服務 特殊服務價位 關於拒絕女生 關於女生價位 關於偷拍被罰款 關於女生照片打碼 關於包夜的價位算法 外國人也可以預約嗎？ 關於拒絕接受入珠客人 為什麼提前預約會比較好 為什麼需要把費用交給司機」的完整說明 日本東京|大阪女子出勤 大阪： t.me/NN3255 東京： t.me/JP9921 聯絡Gleezy ：PPA3 ☺️美月這裡是專門提供外國客人在日本東京大阪享受性愛風俗服務 提供酒店.住宅的上門外送性愛服務. 提供.東京15區 大阪 【女子提供本人照片100% 現金交易（日幣）】 💋约会地点：住宅/饭店/酒店/愛情旅店 （交通費3000-8000） 🚘东京派送區域： 荒川區 北區 墨田區 台東區 江東區 豐島區 文京區 千代田區 中央區 新宿區 港區 中野區 澀谷區 目黑區 品川區 🚘大阪派送區域： 此花区 …
為什麼需要把費用交給司機」的完整說明 很多第一次接觸日本外約的哥哥， 一開始對流程比較陌生， 多少都會有些疑問： 「為什麼不是妹妹自己過來？ 「為什麼會有司機？ 「為什麼超過10萬日元，需要先把費用交給司機或者先存起來？ 所以美月這邊統一和大家說明一下 🚘 為什麼會安排司機？ 因為日本交通費本身就比較高， 尤其深夜、跨區、臨時叫車， 價格其實浮動很大 所以這邊才會統一安排接送 讓交通費固定化 不會因為酒店距離不同而臨時加價 同時也能避免： ❌ 臨時叫不到車 ❌ 妹妹遲到 ❌ 行程混亂 ❌ 深夜移動不安全 整個流程也會更穩定 妹妹能用比較好的狀態陪伴哥哥 ━━當然，也有部分女生是自己叫車前往的━━ 🔍 為什麼超過10萬日元，要先把費用交給司機或者先存起來？ 其實很多哥哥第一次聽到時，會擔心是很正常的 畢竟人在異地，第一次接觸外約， 多少都會想： 「如果先給錢怎麼辦？ 「會不會服務變差？ 「會不會拿了錢就離開…
最近很多第一次來日本的哥哥會問： 「外國人也可以預約嗎？」☺️ 「需要定金嗎？可以上門嗎？」☺️ 答案是可以的✨ 我們這邊安排的都是日本籍女生， 而且沒有特別限制客人的國籍～ 海外旅客、華人哥哥也都可以正常預約🌸 而且是高端外約酒店上門服務。 主要就是外送上門服務。 整體互動會更自然、自由一些🌸 付款方式也是現場現金支付， 不需要事前轉帳，安心很多✨ 有興趣都可以直接私訊美月 @An98363🫶 Gleezy ／ Telegram 都找得到我唷～
很多哥哥其實都有一個誤區—— 會覺得「我今天想約，應該就能約到吧？」 但實際上，日本這邊是完全預約制＋檔期制， 真的不是臨時想就一定有。 簡單講一個很現實的邏輯👇 👉 你越早講，我們越好幫你安排 👉 你越晚說，就只能當下空閒的 越早安排，選擇越多；越晚決定，就越靠運氣。 一個很固定的規律👇 👉 越滿意的客人，幾乎都是提前安排的 👉 越容易覺得「還好」的，大多是臨時決定 原因很簡單： 當你有時間的時候👇 ✔️ 可以慢慢挑 ✔️ 可以比感覺 ✔️ 可以找到真的適合自己的 但當你是臨時才想約👇 👉 能配到時間就不錯 👉 能約到人就已經算運氣好 久了就會變成一種落差： 👉 不是體驗不好 👉 而是「沒有到你原本期待的那個程度」 我們最常聽到的一句話就是： 👉「早知道我早點問你。」 但這句話通常都是在結束之後才出現。 🌸 所以如果你問我最直接的建議： 👉 有想法的時候，就先來問 👉 不用馬上下決定，但先了解、先卡時間 …
美月有話說： 講一個比較關鍵的點—— 如果你本身是比較挑感覺、而且有明確標準的人， 其實很容易讓你一直落在「差一點」的狀態。 因為外送上門很吃當下互動跟氛圍， 不一定每次都能剛好打中你的理想。 有時候條件是OK的， 但只要有一個細節沒對到， 你心裡就會開始扣分。 幾次之後你就會發現， 不是沒有適合你的，而是你越來越難被滿足。 所以與其讓你一直試錯， 不如一開始就把方向抓準。 你先跟我講清楚你的喜好、在意點、雷點， 我可以直接幫你篩選、幫你避掉不適合的， 再幫你安排更穩定的方式。 這樣不只成功率高， 整體體驗也會更接近你要的感覺。 畢竟這種東西不是花次數在賭， 而是選對方向，才會一次就中。
其實我一直覺得，約會最重要的一點，就是 彼此之間要好好溝通。 如果我們第一次合作，你覺得我推薦的女生不太合適，或者跟你想像的不太一樣，真的可以直接跟美月說。 因為如果你沒有說出來，我其實也不知道問題出在哪裡。 只要你願意告訴我你的想法，我都可以再根據你的需求重新推薦更適合的女生。 但如果什麼都沒有說就突然消失，我有時候也會以為你只是隨便問問而已，這樣其實很容易產生誤會。 另外也想拜託各位哥哥，如果你本身不太喜歡太多來回聊天，其實一開始把需求說清楚會更方便，例如： 👉 想要什麼類型的女生 👉 預算大概多少 👉 什麼時間方便見面 這樣我就可以更快、更準確地幫你安排到合適的人選。 我多問幾句，其實只是希望安排的女生，是你真的會喜歡的。 同時也想跟大家說一個很重要的觀念。 每個地區、每個國家的女生，其實都有不同的特點和魅力。 在日本約會的時候，盡量不要完全用自己原本國家的審美標準，去直接跟日本女生做比較。既然都來到日本了，…
#包夜的意義，不只是時間 有些人選擇包夜，不是因為慾望，而是因為孤單。 ✨時間充裕 可以聊天、可以沉默、可以慢慢熟悉彼此。 不用急著進入狀態。 ✨互動更自然 熟悉之後的親密，比匆忙來得更有溫度。 ✨陪伴感最重要 有人在身邊，哪怕只是一起睡著，都會讓人安心。 ✨整體更完整 一晚的節奏，從開始到結束都在掌握之中。 包夜，是一種陪伴。 也是對自己的一種溫柔。
別讓錯誤的審美標準，錯過日本女孩的獨特魅力！ 每個國家的審美本來就不一樣，就像每個國家都有自己獨特的風景和文化一樣🎨。顏值、膚色、身高，甚至流行的感覺與氣質，都是由當地的文化、生活環境塑造出來的💡。所以，千萬不要用自己國家的「標準」，來定義日本的女生哦！ 當你來到日本，如果還帶著自己國家的眼光，甚至拿其他國家的標準來對比，很容易就會變成——看誰都不順眼，看誰都不滿意😣。但這並不是因為日本女生不好，而是因為你一開始就用了錯誤的參照標準❌！ 想像一下：如果你拿越南的物價去和東京的物價比較，當然會覺得差距巨大、不合理🛒💰。但對於長期生活在東京的人來說，那就是再正常不過的日常價位了。同樣的道理，日本女生的美，也是需要用日本的視角去欣賞的🌟。 換個角度，換個標準，你才能真正體會到日本女生的魅力🌸。她們可能沒有你熟悉的「標準美人」特徵，但她們的自在、細膩、獨到的氣質，正是她們最迷人的地方😍。不要讓錯誤的比較方式，把自己限制住，也錯過…
#價位的區別 @An98363 夜市牛排 150 元一份，吃飽而已； 餐廳牛排 1500 元一份，吃的是品質與享受。 妹妹也是如此，便宜的或許能解渴， 但高品質的才會讓你回味無窮。 報價高，不是宰客，是保證
#一直在提醒 但是也還在存留很多遺憾 最近總有寶寶們臨時來問我還有沒有女生可以約 或者是每次介紹了 之後又說想一想 考慮一下 明天在看看的 然後美月又一遍一遍的確定時間 是否可以 是不是給你造成了一種我很急切的感覺呢？如果是這樣那真的抱歉 但是我想要的是你來這一次能好好的享受 體驗的女生的服務 而不是帶著遺憾回去 #及時行樂 請提前預約 我不是一定要確定你的行程，只是因為很多寶寶臨時約往往是帶著遺憾回去，才會一次次一遍遍的詢問。 但..是.. 往往就是 臨時約，最容易錯過最對味的類型。 臨時約，你可能收到的是遺憾、 太臨時約不是你想要預約的女生被預約走了， 就是已經沒有可以約的需要等明天，但是也很多客人第二天的飛機就沒有辦法繼續約了 那這樣帶著沒有預約到喜歡的女生 ， 沒有得到舒壓且不是很遺憾 ， 來都來為什麼要因為沒有提前預約而給自己的旅行帶一點灰色的遺憾呢 ， 及時行樂 請提前預約 #寶…
Showing the 12 most recent of 14 posts we hold for @XTM667. 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 — 943,856 of 1,585,237entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
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 23 August 2026 — this entry's latest reading, not the date you are reading this.
“東京大阪美月夢華坊🇯🇵新手指南” (@XTM667), 117 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/XTM667.
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.