Channel
@asdkl111
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
3,464subscribers
+7 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002044004570 |
|---|---|
| Type | Channel |
| Username | @asdkl111 |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 6 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 6 September 2026 |
| On Telegram | t.me/asdkl111 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Sept 2026, 09:55 | 3,464 | +12 |
| 2 Sept 2026, 09:13 | 3,452 | +22 |
| 30 Aug 2026, 16:09 | 3,430 | -8 |
| 27 Aug 2026, 14:53 | 3,438 | +4 |
| 24 Aug 2026, 08:44 | 3,434 | -2 |
| 21 Aug 2026, 01:13 | 3,436 | -3 |
| 18 Aug 2026, 07:03 | 3,439 | -3 |
| 14 Aug 2026, 23:25 | 3,442 | -2 |
| 11 Aug 2026, 18:05 | 3,444 | -14 |
| 8 Aug 2026, 12:43 | 3,458 | +1 |
| 7 Aug 2026, 21:33 | 3,457 | first reading |
7 posts held, back to 18 July 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 7 posts for this entry, the most recent from 6 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 1 of the 7 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 7 most recent posts we hold, published 18 July 2026 to 6 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.
#北部鄰家妹妹來咯~ #北部客評 #北部可約 野兔 162cm-45kg-小D-46kg 乖巧可愛的鄰家妹妹感，粉嫩白皙的肌膚，五官精緻甜美，胸前飽滿渾圓，身材小巧卻曲線玲瓏，讓人一眼就想呵護。互動自然帶點害羞感，越相處越上癮 ➖➖➖➖➖➖➖➖➖➖➖➖➖ 服務過程：妹妹一進門就笑臉迎人，而且很客氣，我就留下了，一直在跟我說謝謝，我也不知道她 到底謝我啥XD說完就整個抱過來，開始幫我脫，然後就....正式開始！有一點是我很滿意的部分，雖然其他部分也很好，因為我自己是不敏感類型，還沒有成功在做過程中出過水，都是最後靠打出來的，但很多妹妹三個動作之後就會說幫你打出來吧，或偷時間或臉臭不想做等等，但是今天這個完全不會，積極配合各種動作，盡量能幫我出水，我都不好意思了說沒關係，用打的就好，她還是說沒關係她不累，這點讓我非常非常非常滿意，目前沒有遇過這麼長得正又這麼敬業的妹妹，通常二者只能擇一，所以大推服務態度，而且全程笑臉 對芸…
#北部巨乳妹妹預約上囖~ #北部可約 卡卡 156 G 48KG 26歲 點擊我查看卡卡客評1️⃣ 點擊我查看卡卡客評2️⃣ 小隻馬短髮氣質類型的巨乳妹妹！！ 服務超好很耐心 口技好 大奶不肉 奶子又大又軟 很容易濕濕 超好插入 真奶！ 服務過程： 一開門，看見的是長相溫柔、笑容親切又帶著端莊氣質的女生，瞬間融化了我的心。妹妹並不急著開始，而是先分享過來的路上發生的趣事，也間接化解了初次見面的尷尬，之後才領著我去沖洗。抹上沐浴乳後，便用她那豐滿圓潤的雙峰搓洗我的身體，還順便打了一下奶砲。到床上妹妹主動的親吻，慢慢的下滑然後就開始幫我口，過程中時不時用眼神對望，半途還拿出小道具塗抹在龜頭上產生出不一樣的刺激感。妹妹的下體修得非常乾淨，露出美麗的一線鮑，讓人忍不住想趕快插入。她的小穴非常溫暖緊實的包覆著肉棒，深怕一不小心就射出來，抽插的過程中，伴隨著妹妹的呻吟聲，又讓人更加興奮了，做到高潮的時候，能強烈的感受到她小…
【芸熙家北中南有服務的區域大合集】 台北： 北投、士林、內湖、南港、信義 文山、大安、中正、萬華、松山 中山、大同 新北： 中和、永和、新店、板橋、土城 三重、蘆洲、新莊、五股、泰山 汐止 其他： 林口、龜山、淡水、八里 台中： 大雅、西屯、北屯、南屯、大里 烏日、東區、西區、南區、北區 中區、豐原、沙鹿 高雄： 左營、鼓山、新興、前金、三民 苓雅、前鎮、小港、鳳山、楠梓 台南： 東區、北區、南區、中西區 永康、仁德 新竹 市區、東區、北區、竹北、香山
#北部正妹客評來咯~ #北部可約 #北部正妹 亦希 158 C 25歲 46kg 有些時候出來約妹妹真的不要追求完美 沒有任何人可以做到十全十美， 往往有一好就難有二好。 大家在約妹妹的時候可以跟芸熙說最看重幾點 芸熙會優先依照你的核心需求幫你篩選。 對妹妹的評價： 有喔 這個妹妹服務蠻優的 很有女友感 服務過程：一進門就看到一雙會笑的眼睛 用好聽且可愛的聲音跟我打招呼 然後牽著我走進浴室幫我洗澡 動作輕巧溫柔 洗完讓我先去床上等 之後就開始幫我口愛 一邊口還會一邊看著你 很魅惑 服務過程很享受 結束後一樣牽著你去洗澡 全部結束後離開前還會跟你抱抱 女友感滿分 對芸熙的評價：芸熙推薦 不會踩雷
#北部紅牌妹妹來囖~ #北部可約 #北部客評 絲絲 164 E 28 47kg 氣質與誘惑並存—為你專屬服務的女神，長腿筆直 淡妝清透卻難掩高顏值，制服包裹下的身材線條俐落流暢，腰身收得漂亮，臀腿比例出色 因為信任所以麻吉每一次約的妹妹都玩的很開心 正是為了不辜負這份信任，在篩選妹妹的時候芸熙更加上心 每一次從確認到安排都很乾脆 信任交給芸熙 剩下的自然做到位 信任 是一次次穩定安排累積出的答案 客評： 這位活潑 氣質也很好比較開放 今天的妹妹第一眼看到非常讓我驚艷～ 妹妹很有氣質而且有種優雅的感覺，很吸引人！那個氣質不是刻意裝出來的，而是自然由內散發出來的～ 今天愛愛的時候當然是非常享受的時光，親吻也是非常享受的火辣辣的熱情舌吻💋，會讓人捨不得離開那柔軟的嘴唇，然後進行愛愛更是非常享受的 她的叫聲 也是讓我會一直想念的⋯⋯超級酥酥痲痲的 好聽～
#高雄正妹推薦 #南部客評 #高雄可約 予安 166 D 25歲 46kg 可御可甜的反差氣質妹妹，床上服務淫蕩很會扭動也很會挑逗哥哥，還會主動把手伸入哥哥的褲襠里撫摸哥哥的DD，主動的幫你脫掉一件件遮擋物，口交技術超讚，粉嫩的小嘴含住你的DD一進一出，舌尖挑逗你的小頭好爽~ 對妹妹的評價：不錯呀，妹很高，166，臉是可愛的，胸部D是真奶，很會聊天，個性開朗，有大學生的開朗。 客評：服務很好喔，少數洗完澡，會幫忙擦乾身體的。床上服務也很好，輕輕柔柔的。吹完戴套就自己坐上來，不用潤滑液，厲害。第一次結束，沖澡，泡澡，中間一直在聊天。今天的妹蠻放的開的，第一次遇到，出來後拔套，還沒洗就幫我吹
❤1
#高雄妹妹客評來咯~ #高雄推薦 #高雄可約 沐妍 163 48 C 28 安喜163 41 小E 25 一天做兩個風格完全不一樣的妹妹。也是只有在芸熙家次才能這樣每一個都不踩雷啦~哈哈哈哈 這就是無照妹妹的魅力叭~ 服務過程：原本我的時間喬不攏 跟芸熙說不用勉強，後來芸熙搞出新的想法 為了配合我的時間，分別請兩個妹妹來服務我 當然不是雙飛，是各別分開服務 第一個妹妹【沐妍 163 48 C 28】 很健談，一邊跟我聊一邊脫衣服 一起去洗澡時，幫我抹完沐浴乳後，妹妹背對著我 讓我用已經硬梆梆的弟弟磨蹭她的屁屁 我的雙手也沒停下，不斷的摸著她的雙乳 洗完後到床上，兩人先聊聊後，妹妹說看我的弟弟很硬 她忍不住想吃（很會），就吃了，妹妹說她喜歡我的反應 我說我更喜歡她的反應，吃完後，戴上套就衝了 妹妹說她興奮時會說些淫語，希望我不要介意，我說我很愛聽 抽插過程中，…
Showing the 7 most recent of 7 posts we hold for @asdkl111. 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 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 6 September 2026 — this entry's latest reading, not the date you are reading this.
“芸熙の客評” (@asdkl111), 3,464 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/asdkl111.
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.