Channel
@nainai865
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
20subscribers
+2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002590682400 |
|---|---|
| Type | Channel |
| Username | @nainai865 |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/nainai865 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 20:54 | 20 | +1 |
| 24 Aug 2026, 08:06 | 19 | +1 |
| 11 Aug 2026, 19:15 | 18 | no change |
| 7 Aug 2026, 21:19 | 18 | first reading |
5 posts held, back to 13 November 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 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 5 posts for this entry, the most recent from 2 August 2026. An engagement rate over an empty window would be a number about nothing.
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 5 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 13 November 2025 to 2 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.
✨【 純白下的豐盈慾望 】✨ ━━━━━━ 💕 ━━━━━━ 💕 名前： 姫川 (24) 💖 スペック： 163cm / Eカップ 🤪 福利： 預約現折 6000 🥰 職業： 醫美顧問 ━━━━━━ 💕 ━━━━━━ 🗝「看似高冷的精緻外表下，藏著只想為你濕透的火熱靈魂。」 👉 私信預約 📱 TG: @Japan8n 🫶🫶 👉 私信預約 ⭐️Gleezy: Japan8n 💌 中文版出勤班表 💌日語版出勤班表 ✍️ 客評分享區 🇯🇵 日本动漫里番🔞 ⭐️: 完整版出勤表 / 出勤表の完全版 🍀 #日本外約 #東京大阪上門服務 #東京泡泡浴 #大阪外送茶 #東京外約 #日本歌舞伎町 #日本旅遊 #大阪デリヘル #出張サービス #日本叫小姐 #大阪东京旅
奈奈是不會辜負每一個相信我的人 小姐很可愛 服務很好 長得像工藤拉拉 可私信我看本人照 👉 私信預約 TG: @Japan8n 🫶🫶
近期有計劃來東京大阪約的帥哥們 可以提前預約小姐喲 如果沒有提前預約 只能安排當下有時間的小姐啦 這樣選擇會比較少 或者沒有妹可以安排喲 預約是不需要收取費用的 費用奈奈 這邊先幫忙墊付 頻道裡面的小姐只是一部分 私信小涵可以看更多私藏小姐 歡迎找奈奈預約 👉 私信預約 📱 TG: @Japan8n 🫶🫶
❤1
認識我 從來都不用覺得晚 緣分到了 自然就會遇到了 之前跟別人約 有過不好的經營 這次跟奈奈配合完之後 覺得可以把之前叫過妹妹的店家都可以刪掉了 下次來日本肯定要再找我幫忙 安排 哈哈 謝謝你的認可 奈奈是不會讓你失望的 今天跟奈奈約了一位很正的女生 健談 溫柔 給人小家碧玉的感覺 重點是配合度很好喲 在東京 想要約的 或者有計劃來東京出差 旅遊 都可以提前找奈奈預約喲 👉 私信預約 📱 TG: @Japan8n 🫶🫶 👉 私信預約 ⭐Gleezy: Japan8n 💌 中文版出勤班表 💌日語版出勤班表 ✍️ 客評分享區 🇯🇵 日本动漫里番🔞 ⭐: 完整版出勤表 / 出勤表の完全版 🍀 #日本外約 #東京大阪上門服務 #東京泡泡浴 #大阪外送茶 #東京外約 #日本歌舞伎町 #日本旅遊 #大阪デリヘル #出張サービス #日本叫小姐 #大阪东京旅游
🔥笑死我了 😂 熟客回來找我安排，他在等小姐的過程中跟我聊： 「這妹是真的好，我很喜歡，如果她是我女朋友就好了😂 把她娶去香港！」 還說這次跟小姐做得很舒服，也很爽～👍 💖【熟客回約最真實的肯定】 這位香港客人已經找我安排過5次了～ 昨天又回約了一位他前幾天很喜歡的小姐： ✨ 顏值高、氣質佳 ✨ 身材超讚，大奶曲線超吸引 ✨ 個性好聊、互動自然 ✨ 在服務過程中非常配合，整體感覺就像有女友FU 客人玩得超開心，也非常滿意～ 每次有人願意再回來找我，就是對我最大的肯定❤️ 我會繼續幫大家安排最合適、最滿意的那一位✨ #香港客人 #回約分享 #奈奈安排 #日本出差 #高滿意度 #信任安排 #不踩雷保證
Showing the 5 most recent of 5 posts we hold for @nainai865. 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.
Named by 2 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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“🇯🇵お客様フィードバックエリア” (@nainai865), 20 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/nainai865.
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.