Channel
@osaka670
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
224subscribers
+85 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003734379340 |
|---|---|
| Type | Channel |
| Username | @osaka670 |
| Created | Between 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 11 October 2026 |
| On Telegram | t.me/osaka670 |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 24 September 2026 and assigned it the closest of 31 fixed categories, at 54% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Oct 2026, 18:37 | 224 | +18 |
| 1 Oct 2026, 12:54 | 206 | +15 |
| 17 Sept 2026, 18:56 | 191 | +10 |
| 9 Sept 2026, 06:42 | 181 | +3 |
| 31 Aug 2026, 09:02 | 178 | +1 |
| 24 Aug 2026, 22:09 | 177 | +9 |
| 16 Aug 2026, 20:29 | 168 | +25 |
| 8 Aug 2026, 21:45 | 143 | no change |
| 8 Aug 2026, 11:12 | 143 | +4 |
| 7 Aug 2026, 14:43 | 139 | first reading |
9 posts held, back to 7 August 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 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 9 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
❤️ 謝謝這份寶貴的信任 好開心吖~遇到一位弟弟從網站上看到我的咨詢加入頻道，昨天成功預約了三個小時，聊天時他坦白說： 💬 「我進頻道大概一個禮拜了」 才知道原來他不是衝動預約，而是觀察了很久： 看我發的內容、看客人反饋、看我是不是真實做事，最後才放心把「第一次」交給靜香。 其實，第一次預約會擔心、怕踩雷、怕被騙， 這都非常正常！尤其隻身在國外，本來就該謹慎。 所以，如果你也有顧慮，真的沒關係！ 如果你也是一樣的情況，不用急著預約， 歡迎你先留在頻道「觀察靜香」： 看看我平常發的女孩資訊 📋 看看客人對我的真實反饋 💬 也可以隨時來找我聊聊天以及了解咨詢 ☺️ 信任不是靠一句口頭上的「相信我」， 而是靠每天誠實經營累積出來的。 所以靜香不怕你觀察，反而很歡迎你來看！ 這次弟弟預約了 3 個小時，順利完成 ❤️。 比起預約成功，更讓我高興的是在這麼多選擇裡，他願意信任我。 如果你也是第一次來日本、有很多疑問，別擔心，不用…
#老朋友的信任和支持 每次來日本出差都會找靜香 交給靜香安排 有些默契，真的不用多說。 舒服、順、對了，就會再出現。 謝謝哥哥的信任，把時間再次交給我🫶
正確的消費方式（本店消費模式）： ✔️ 見面滿意 、現金消費、不強迫消費、無隱形消費 ❌不匯款 ❌不轉賬 ❌不買點數 🐾正妹類型： 淫蕩少婦⭐貧乳幼齒⭐專櫃正妹⭐ 單親媽媽⭐大學校花⭐火辣女模⭐ 風騷護士⭐展辣車妹⭐裸露女教師⭐ 火辣空姐⭐幼齒蘿莉⭐饑渴美魔女⭐
觀察了靜香一段時間 覺得靜香值得相信，這次放假直接來預約 昨天約完之後說還想要再次見到她！😍 一試成主顧，說得就是這種情況吧哈哈哈 （本店回約某個女生不需要額外加本指名費喲~） 溫馨提示： 假期很多酒店都滿房 特別是情人酒店，房間不好找，建議大家提前出門 遇到🈵房，也有時間找其他的酒店
新朋友必看｜新手常見問題指南 https://t.me/yy1985/3928
感謝哥哥們的熱烈捧場與信任 💕 昨天剛體驗完的哥哥， 早上來又收到哥哥的消息了嘿嘿~ 一試成主顧！ 這位哥哥一開始最大的煩惱其實不是選妹妹🤣 而是： 🏩 不知道哪裡有愛情酒店 🏩 不知道怎麼開房 🏩 附近哪一家比較方便 通通不用擔心！交給靜香一手包辦 🫡 只要告訴我你靠近哪個車站，靜香直接幫你精選推薦、指引最方便的愛情酒店，保證把你和妹子安排得妥妥當當、直接送進房門！ 📥 唯一認證預約通道：@chi669 🏛 官網看照片： www.av669jp.com
🌟#日本修車 #日本風俗🌟 「番號 8083—鑽石💎」 ● 11萬/60分鐘 第二節半價 ● 169/F/24歲/49kg ● 標籤：#大阪 /退役空姐 高挑長腿、豐滿胸型、氣質滿分，輕輕一抱就能感受到胸前的份量，低頭就能聞到她身上的淡香。 🦋🖤🦋🖤🧸🖤🦋🖤🦋 ⭐ chi669 🌐 @qin670 🎀 東京 🎀 大阪 🎀 客評 🌟 一鍵加入靜香所有頻道 🌟 請點擊加 Gleezy福利群組
🌟#日本修車 #日本風俗🌟 「番號 8081—水晶🔮」 ● 160/B/21歲/40kg ● 標籤：#大阪 /OL新人 外表像鄰家小妹，適合喜歡把女生整個圈在懷裡的你。 🦋🖤🦋🖤🧸🖤🦋🖤🦋 ⭐ chi669 🌐 @qin670 🎀 東京 🎀 大阪 🎀 客評 🌟 一鍵加入靜香所有頻道 🌟 請點擊加 Gleezy福利群組
🚫【在日本常見的詐騙手法】 —— 想玩得開心，請先了解如何避坑 1️⃣ 超低價進房 → 項目加價詐騙 用「1萬本番」「3萬包夜」吸引人，一進房卻開始額外加收： 👉「摸一下加3000、口交加1萬、本番加5萬」 不付就恐嚇、不讓走，甚至喊出「最低消費」。 ➡️表面便宜，實際暴力加價。 2️⃣ 提前付款陷阱 以「怕被放鴿子」為由，要你先付「保證金」才能見面。 有些人真的去了現場，結果卻被釣魚威脅，甚至捲入糾紛。 ➡️見面前一律不轉帳！ 3️⃣ 店鋪黑幕操作 進店後才發現「照片裡的小姐沒來」「要加錢才有服務」「VIP才有全套」。 有時候還會被強迫換人、付兩次錢。 ➡️價格不透明，馬上退出！ 4️⃣ 點數卡／ATM詐騙 要你去便利商店買點數卡，或操作ATM儲值幾萬日圓，理由是「身份驗證」或「服務保證」。 還可能在你拒絕後打電話恐嚇你。 ➡️這類詐騙在日本也很猖獗，務必警覺！ 5️⃣ 被釣去現場 → 勒索威脅 對方用性感照騙你去某…
Showing the 9 most recent of 9 posts we hold for @osaka670. 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.
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.
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 11 October 2026 — this entry's latest reading, not the date you are reading this.
“静香外送茶｜🏯大阪出張專區 #日本外送 #日本泡泡浴” (@osaka670), 224 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/osaka670.
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.