Channel
@tw943
On this record: Topic · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
337subscribers
+13 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002632429478 |
|---|---|
| Type | Channel |
| Username | @tw943 |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/tw943 |
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 70% 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, 08:19 | 337 | +6 |
| 9 Sept 2026, 22:39 | 331 | -2 |
| 31 Aug 2026, 05:37 | 333 | -1 |
| 16 Aug 2026, 14:26 | 334 | +12 |
| 8 Aug 2026, 07:37 | 322 | -2 |
| 8 Aug 2026, 07:20 | 324 | no change |
| 7 Aug 2026, 18:33 | 324 | first reading |
11 posts held, back to 6 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 11 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
📍#困困優質中部外送茶 資訊：柔柔 - 157 - 44 - B - 19歲 💸茶價：18000 NT$ 【兩節34000】【三節48000】 #半價試車 #免車資免無套小費 #全台約妹立減6170 💻甜美可愛型 學生妹 很適合喜歡粉嫩小穴的麻吉哦！幹淨 青澀 瘦瘦的很好駕馭 很有女友fu~ ✈️Telegram: @tq771 ✈️VIP專屬Telegram:@kun0617 ⭐Gleezy: ty1111 🌐LINE: 667v 🌐VIP專屬LINE: 6h6s 😀新手上車指南 📺 全台正妹選妃區 📝 客評售後 🌟困困的心情樹洞 📱困困の論壇 🤩簽到福利群 😍色色頻
📍#困困優質中部外送茶 資訊：曼曼 - 162 - 44 - C - 29歲 💸茶價：3500 NT$ #半價試車 #免車資免無套小費 #全台約妹立減6170 💻這個妹妹困困私藏了一段時間 因為回約率實在是太高了！每天妹妹都排滿熟客回約 導致沒時間接新客人 現在過了一段時間 才能推出來給大家 而且她出來兼職一方面是因為性癮大 還有一方面 就是她老公有綠帽癖！！所以被調教的很好 完全的榨汁機騷貨 碰過以後就會念念不忘的床上功夫 賴667v老公平時還會幫她保養 按摩身體 小穴有客人說比20來歲的妹子還緊還濕潤 真的韻味十足 敢玩 所以建議想狠狠操逼的哥哥試試看 她絕對可以讓你欲罷不能 ✈️Telegram: @tq771 ✈️VIP專屬Telegram:@kun0617 ⭐Gleezy: ty1111 🌐LINE: 667v 🌐VIP專屬LINE: 6h6s 😀新手上車指南 …
📍#困困優質中部外送茶 資訊：小語 - 160 - 39 - C - 20歲 💸茶價：8000 NT$ #半價試車 #免車資免無套小費 #全台約妹立減6170 💻臉蛋清新甜美 青澀學生感 床上卻敢玩 主動坐上來扭腰 聲音奶甜讓人秒硬 喜歡給你足交 ✈️Telegram: @tq771 ✈️VIP專屬Telegram:@kun0617 ⭐Gleezy: ty1111 🌐LINE: 667v 🌐VIP專屬LINE: 6h6s 😀新手上車指南 📺 全台正妹選妃區 📝 客評售後 🌟困困的心情樹洞 📱困困の論壇 🤩簽到福利群 😍色色頻道
誰可以送我立秋的第一單
📍#困困優質中部外送茶 資訊：甜心 - 163 - 41 - C - 22歲 💸茶價：5000 NT$ #半價試車 #免車資免無套小費 #全台約妹立減6170 💻溫柔貼心 好聊 身材好 服務好 很騷的 欲望很強 配合度高 主動敢玩 ✈️Telegram: @tq771 ✈️VIP專屬Telegram:@kun0617 ⭐Gleezy: ty1111 🌐LINE: 667v 🌐VIP專屬LINE: 6h6s 😀新手上車指南 📺 全台正妹選妃區 📝 客評售後 🌟困困的心情樹洞 📱困困の論壇 🤩簽到福利群 😍色色頻道
📍#困困優質中部外送茶 資訊：周周 - 166 - 48 - D - 22歲 💸茶價：8000 NT$ #半價試車 #免車資免無套小費 #全台約妹立減6170 💻#高挑長腿 身材比例很勻稱 性慾很強 平時很忙 沒時間沒地方發泄 但是為了保持專業形象 一直在壓抑着欲火 此次報班只為跟哥哥一起淪陷在慾望の沼澤 ✈️Telegram: @tq771 ✈️VIP專屬Telegram:@kun0617 ⭐Gleezy: ty1111 🌐LINE: 667v 🌐VIP專屬LINE: 6h6s 😀新手上車指南 📺 全台正妹選妃區 📝 客評售後 🌟困困的心情樹洞 📱困困の論壇 🤩簽到
📍#困困優質中部外送茶 資訊：飛燕 - 170 - 50 - E - 21歲 💸茶價：15000 NT$ #半價試車 #免車資免無套小費 #全台約妹立減6170 💻高挑美長腿，完美模特身材，服務認真有禮貌，整場都微笑又帶點羞澀的表情，配合度高，淫蕩風騷浪妹妹，口技一流舔蛋超舒服！ ✈️Telegram: @tq771 ✈️VIP專屬Telegram:@kun0617 ⭐Gleezy: ty1111 🌐LINE: 667v 🌐VIP專屬LINE: 6h6s 😀新手上車指南 📺 全台正妹選妃區 📝 客評售後 🌟困困的心情樹洞 📱困困の論壇 🤩簽到福利群 😍色色頻道
Posted without readable text
📍#困困優質中部外送茶 資訊：婕兒 - 170 - 50 - C - 23歲 💸茶價：14000 NT$ #半價試車 #免車資免無套小費 #全台約妹立減6170 💻婕兒，就像是一個冰雪美人，有著冷豔高雅的氣質。她就像一位遙遠而高貴的女皇，讓人難以靠近，又令人著迷。婕兒就像一股冷冽的寒風，讓你的心瞬間冰凍，卻又渴望她的溫暖。當她展現熱情的一面，那份火熱能讓你完全燃燒，感受高冷與熱情相互碰撞的火花 ✈️Telegram: @tq771 ✈️VIP專屬Telegram:@kun0617 ⭐Gleezy: ty1111 🌐LINE: 667v 🌐VIP專屬LINE: 6h6s 😀新手上車指南 📺 全台正妹選妃區 📝 客評售後 🌟困困的心情樹洞 📱困困…
📍#困困優質中部外送茶 資訊：雪姬 - 158 - 38 - C - 19歲 💸茶價：8000 NT$ 【兩節14000】【三節18000】 #半價試車 #免車資免無套小費 #全台約妹立減6170 💻稚嫩小白兔，純真無邪，皮膚白皙如雪，身材嬌小緊致。眼神明亮，笑容甜美，初次體驗的羞澀感讓人倍感保護欲。雖然經驗不足，但熱情主動，渴望學習新鮮事物. ✈️Telegram: @tq771 ✈️VIP專屬Telegram:@kun0617 ⭐Gleezy: ty1111 🌐LINE: 667v 🌐VIP專屬LINE: 6h6s 😀新手上車指南 📺 全台正妹選妃區 📝 客評售後 🌟困困的心情樹洞 📱困困の論壇 …
📍#困困優質中部外送茶 資訊：靜香 - 163 - 46 - D - 27歲 💸茶價：3000 NT$ #半價試車 #免車資免無套小費 #全台約妹立減6170 💻內心狂熱 騷 淫蕩 輕熟女尺度很大 玩很大 特別寂寞的時候就會下海兼職 超級美胸可配合 服裝 絲襪床上很淫蕩 技術到位很會服侍 超奔放 超大膽的 ✈️Telegram: @tq771 ✈️VIP專屬Telegram:@kun0617 ⭐Gleezy: ty1111 🌐LINE: 667v 🌐VIP專屬LINE: 6h6s 😀新手上車指南 📺 全台正妹選妃區 📝 客評售後 🌟困困的心情樹洞 📱困困の論壇 🤩簽到
Showing the 11 most recent of 11 posts we hold for @tw943. 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 16 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.
@tw943 named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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.
“🏆渴渴茶坊【紅牌·系列】-line：tc689” (@tw943), 337 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/tw943.
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.