Channel
@Esseymiyaki1
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
1,756subscribers
-191 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002358173079 |
|---|---|
| Type | Channel |
| Username | @Esseymiyaki1 |
| 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 | 18 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/Esseymiyaki1 |
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 79% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 22:35 | 1,756 | -60 |
| 14 Sept 2026, 23:19 | 1,816 | -4 |
| 11 Sept 2026, 05:15 | 1,820 | -21 |
| 6 Sept 2026, 04:40 | 1,841 | -9 |
| 1 Sept 2026, 18:24 | 1,850 | -15 |
| 29 Aug 2026, 08:27 | 1,865 | -14 |
| 26 Aug 2026, 05:18 | 1,879 | -11 |
| 23 Aug 2026, 05:35 | 1,890 | -6 |
| 19 Aug 2026, 19:16 | 1,896 | -12 |
| 16 Aug 2026, 19:46 | 1,908 | -7 |
| 13 Aug 2026, 15:08 | 1,915 | -17 |
| 10 Aug 2026, 15:23 | 1,932 | -20 |
| 7 Aug 2026, 20:01 | 1,952 | +5 |
| 7 Aug 2026, 15:02 | 1,947 | no change |
| 7 Aug 2026, 13:07 | 1,947 | first reading |
6 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 6 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
📢☹️😘 📢☹️😘 艺名：Dior 年龄：23岁 国际：Korean 身材：36c 24 34 身高：165cm 体重：47kg 🫥服务内容 😀无套口交😀鸳鸯浴 😀口交😀性爱😀ktv 😑堂食费用 👨💼Rm460 45min 1shot 👨💼Rm920 90min 2shot 💖包夜优惠（incall） 👨💼Rm2400 = 10pm-8am [10 hour] 💖包夜优惠（incall） 👨💼Rm1920 = 12pm-8am [8hour] 📱📱 📱Incall堂食 📱Outcall外卖 📱Overnight过夜 ♐️☸️💘💙☣️ @Nicky7788882 📱☸️💘💙☣️ https://wa.me/+601162340892
预约制 · 私密体验 ❤️回扣🅰️🅰️2️⃣0️⃣ 📷照片点击 1️⃣[KL Bangsar酒店】地区 📷 https://t.me/Esseymiyaki1 😀【照常营业】 2️⃣[Subang Usj酒店】地区 📷 https://t.me/Esseymiyaki 😀【 照常营业】 3️⃣[Damansara Pju酒店】地区 📷 https://t.me/Esseymiyaki2 😀【照常营业】 4️⃣[Petaling Jaya酒店】地区 📷https://t.me/Esseymiyaki5 😀【照常营业】 😀如果要外籍可以pm 😀Incall包夜不需要订金 😀Outcall 必需要订金 😀支付宝转账 😀Usdt 😀Tng 一即通 😀银行转账 😀现金交易 😀照镜是随机看那个小姐得空 😀满意才进去给钱小姐 😀高级酒店 😀如果不适合可以选择不要进去。 公司不会强逼顾客一定要选择一个。公平交易。 ❤️点击链接 …
姓名 : Yuna 年龄 : 24 身材 : 34D 24 34 身高 : 165cm 种族 : 韩国 Korea 费用 : RM460 45min 费用 : RM920 90min 优惠 : RM1800 12am-8am 🏠 通道 : kl #Korea #韩国
📱☹️😘 📱📱Miko 📱📱23岁 📱📱日本 📱📱34D 24 33 📱📱165cm 📱📱48kg 📝服务内容 ✅鸳鸯浴✅无套口交 ✅性爱 ✅69式 😀堂食费用📱📱 🥰460 1s 45min 🥰920 2s 90min ➡️新车到 ✅Incall堂食 ✅Outcall外卖 ✅过夜 📱📱 @nicky7788882 📱📱📱 📱： https://wa.me/+601162340892
💎名字：小玖 💎年龄：24 💎国籍： 中国 💎身高：165cm 💎胸围：36c 24 34 真奶 服务内容： 无套口交✅帮顾客冲凉✅ 胸推✅ 69式✅舔阴部✅ 按摩✅ 🫥堂食费用 🪙Rm480 1s 45min （扣了20） 🪙Rm960 2s 90min （扣了40） Outcall 外卖 可以 Overnight 过夜 可以 KTV ok 📱📱 📱Incall堂食 📱Outcall外卖 📱Overnight包夜 ♐️☸️💘💙☣️ @nicky7788882 📱☸️💘💙☣️ https://wa.me/+601162340892
📱☹️😘 📱📱七月 📱📱25岁 📱📱中国 📱📱36b 24 35 📱📱171cm 📱📱45kg ❤️包好服务 ➡️服务内容 😀69😀无套口交😀鸳鸯浴 😀接吻😀按摩😀口爆 😀独龙 😀舔蛋😀品鲍😀一条龙 😀服务一流 ❤️堂食费用 🥰480 45min 1shot （扣了20） 😦960 90min 2shot （扣了40） ❤️Incall堂食 ❤️Outcall外卖 ❤️过夜 📱📱 @nicky7788882 📱📱📱 📱： https://wa.me/+601162340892
Showing the 6 most recent of 6 posts we hold for @Esseymiyaki1. 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.
Named by 5 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“倚丝玫雅[Kl Bangsar店】” (@Esseymiyaki1), 1,756 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/Esseymiyaki1.
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.