#五週年慶典! 就說嘛 #搏一搏單車變摩托 成功骰出 #特殊服務任選卡5張! 活動還在進行中喔! 週年慶&博餅正在進行中 t.me/JP796/8750

Channel
🇯🇵「大阪」不夜谷高級外約俱樂部👑
@xw5836
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
1,836subscribers
+96 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002381171271 |
|---|---|
| Type | Channel |
| Username | @xw5836 |
| 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 | 30 September 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 30 September 2026 |
| On Telegram | t.me/xw5836 |
Topic
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 16 September 2026 and assigned it the closest of 31 fixed categories, at 41% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Sept 2026, 07:22 | 1,836 | +19 |
| 19 Sept 2026, 17:36 | 1,817 | +12 |
| 15 Sept 2026, 06:19 | 1,805 | +1 |
| 11 Sept 2026, 06:41 | 1,804 | +9 |
| 6 Sept 2026, 10:00 | 1,795 | +7 |
| 1 Sept 2026, 22:25 | 1,788 | -3 |
| 30 Aug 2026, 04:03 | 1,791 | +12 |
| 27 Aug 2026, 07:04 | 1,779 | -2 |
| 24 Aug 2026, 15:04 | 1,781 | +7 |
| 21 Aug 2026, 05:52 | 1,774 | +4 |
| 18 Aug 2026, 08:12 | 1,770 | +6 |
| 14 Aug 2026, 21:23 | 1,764 | +7 |
| 11 Aug 2026, 09:02 | 1,757 | +14 |
| 7 Aug 2026, 23:55 | 1,743 | +3 |
| 7 Aug 2026, 17:33 | 1,740 | no change |
| 7 Aug 2026, 17:09 | 1,740 | first reading |
Engagement
13 posts held, back to 3 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 6 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
#老朋友+1 #預約+1 哇塞,誰懂 #你辦事我放心 這句話的含金量呀~ 大大說 #一決定去東京就找你了哈哈哈 我永遠相信 #真誠才是必殺技 Angel不做一錘子買賣只做細水長流😋
#新朋友+1 #預約+1 這位哥哥年初加入Angel的時候,就跟我說了一句 #8月來找妳 8月一到他踩着七彩祥雲就來了(此處應有掌聲👏) 我宣布📢2026年度最有魅力的男人,就是言出必行的男人 ❤️
⭐⭐⭐⭐⭐⭐🌟🌟🌟 「品質茶💎皮膚管理師」 🧸優香 163.C.28.45kg 🧸皮膚白皙,身材均勻無贅肉真胸C粉軟!小腹平坦屁股緊實好撞,皮膚光滑 態度好懂男人的女生,自帶女友感 ➡️🗼東京專區 ➡️🏯大阪專區 📩Angel⭐ JP8689 📩Angel🌐 t.me/dy947 📩Angel🌐 t.me/AV3878 📩官 網🌐 www.JP838.com ୨୧始於相遇✨終於素質୨୧
⭐⭐⭐⭐⭐⭐🌟🌟🌟 「品質茶💎美少女學姐」 🧸理沙 161.C.22.46kg 🧸酷颯風格的穿搭讓感受到是一股比較強的氣場 她是班級上的班長 所以氣質非凡 酷酷風格的她有略帶地雷系即視感 不過人嘛都會有青春期 當然酷學姐也有啦 逃不過青春期的帶來的一些濛動 讓她對性愛有一種新的嚮往😂 ➡️🗼東京專區 ➡️🏯大阪專區 📩Angel⭐ JP8689 📩Angel🌐 t.me/dy947 📩Angel🌐 t.me/AV3878 📩官 網🌐 www.JP838.com ୨୧始於相遇✨終於素質୨୧
⭐⭐⭐⭐🌟🌟🌟🌟🌟 「優質茶💎藝術院校校花」 🧸艾琳娜 168.C.20.47kg 🧸身高167公分 C罩杯 完美的身材曲綫是吸精的武器 溫柔清秀并存 貼心小舉動精確的刺激你的敏感地帶 甜美臉加甜美音 溫柔似水的性格 把溫柔鄉三個字體現的淋漓盡致 ➡️🗼東京專區 ➡️🏯大阪專區 📩Angel⭐ JP8689 📩Angel🌐 t.me/dy947 📩Angel🌐 t.me/AV3878 📩官 網🌐 www.JP838.com ୨୧始於相遇✨終於素質୨୧
我一直都在
Sticker, posted without a caption
哈哈哈哈
我來啦
我早來啦
別以為我不在
Showing the 12 most recent of 13 posts we hold for @xw5836. 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 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.
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 30 September 2026 — this entry's latest reading, not the date you are reading this.
“🇯🇵「大阪」不夜谷高級外約俱樂部👑” (@xw5836), 1,836 subscribers as measured 30 September 2026. Telegram Register, tgregister.com/channel/xw5836.
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.