Telegram RegisterThe public register of Telegram
Telegram profile photo for 🇯🇵梦雅阁東京/大阪酒店出張|櫻花外送茶上門|Tokyo/Osaka暗黑-泡泡浴風俗

Channel

🇯🇵梦雅阁東京/大阪酒店出張|櫻花外送茶上門|Tokyo/Osaka暗黑-泡泡浴風俗

@yuluqin1686

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

565subscribers

+40 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001648111484
TypeChannel
Username@yuluqin1686
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live18 September 2026
Measurements held9
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/yuluqin1686

Topic

Adult — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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.

Growth

524565544.57 August 2026 — 525 subscribers7 August 2026 — 524 subscribers8 August 2026 — 524 subscribers13 August 2026 — 526 subscribers20 August 2026 — 525 subscribers26 August 2026 — 532 subscribers1 September 2026 — 547 subscribers10 September 2026 — 560 subscribers18 September 2026 — 565 subscribers7 August 202618 September 2026
9 measurements spanning 42 days, net +40. 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 518–571 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 06:59565+5
10 Sept 2026, 15:01560+13
1 Sept 2026, 11:16547+15
26 Aug 2026, 09:14532+7
20 Aug 2026, 10:09525-1
13 Aug 2026, 17:55526+2
8 Aug 2026, 04:01524no change
7 Aug 2026, 15:56524-1
7 Aug 2026, 10:25525first reading

Engagement

13 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 13 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
15s
Average length
15s

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

8 Aug 2026, 01:51 UTC4 viewsread 8 August 2026
Photo

💖東京 番號A885 💖155cm·Bcup·43kg·19歲 貧乳小隻馬 配合度高,互動自然 🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀 預約方式: 🖤Telegram:@nai881🖤 您的專屬性福小助手

8 Aug 2026, 01:01 UTC6 viewsread 8 August 2026
Photo

💖東京 番號A884 💖163cm·Fcup·46kg·24.歲 水滴奶,主要服務技術派,希望服務熱情且全程被帶動的哥哥不要錯過 🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀 預約方式: 🖤Telegram:@nai881🖤 您的專屬性福小助手

8 Aug 2026, 00:31 UTC5 viewsread 8 August 2026
Photo

💖東京 番號A883 💖161cm·Dcup·47kg·32歲 外表端莊大方,氣質溫柔如春風 身材勻稱自然,曲線柔和優美 帶著輕熟韻味,散發小女人的魅力 🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀 預約方式: 🖤Telegram:@nai881🖤 您的專屬性福小助手

7 Aug 2026, 23:31 UTC5 viewsread 8 August 2026
Photo

💖大阪 番號B882 💖173cm·Ecup·46kg·23歲 高挑纖細的身形比例出眾,氣質乾淨俐落 🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀 預約方式: 🖤Telegram:@nai881🖤 您的專屬性福小助手

7 Aug 2026, 22:35 UTC5 viewsread 8 August 2026
Photo

💖大阪 番號B881 💖155cm·Dcup·43kg·20歲 乖巧聽話 第一次下海 無刺青 不抽菸 乖巧好配合 經驗不多 需要調教 小穴敏感很緊 要約的哥哥 不要太粗魯喲 🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀 預約方式: 🖤Telegram:@nai881🖤 您的專屬性福小助手

7 Aug 2026, 12:19 UTC11 viewsread 8 August 2026
Forwarded from @nai4626

🤩哥哥們看過來~奈奈來整理一下自己的「秘密基地入口」啦 最近有些哥哥問: 「奈奈到底哪個號是真的呀?」 「頻道好多,要看哪一個呀?」 所以我偷偷整理了一份《奈奈官方導航地圖》 以後找我、看資訊,不用像在迷宮探險啦~ 🦋聯絡奈奈🦋⤵️ 主號: @nai881 備用小號: 1️⃣@xia421 2️⃣@xia0712 3️⃣@nai993 小助理⤵️ @tea489 (PS:如果主號忙碌,哥哥可以找備用號喔~) 🚨官方資訊頻道 主頻道:https://t.me/younai301 頻道2:https://t.me/yuluqin1686 English:https://t.me/nai523 🇯🇵日本語:https://t.me/nai489 🐇不同主題的小天地⤵️ 奈の日常:https://t.me/nai852 大阪の妹妹:https://t.me/nai152415 🗼 東京の妹妹:https://t.me/n…

7 Aug 2026, 11:54 UTC10 viewsread 8 August 2026
Forwarded from @nai852

真的不能空腹喝咖啡,真的很难受呜呜呜,可能是对咖啡不耐受,也不是痛就是很难形容的感觉,肚子不舒服?头有点晕?反正就是这种,不痛不痒,但是难受,咖啡我恨你😭😭

7 Aug 2026, 08:35 UTC12 viewsread 8 August 2026
Video

櫻花妹真的都很可愛有活力耶! 大家覺得呢~ #青春感滿滿,嘿嘿🚨

7 Aug 2026, 08:35 UTC14 viewsread 8 August 2026
Photo

看到海外哥哥的訊息,奈奈真的超開心🥰 #每位哥哥喜歡的類型都不一樣,有人喜歡可愛系,也有人偏愛成熟人妻、輕熟姐姐 只要把喜好告訴奈奈,我都會盡量幫哥哥找到最適合的妹妹,不用盲選、不用碰運氣 #謝謝海外哥哥一直以來的支持呀!🩷 有你們的信任,奈奈才有動力一直努力下去~ 以後也會繼續幫大家挖掘更多高顏值、互動好、服務棒的優質妹妹 希望每位哥哥來找奈奈,都能開開心心來、滿意而歸呀~(。•ᴗ•。)♡

7 Aug 2026, 08:10 UTC11 viewsread 8 August 2026
Photo

🤓🤓🤓🤓🤓🤓 #包夜福利 哥哥們這個福利還在的喔! #其實不少哥哥都會選擇這個方案, 時間比較充裕,不用趕行程,整個體驗也會更放鬆、更盡興 目前 #高端級「買4送2」活動 還在進行中, 想安排 6 小時 的哥哥,都可以來問奈奈幫你介紹適合的妹妹唷🪽 有喜歡的類型也可以先跟奈奈說, 可愛、小隻、性感、氣質、高挑…奈奈都會幫哥哥推薦最適合的,不用自己慢慢找 歡迎提前預約,#奈奈幫哥哥安排好最舒服的時間

7 Aug 2026, 07:49 UTC9 viewsread 8 August 2026
Photo

#預約流程 很多哥哥一開始都會問我: 「#要怎麼預約呀?」 其實很簡單,只要填寫幾個基本資訊就可以囉~ ✅想約的時間 ✅時長 ✅ 預算 ✅ 喜歡的類型 ✅ 地區 哥哥填寫完成後,奈奈就可以依照你的需求,#更有針對性地推薦適合的妹妹,不用一個一個慢慢挑,也能節省很多時間🩷

Showing the 12 most recent of 13 posts we hold for @yuluqin1686. 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.

Forward network

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.

Mentions

Named by 4 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 18 September 2026 — this entry's latest reading, not the date you are reading this.

“🇯🇵梦雅阁東京/大阪酒店出張|櫻花外送茶上門|Tokyo/Osaka暗黑-泡泡浴風俗” (@yuluqin1686), 565 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/yuluqin1686.

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.