Telegram RegisterThe public register of Telegram
Telegram profile photo for 東京の風俗産業🇯🇵デリヘル

Channel

東京の風俗産業🇯🇵デリヘル

@ce6691

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

385subscribers

+9 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-1002396620935
TypeChannel
Username@ce6691
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live7 October 2026
Measurements held9
Confirmed unchanged1 time, most recently 7 October 2026
On Telegramt.me/ce6691

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 22 September 2026 and assigned it the closest of 31 fixed categories, at 65% 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

376387381.57 August 2026 — 376 subscribers8 August 2026 — 376 subscribers15 August 2026 — 377 subscribers23 August 2026 — 376 subscribers30 August 2026 — 386 subscribers7 September 2026 — 383 subscribers15 September 2026 — 387 subscribers27 September 2026 — 384 subscribers7 October 2026 — 385 subscribers3857 August 20267 October 2026
9 measurements spanning 61 days, net +9. 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 374–389 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Oct 2026, 14:57385+1
27 Sept 2026, 15:17384-3
15 Sept 2026, 00:19387+4
7 Sept 2026, 15:40383-3
30 Aug 2026, 00:35386+10
23 Aug 2026, 01:48376-1
15 Aug 2026, 05:26377+1
8 Aug 2026, 06:18376no change
7 Aug 2026, 15:35376first reading

Engagement

11 posts held, back to 23 September 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 11 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
2s
Average length
2s

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.

Reaction mix

54 reactions across 9 posts, in 8 distinct kinds. The most used accounts for 37.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤2037.0%
👍1222.2%
🔥713.0%
💯59.26%
🥰47.41%
👏35.56%
😍23.70%
🍌11.85%

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 10 of the 11 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 54 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 11 most recent posts we hold, published 23 September 2025 to 5 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.

Recent posts

5 Aug 2026, 02:52 UTC61 viewsread 8 August 2026

グループチャンネルは必ずしも更新されないので、必要があれば直接私にメッセージを送って女の子を手配できます

6 Jun 2026, 06:48 UTC≈1,080 views4 reactionsread 8 August 2026

下北澤古著店店長|まい(麻衣) 158cm 48kg A|27歲 中目黑咖啡廳甜點師|あんな(杏奈) 163cm 51kg C|26歲 池袋動漫周邊店店員|りこ(理子) 154cm 44kg B|23歲 惠比壽美容沙龍美容師|さき(沙紀) 160cm 50kg D|31歲 高圓寺超市收銀員|ゆき(由紀) 156cm 47kg A|29歲 🏠デートスポット:自宅、ホテルです。 🏠約會地點:自宅、飯店 📱Telegram :@s98267 🍀千雪:@w985ma 🇯🇵預約流程:@toyo218 ❤️評価区:@toyo219 🔔東京の:@ce6691 🎉大阪の:@ce6698 ⭐Gleezy:ce669 ⭐Gleezy:https://gleezy.net/ce669 ⭐東京🇯🇵デリヘル:https://g.gleezy.top/ce669 ⭐大版🇯🇵デリヘル:https://g.gleezy.top/ce6

❤3👍1

23 Jan 2026, 12:13 UTC≈2,120 views1 reactionsread 8 August 2026
Forwarded from @w985maPhoto

楽しい生活

❤1

19 Oct 2025, 06:12 UTC≈2,080 views6 reactionsread 8 August 2026
Photo

名前:すずき 身長:158cm バストサイズ:Dカップ 年齢:19歳 豊胸の有無:なし 出身地:東京🇯🇵 🏠デートスポット:自宅、ホテルです。 🏠約會地點:自宅、飯店 📱Telegram :@s98267 🍀千雪:@w985ma 🇯🇵預約流程:@toyo218 ❤️評価区:@toyo219 🔔東京の:@ce6691 🎉大阪の:@ce6698 🔞網站:www.s98267.com ⭐Gleezy:ce669 ⭐Gleezy:https://gleezy.net/ce669 ⭐東京🇯🇵デリヘル:https://g.gleezy.top/ce669 ⭐大版🇯🇵デリヘル:https://g.gleezy.top/ce6699

❤3👍2💯1

26 Sept 2025, 06:28 UTC≈1,600 views4 reactionsread 8 August 2026
Photo

名前:優衣 身長:155cm バストサイズ:Bカップ 年齢:20歳 體重:43kg 豊胸の有無:なし 出身地:東京🇯🇵 🏠デートスポット:自宅、ホテルです。 🏠約會地點:自宅、飯店 📱Telegram :@s98267 🍀千雪:@w985ma 🇯🇵預約流程:@toyo218 ❤️評価区:@toyo219 🔔東京の:@ce6691 🎉大阪の:@ce6698 🔞網站:www.s98267.com ⭐Gleezy:ce669 ⭐Gleezy:https://gleezy.net/ce669 ⭐東京🇯🇵デリヘル:https://g.gleezy.top/ce669 ⭐大版🇯🇵デリヘル:https://g.gleezy.top/ce6699

👍1👏1🔥1🥰1

25 Sept 2025, 03:01 UTC≈1,050 views8 reactionsread 8 August 2026
Photo

名前:ひかり 身長:162cm バストサイズ:Eカップ 年齢:23歳 體重:48kg 豊胸の有無:なし 出身地:東京🇯🇵 🏠デートスポット:自宅、ホテルです。 🏠約會地點:自宅、飯店 📱Telegram :@s98267 🍀千雪:@w985ma 🇯🇵預約流程:@toyo218 ❤️評価区:@toyo219 🔔東京の:@ce6691 🎉大阪の:@ce6698 🔞網站:www.s98267.com ⭐Gleezy:ce669 ⭐Gleezy:https://gleezy.net/ce669 ⭐東京🇯🇵デリヘル:https://g.gleezy.top/ce669 ⭐大版🇯🇵デリヘル:https://g.gleezy.top/ce6699

👍4👏2🔥2

24 Sept 2025, 04:48 UTC817 views8 reactionsread 8 August 2026
Photo

名前:リコ 身長:155cm バストサイズ:Cカップ 年齢:20歳 體重:44kg 豊胸の有無:なし 出身地:東京🇯🇵 🏠デートスポット:自宅、ホテルです。 🏠約會地點:自宅、飯店 📱Telegram :@s98267 🍀千雪:@w985ma 🇯🇵預約流程:@toyo218 ❤️評価区:@toyo219 🔔東京の:@ce6691 🎉大阪の:@ce6698 🔞網站:www.s98267.com ⭐Gleezy:ce669 ⭐Gleezy:https://gleezy.net/ce669 ⭐東京🇯🇵デリヘル:https://g.gleezy.top/ce669 ⭐大版🇯🇵デリヘル:https://g.gleezy.top/ce6699

🔥3👍2💯2🥰1

24 Sept 2025, 04:39 UTC917 views8 reactionsread 8 August 2026
Photo

名前:risa 身長:166cm バストサイズ:Fカップ 年齢:24歳 體重:48kg 豊胸の有無:なし 出身地:東京🇯🇵 🏠デートスポット:自宅、ホテルです。 🏠約會地點:自宅、飯店 📱Telegram :@s98267 🍀千雪:@w985ma 🇯🇵預約流程:@toyo218 ❤️評価区:@toyo219 🔔東京の:@ce6691 🎉大阪の:@ce6698 🔞網站:www.s98267.com ⭐Gleezy:ce669 ⭐Gleezy:https://gleezy.net/ce669 ⭐東京🇯🇵デリヘル:https://g.gleezy.top/ce669 ⭐大版🇯🇵デリヘル:https://g.gleezy.top/ce6699

❤2👍2💯2🍌1🔥1

23 Sept 2025, 06:04 UTC667 views9 reactionsread 8 August 2026
Forwarded from @w985maVideo

サンリオで買った小さなケープ!かわいいかわいい

❤5🥰2😍2

Showing the 11 most recent of 11 posts we hold for @ce6691. 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

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.

Mentions

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

“東京の風俗産業🇯🇵デリヘル” (@ce6691), 385 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/ce6691.

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.