Channel
@tw7203
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Declared links · Cite this entry
485subscribers
-30 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003191739022 |
|---|---|
| Type | Channel |
| Username | @tw7203 |
| Created | Between 1 September 2025 and 30 November 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/tw7203 |
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 21 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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, 12:44 | 485 | -6 |
| 2 Oct 2026, 02:40 | 491 | -7 |
| 16 Sept 2026, 15:00 | 498 | +5 |
| 8 Sept 2026, 10:36 | 493 | -8 |
| 30 Aug 2026, 18:26 | 501 | -5 |
| 15 Aug 2026, 19:15 | 506 | -5 |
| 9 Aug 2026, 08:51 | 511 | -4 |
| 8 Aug 2026, 09:33 | 515 | first reading |
5 posts held, back to 12 May 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 5 posts for this entry, the most recent from 4 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 3 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
#新竹 客評 我就很簡單呀 喜歡坦誠相待 — 用心服務好每一個客人 — —客人的小事都是我的大事— — 你有空我就隨時在 — — 風裏雨裏 旅館等你 — 名字：果凍 妹妹年紀：約20 外表：五官立體（像某位明星） 身材：完全沒有贅肉（胸部B) 服務：妹妹外表身材真的沒話說胸部與鮑魚也是嫩嫩的完全是極品,妹妹LG舔鮑與口都非常的棒在做的時候也會輕微呻吟搭配外表真的一下子就繳械這次原本約2節但是妹妹有事只能一節,真的很傷心因為今天只有一節很多姿勢都沒法解鎖，這位妹妹一定要回約 非常有女友fu 🫣 ❤️❤️❤️❤️ 🫣 ❤️❤️❤️❤️🫣 ⭐粥粥のGleezy🆔：tw625 🌐粥粥の賴：av625 🌐粥粥のTelegram ：@tw625 或者 @av625 ⭐Gleezy每日班表 https://c.gleezy.top/tpb0VL2K ⭐Gleezy外流A片 https://c.gleezy.top/vaJh1…
❤️粥粥茶坊 7月底好康福利來囉 截止時間 7月25日-8月5日 內容是： 福利1 ：免房券（可以馬上使用） 福利2：免小費券（可以馬上使用） 福利3：消費滿 10000 再折 3000 好康不要錯過！ 福利4：6000試車券 （不管什麼類型都可以使用） 福利5：限時8折券 1 張（想什麼時候用都可以） 福利6：滿10000以上+2000 可以實現買1送1 剛興趣的哥哥可以來找粥粥使用喔！！ ✊✊ ⭐ 粥粥のGleezy🆔：tw625 🌐粥粥の賴：av625 🌐粥粥のTelegram ：@tw625 或者 @av625
Video, posted without a caption
Photo, posted without a caption
Video, posted without a caption
Showing the 5 most recent of 5 posts we hold for @tw7203. 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 1 registered channel — 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.
One URL this entry has put in its own public description, shown exactly as written there. A declaration, not a verified association — we measured that the description contained this text, and nothing more. It is not a claim that this entry owns, runs or is connected to whatever the link resolves to; a description is text anyone controls, and anyone can put anyone else’s URL into it. How this is measured.
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.
“推特Onlyfans反差福利姬” (@tw7203), 485 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/tw7203.
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.