Channel
@sk66226
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
1,457subscribers
+171 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002592071512 |
|---|---|
| Type | Channel |
| Username | @sk66226 |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/sk66226 |
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 82% 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 |
|---|---|---|
| 12 Oct 2026, 09:37 | 1,457 | +10 |
| 5 Oct 2026, 22:19 | 1,447 | +46 |
| 28 Sept 2026, 12:18 | 1,401 | +51 |
| 18 Sept 2026, 22:38 | 1,350 | +22 |
| 14 Sept 2026, 23:20 | 1,328 | +14 |
| 11 Sept 2026, 04:00 | 1,314 | -7 |
| 6 Sept 2026, 06:21 | 1,321 | -3 |
| 2 Sept 2026, 06:03 | 1,324 | +10 |
| 30 Aug 2026, 04:47 | 1,314 | -2 |
| 27 Aug 2026, 09:34 | 1,316 | +3 |
| 24 Aug 2026, 02:53 | 1,313 | +5 |
| 20 Aug 2026, 02:42 | 1,308 | -2 |
| 17 Aug 2026, 10:05 | 1,310 | +9 |
| 13 Aug 2026, 17:37 | 1,301 | +10 |
| 10 Aug 2026, 23:02 | 1,291 | +3 |
| 7 Aug 2026, 23:05 | 1,288 | +2 |
| 7 Aug 2026, 00:16 | 1,286 | first reading |
8 posts held, back to 29 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 8 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
🎓 暑期熱門大學生來了！ 這批學生妹人氣真的很高， 每天都有客人提前預約。 現在預約可以優先安排今天可約名單。 有喜歡的類型直接私訊即可。 每位皆由布丁本人親自面試、素質嚴格把關，協助你快速找到適合的對象。 🤍外約安排 🤍 週一～週四 $8000 🤍 週五～週日 $10000 LINE：wk228 Telegram：@sk662 | @sk6628 gleezy：sk662 | yyds662
歡馨 160.F.48.21歲 #新竹 可愛笑顏，勻稱飽滿，性感可愛的學生嫩妹！純粹的性愛饗宴，奶炮沐浴、一流舌功、敏感緊緻的一線美鮑，玩過可是會流連忘返的喔！ 🫧 聯絡小布丁 • Telegram：@sk662 | @sk6628 • Line：wk228 • 大G：sk662 😘 快速導覽選單 • 🫧 選妹論壇 • 🫧 心得分享 • 🫧 新手必看 🫧 服務地區：北部｜中部｜南部｜新竹 😘 營業時間：13:00 - 04:00 🫧 點此一鍵訂閱全部頻道 #林森北外送茶 #中山區外送茶 #搶頭香 板橋區外送茶 #中山區喝茶 #台灣外流 #台北外約 #台北找小姐 #台北學生兼職 #桃園外送茶
丁丁 165cm.54kg.Ecup.24歲 #新竹 長腿大奶 微肉女神， 給你極致快感。讓你心醉神迷 讓人無法自拔 🫧 聯絡小布丁 • Telegram：@sk662 | @sk6628 • Line：wk228 • 大G：sk662 😘 快速導覽選單 • 🫧 選妹論壇 • 🫧 心得分享 • 🫧 新手必看 🫧 服務地區：北部｜中部｜南部｜新竹 😘 營業時間：13:00 - 04:00 🫧 點此一鍵訂閱全部頻道 #林森北外送茶 #中山區外送茶 #搶頭香 板橋區外送茶 #中山區喝茶 #台灣外流 #台北外約 #台北找小姐 #台北學生兼職 #桃園外送茶
不常報班的一位小姐 #新竹 芷涵 162cm- D+奶-47kg 23歲 甜美笑容＋白皙嫩肌 床上超誘人 🫧 聯絡小布丁 • Telegram：@sk662 | @sk6628 • Line：wk228 • 大G：sk662 😘 快速導覽選單 • 🫧 選妹論壇 • 🫧 心得分享 • 🫧 新手必看 🫧 服務地區：北部｜中部｜南部｜新竹 😘 營業時間：13:00 - 04:00 🫧 點此一鍵訂閱全部頻道 #林森北外送茶 #中山區外送茶 #搶頭香 板橋區外送茶 #中山區喝茶 #台灣外流 #台北外約 #台北找小姐 #台北學生兼職 #桃園外送茶
紫萱 158cm 48kg E杯 20歲 #新竹 聲音蘇到骨子裡的軟萌學生妹 小隻馬身材，E奶形狀超完美，抱起來超有保護欲 。小穴緊緻水多，敏感度極高 🫧 聯絡小布丁 • Telegram：@sk662 | @sk6628 • Line：wk228 • 大G：sk662 😘 快速導覽選單 • 🫧 選妹論壇 • 🫧 心得分享 • 🫧 新手必看 🫧 服務地區：北部｜中部｜南部｜新竹 😘 營業時間：13:00 - 04:00 🫧 點此一鍵訂閱全部頻道 #林森北外送茶 #中山區外送茶 #搶頭香 板橋區外送茶 #中山區喝茶 #台灣外流 #台北外約 #台北找小姐 #台北學生兼職 #桃園外送茶
七月完美收官！謝謝各位老闆們這一個月的捧場與照顧捏，愛你們～八月繼續安排起來！✨
第一次約外送就直接下兩節！整體體驗超棒～ 互動起來像朋友一樣輕鬆，哥哥非常貼心，超照顧妹妹！謝謝信任唷～ 又是被老司機推坑跑來找布丁的可愛新朋友，絕對讓你不踩雷！ @sk662 #台中外送茶
少喝一杯手搖飲不會瘦， 但多點一杯好茶保證解百愁！ 白天給老闆當孫子， 晚上總得當個爺吧？ 月底倒數，急需一位英勇的【乾爹】降臨救火！ @sk662
Showing the 8 most recent of 8 posts we hold for @sk66226. 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.
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 12 October 2026 — this entry's latest reading, not the date you are reading this.
“新竹外送茶・台灣外送茶” (@sk66226), 1,457 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/sk66226.
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.