Channel
@kui626
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
775subscribers
+76 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003949314638 |
|---|---|
| Type | Channel |
| Username | @kui626 |
| Created | Between 1 April 2026 and 8 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 26 September 2026 |
| On Telegram | t.me/kui626 |
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 20 September 2026 and assigned it the closest of 31 fixed categories, at 80% 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 |
|---|---|---|
| 26 Sept 2026, 10:42 | 775 | +32 |
| 13 Sept 2026, 04:21 | 743 | +9 |
| 4 Sept 2026, 13:17 | 734 | +9 |
| 27 Aug 2026, 11:44 | 725 | +6 |
| 21 Aug 2026, 09:57 | 719 | +7 |
| 14 Aug 2026, 12:04 | 712 | +11 |
| 7 Aug 2026, 22:13 | 701 | +2 |
| 7 Aug 2026, 09:18 | 699 | first reading |
7 posts held, back to 8 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.
補發客評 💖 大寶又來捧場啦～ 一有空就來支持小葵，真的超甘溫感謝 • 年紀： 2X • 身高： 忘了… • 體重： 體態剛剛好，不胖不瘦 • 胸部：尺寸不知道，小而挺 • 態度：年輕的妹妹，感覺得出來她會努力找話題聊，值得肯定 • 有無刺青： 腳上好像有小刺青（？） •過程分享：妹妹新來的，感覺還很青澀，但服務不馬虎。口技一般般，不會含很深，但手上功夫確實挺不錯的。會主動女上位。休息過程中會靠著你握著你的手，陪你聊聊天。 • 是否回約：有機會可以 • 對小葵的評價：我葵子寶貝，100分，不，200分！ • 整體給幾分：妹妹我給90分～ 🤍🤍🤍🦋聯絡小葵🦋🤍🤍🤍 🌐 @diy62 🌐 buff51 ⭐ buff51 ⭐班表：https://c.gleezy.top/maldySAn 🤩 點擊一鍵加入小葵所有茶單頻道 🤩
簽收老朋友啦 感謝捧場！ #好評➕1 #回約➕1 #信任➕1 🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍 • 年紀：20歲左右 • 身高： 158那邊 • 體重：沒問是瘦的 • 胸部：大C小D • 態度：一開始冷淡 不難相處 • 有無刺青： 無 •過程分享：過程很好 配合度很高 有情緒價值 口技也真的很好 • 是否回約：是 • 對小葵的評價：10分 • 整體給幾分：9分 🤍🤍🤍🦋聯絡小葵🦋🤍🤍🤍 🌐 @diy62 🌐 buff51 ⭐ buff51 ⭐班表：https://c.gleezy.top/maldySAn 🤩 點擊一鍵加入小葵所有茶單頻道 🤩
🖤 #北部 #好評口碑推薦 喜歡小隻大奶 女友fu~的可約 #好評➕1 #回約➕1 #信任➕1 🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍 • 年紀： 2X • 身高： 15X • 體重：秘密(整體看上去體態剛好，不會太瘦) • 胸部：E • 態度：女友感十足 • 有無刺青： 無 •過程分享：見面就是一個漂亮妹子，衣服阻擋不了他的好身材，簡單的洗洗後，就開始正戲。妹妹的手很巧，再加上小隻的身材，讓人欲罷不能。尤其是從後面來的時候，那個屁股蛋，太好撞了❤️ • 是否回約：會回約 • 對小葵的評價：葵子是我的小寶貝，感謝他推薦好妹妹 • 整體給幾分：妹妹90分，葵子我給100 🤍🤍🤍🦋聯絡小葵🦋🤍🤍🤍 🌐 @diy62 🌐 buff51 ⭐ buff51 ⭐班表：https://c.gleezy.top/maldySAn 🤩 點擊一鍵加入小葵所有茶單頻道 🤩
✈️ 回國第一件事，就是先來找小葵 超感謝哥哥一落地就來捧場！ 這次安排的妹妹年輕 外貿優 互動自然，服務也很細心 能讓哥哥一回國就想到小葵，真的很開心🩵 🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍 🌐 @diy62 🌐 buff51 ⭐ buff51 🤩 點擊一鍵加入小葵所有茶單頻道 🤩
🩵 簽收今日新朋友好評 +1 第一次安排就很順利☺️ 小隻、年輕，整體表現都很不錯， 哥哥也直接給妹妹和小葵 100 分💯 謝謝第一次就選擇相信小葵， 有需要再來找小葵就對啦 ☑️ 🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍 🌐 @diy62 🌐 buff51 ⭐ buff51 🤩 點擊一鍵加入小葵所有茶單頻道 🤩
🖤 #北部 #好評口碑推薦 喜歡年輕小奶纖瘦 女友fu~的可約 • 年紀：20-21 • 身高： 162左右 • 體重：看起來44-45 • 胸部：B • 態度：很客氣，聊一下比較熟之後很好聊 • 有無刺青： 有 •過程分享：很放鬆 妹妹很nice配合度也很好 • 是否回約：是 • 對小葵的評價：讚 • 整體給幾分：9分 🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍 🌐 @diy62 🌐 buff51 ⭐ buff51 🤩 點擊一鍵加入小葵所有茶單頻道 🤩
🖤 #南部 #好評口碑推薦 簽收老朋友好評 +1 選擇很多 謝謝哥哥每一次都願意找小葵。 每一份信任，我都會用心安排 ❤️ #好評➕1 #回約➕1 #信任➕1 🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍 • 年紀：目測19-24 • 身高：150 • 體重：47 • 胸部：D • 態度：講話溫柔 • 有無刺青：有（小臂 背後閣一小塊） •過程分享：妹妹洗殘廢澡洗的非常溫柔，口技略為生澀，但過程中一直撫摸妹妹身體，皮膚白嫩緊緻非常好摸。胸部大又挺卻完全不下垂，下面很緊，口交時完全無異味還香香的，抽插的過程中一直玩弄妹妹的大胸部真的很爽。 • 是否回約：是 • 對小葵的評價：8.5分 • 整體給幾分：8.5分 🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍 🌐 @diy62 🌐 buff51 ⭐ buff51 🤩 點擊一鍵加入小葵所有茶單頻道 🤩
Showing the 7 most recent of 7 posts we hold for @kui626. 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 7 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.
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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“小葵茶坊ღ 客評專區🩵” (@kui626), 775 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/kui626.
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.