Channel
@yy1985
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Posts · Citations · Cite this entry
4,457subscribers
+27 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002432052775 |
|---|---|
| Type | Channel |
| Username | @yy1985 |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/yy1985 |
Adult — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 53% 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @yy1985/6831 · this entry6 Aug 2026, 12:50 UTC | @chichi670/99736 Aug 2026, 13:11 UTC | 1.00 | 20 minutes |
| @yy1985/6836 · this entry6 Aug 2026, 16:21 UTC | @chichi670/99786 Aug 2026, 16:54 UTC | 1.00 | 32 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @chichi670 | 10 (8/8 hand-verifiable sample passed) | 1.00 | 21 minutes | this entry (10–0) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 10 comparable posts for this entry, running 6 August 2026 to 7 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Across the whole group of 2, the earliest publisher we hold is @yy1985 — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 13:42 | 4,457 | +19 |
| 8 Aug 2026, 07:25 | 4,438 | +8 |
| 7 Aug 2026, 14:18 | 4,430 | first reading |
24 posts held, back to 6 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 5 pagesof 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 8 August 2026 |
|---|---|
| Posts held | 24 (6 August 2026 – 8 August 2026) |
| Views total | 2,043 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 18:06 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.
❤️ 謝謝這份寶貴的信任 好開心吖~遇到一位弟弟從網站上看到我的咨詢加入頻道，昨天成功預約了三個小時，聊天時他坦白說： 💬 「我進頻道大概一個禮拜了」 才知道原來他不是衝動預約，而是觀察了很久： 看我發的內容、看客人反饋、看我是不是真實做事，最後才放心把「第一次」交給靜香。 其實，第一次預約會擔心、怕踩雷、怕被騙， 這都非常正常！尤其隻身在國外，本來就該謹慎。 所以，如果你也有顧慮，真的沒關係！ 如果你也是一樣的情況，不用急著預約， 歡迎你先留在頻道「觀察靜香」： 看看我平常發的女孩資訊 📋 看看客人對我的真實反饋 💬 也可以隨時來找我聊聊天以及了解咨詢 ☺️ 信任不是靠一句口頭上的「相信我」， 而是靠每天誠實經營累積出來的。 所以靜香不怕你觀察，反而很歡迎你來看！ 這次弟弟預約了 3 個小時，順利完成 ❤️。 比起預約成功，更讓我高興的是在這麼多選擇裡，他願意信任我。 如果你也是第一次來日本、有很多疑問，別擔心，不用…
#老朋友的信任和支持 每次來日本出差都會找靜香 交給靜香安排 有些默契，真的不用多說。 舒服、順、對了，就會再出現。 謝謝哥哥的信任，把時間再次交給我🫶
正確的消費方式（本店消費模式）： ✔️ 見面滿意 、現金消費、不強迫消費、無隱形消費 ❌不匯款 ❌不轉賬 ❌不買點數 🐾正妹類型： 淫蕩少婦⭐貧乳幼齒⭐專櫃正妹⭐ 單親媽媽⭐大學校花⭐火辣女模⭐ 風騷護士⭐展辣車妹⭐裸露女教師⭐ 火辣空姐⭐幼齒蘿莉⭐饑渴美魔女⭐
觀察了靜香一段時間 覺得靜香值得相信，這次放假直接來預約 昨天約完之後說還想要再次見到她！😍 一試成主顧，說得就是這種情況吧哈哈哈 （本店回約某個女生不需要額外加本指名費喲~） 溫馨提示： 假期很多酒店都滿房 特別是情人酒店，房間不好找，建議大家提前出門 遇到🈵房，也有時間找其他的酒店
新朋友必看｜新手常見問題指南 https://t.me/yy1985/3928
感謝哥哥們的熱烈捧場與信任 💕 昨天剛體驗完的哥哥， 早上來又收到哥哥的消息了嘿嘿~ 一試成主顧！ 這位哥哥一開始最大的煩惱其實不是選妹妹🤣 而是： 🏩 不知道哪裡有愛情酒店 🏩 不知道怎麼開房 🏩 附近哪一家比較方便 通通不用擔心！交給靜香一手包辦 🫡 只要告訴我你靠近哪個車站，靜香直接幫你精選推薦、指引最方便的愛情酒店，保證把你和妹子安排得妥妥當當、直接送進房門！ 📥 唯一認證預約通道：@chi669 🏛 官網看照片： www.av669jp.com
🌟#日本修車 #日本風俗🌟 「番號 8084—鑽石💎」 ● 169/H/24歲/50kg ● 標籤：#東京 /網美 明星臉、身材是罪惡感，H杯的份量感連衣服都遮不住，走在路上回頭率爆表，近距離更是讓人呼吸困難。 🦋🖤🦋🖤🧸🖤🦋🖤🦋 ⭐ chi669 🌐 @qin670 🎀 東京 🎀 大阪 🎀 客評 🌟 一鍵加入靜香所有頻道 🌟 請點擊加 Gleezy福利群組
🌟#日本修車 #日本風俗🌟 「番號 8083—鑽石💎」 ● 11萬/60分鐘 第二節半價 ● 169/F/24歲/49kg ● 標籤：#大阪 /退役空姐 高挑長腿、豐滿胸型、氣質滿分，輕輕一抱就能感受到胸前的份量，低頭就能聞到她身上的淡香。 🦋🖤🦋🖤🧸🖤🦋🖤🦋 ⭐ chi669 🌐 @qin670 🎀 東京 🎀 大阪 🎀 客評 🌟 一鍵加入靜香所有頻道 🌟 請點擊加 Gleezy福利群組
🌟#日本修車 #日本風俗🌟 「番號 8082—白金💠」 ● 148/B/19歲/40kg ● 標籤：#東京 /現役女大生 臉小、身更小，像從偶像團體走出來的隱藏成員，嬌小到穿制服都顯幼，年輕到眼神還帶點害羞。 🦋🖤🦋🖤🧸🖤🦋🖤🦋 ⭐ 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 12 most recent of 24 posts we hold for @yy1985. 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 — 46,780 of 1,151,006entries 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 8 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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“🇯🇵靜香日本Tokyo & Osaka外送茶-上門服務-出張風俗店🍵” (@yy1985), 4,457 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/yy1985.
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.