Telegram RegisterThe public register of Telegram
Telegram profile photo for 台中彰化外送茶LINE:tea232

Channel

台中彰化外送茶LINE:tea232

@taimei52

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

542subscribers

+26 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002136570369
TypeChannel
Username@taimei52
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live10 October 2026
Measurements held10
Confirmed unchanged1 time, most recently 10 October 2026
On Telegramt.me/taimei52

Topic

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 77% 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.

Growth

5165425297 August 2026 — 516 subscribers8 August 2026 — 516 subscribers8 August 2026 — 517 subscribers14 August 2026 — 518 subscribers22 August 2026 — 523 subscribers30 August 2026 — 521 subscribers8 September 2026 — 535 subscribers15 September 2026 — 540 subscribers30 September 2026 — 541 subscribers10 October 2026 — 542 subscribers7 August 202610 October 2026
10 measurements spanning 64 days, net +26. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 512–546 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Oct 2026, 20:38542+1
30 Sept 2026, 13:39541+1
15 Sept 2026, 09:55540+5
8 Sept 2026, 17:54535+14
30 Aug 2026, 10:04521-2
22 Aug 2026, 11:44523+5
14 Aug 2026, 21:46518+1
8 Aug 2026, 10:02517+1
8 Aug 2026, 04:04516no change
7 Aug 2026, 23:45516first reading

Engagement

9 posts held, back to 3 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 9 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1100.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 9 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 9 most recent posts we hold, published 3 August 2026 to 7 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.

Recent posts

7 Aug 2026, 16:23 UTC29 viewsread 8 August 2026
Photo

TG:@sun6633 TG:@sun568 輕鬆暢聊直接點擊線上聊天 https://gleezy.net/ewvpxw 蜜雪兒 165 47 D 27歲 淫蕩狂野性感火辣 放蕩不羈 很浪很騷很敢玩 只有哥哥想不到 沒有妹妹做不到呦~ LINE:sun5637 https://line.me/ti/p/wCRqXBBPsE WeChat:yee5669 雙北新竹名單:https://t.me/tea698 台中彰化茶單:https://t.me/taimei52 南部每日好茶:https://t.me/gaox520 高檔茶推薦: https://t.me/sun56877 正妹分享私密約炮: https://t.me/tws668 佳人外送茶|迅速又安全 www.teas0204.com

7 Aug 2026, 09:17 UTC38 viewsread 8 August 2026
Photo

TG:@sun6633 TG:@sun568 輕鬆暢聊直接點擊線上聊天 https://gleezy.net/ewvpxw 漂亮主動的學妹來啦 琳琳 162.45.C+.20歲 在校學生妹 皮膚細嫩 很有女友fu 喜歡玩速度與激情按摩 口交 殘廢澡 無抽菸無刺青 LINE:sun5637 https://line.me/ti/p/wCRqXBBPsE WeChat:yee5669 雙北新竹名單:https://t.me/tea698 台中彰化茶單:https://t.me/taimei52 南部每日好茶:https://t.me/gaox520 高檔茶推薦: https://t.me/sun56877 正妹分享私密約炮: https://t.me/tws668 佳人外送茶|迅速又安全 www.teas0204.com

7 Aug 2026, 09:15 UTC35 viewsread 8 August 2026
Photo

TG:@sun6633 TG:@sun568 輕鬆暢聊直接點擊線上聊天 https://gleezy.net/ewvpxw 渝渝 163 48 kg Dcup 30 歲 性感氣質 小騷貨大奶 薇肉皮膚白皙 性感大水蜜桃臀 淫蕩風騷小蕩婦性慾強 技術好 比例非常好 LINE:sun5637 https://line.me/ti/p/wCRqXBBPsE WeChat:yee5669 雙北新竹名單:https://t.me/tea698 台中彰化茶單:https://t.me/taimei52 南部每日好茶:https://t.me/gaox520 高檔茶推薦: https://t.me/sun56877 正妹分享私密約炮: https://t.me/tws668 佳人外送茶|迅速又安全 www.teas0204.com

7 Aug 2026, 09:11 UTC34 viewsread 8 August 2026
Photo

TG:@sun6633 TG:@sun568 輕鬆暢聊直接點擊線上聊天 https://gleezy.net/ewvpxw #台中 今日高檔妹妹 LINE:sun5637 https://line.me/ti/p/wCRqXBBPsE WeChat:yee5669 雙北新竹名單:https://t.me/tea698 台中彰化茶單:https://t.me/taimei52 南部每日好茶:https://t.me/gaox520 高檔茶推薦: https://t.me/sun56877 正妹分享私密約炮: https://t.me/tws668 佳人外送茶|迅速又安全 www.teas0204.com

6 Aug 2026, 18:18 UTC49 viewsread 8 August 2026
Photo

TG:@sun6633 TG:@sun568 輕鬆暢聊直接點擊線上聊天 https://gleezy.net/ewvpxw 奈奈157 46 D 22歲 萌系少女外表下潛藏淫蕩小惡魔 上線 口活絕佳的榨精能手 體力持久多次高潮 超浪超慾望 你想要的玩法她都能陪你嘗試 LINE:sun5637 https://line.me/ti/p/wCRqXBBPsE WeChat:yee5669 雙北新竹名單:https://t.me/tea698 台中彰化茶單:https://t.me/taimei52 南部每日好茶:https://t.me/gaox520 高檔茶推薦: https://t.me/sun56877 正妹分享私密約炮: https://t.me/tws668 佳人外送茶|迅速又安全 www.teas0204.com

6 Aug 2026, 18:15 UTC47 viewsread 8 August 2026
Photo

TG:@sun6633 TG:@sun568 輕鬆暢聊直接點擊線上聊天 https://gleezy.net/ewvpxw 娃娃 163cm 47 E奶 22歲 #第一次下海兼職 粉嫩又緊緻 超級敏感水多 喜歡LG 可愛活潑 價位 10000 LINE:sun5637 https://line.me/ti/p/wCRqXBBPsE WeChat:yee5669 雙北新竹名單:https://t.me/tea698 台中彰化茶單:https://t.me/taimei52 南部每日好茶:https://t.me/gaox520 高檔茶推薦: https://t.me/sun56877 正妹分享私密約炮: https://t.me/tws668 佳人外送茶|迅速又安全 www.teas0204.com

6 Aug 2026, 18:14 UTC42 viewsread 8 August 2026
Photo

TG:@sun6633 TG:@sun568 輕鬆暢聊直接點擊線上聊天 https://gleezy.net/ewvpxw 心妍 162cm D奶26歲 電信公司客服 聲音好聽 床上溫柔小女人 很會口 價位 6000 LINE:sun5637 https://line.me/ti/p/wCRqXBBPsE WeChat:yee5669 雙北新竹名單:https://t.me/tea698 台中彰化茶單:https://t.me/taimei52 南部每日好茶:https://t.me/gaox520 高檔茶推薦: https://t.me/sun56877 正妹分享私密約炮: https://t.me/tws668 佳人外送茶|迅速又安全 www.teas0204.com

4 Aug 2026, 09:05 UTC85 views1 reactionsread 8 August 2026
Photo

TG:@sun6633 TG:@sun568 輕鬆暢聊直接點擊線上聊天 https://gleezy.net/ewvpxw 麗雅 166cm 50kg cup 23歲 氣質性感美腿正妹 小女人的fu 床上性感尤物. 口交技術不錯 白皙嫩乳 服務態度好不會擺臉色 LINE:sun5637 https://line.me/ti/p/wCRqXBBPsE WeChat:yee5669 雙北新竹名單:https://t.me/tea698 台中彰化茶單:https://t.me/taimei52 南部每日好茶:https://t.me/gaox520 高檔茶推薦: https://t.me/sun56877 正妹分享私密約炮: https://t.me/tws668 佳人外送茶|迅速又安全 www.teas0204.com

❤1

3 Aug 2026, 08:25 UTC90 viewsread 8 August 2026
Photo

TG:@sun6633 TG:@sun568 輕鬆暢聊直接點擊線上聊天 https://gleezy.net/ewvpxw 琪琪 157cm 46kg E Ccup 20歲 這個天氣適合床上打炮嘿嘿 床上很會撒嬌 #個性溫柔體貼 嘴上功夫厲害 深深情慾刺激你的神經 主動一起洗澡 一邊舔你的DD跟蛋蛋 價位 8000 LINE:sun5637 https://line.me/ti/p/wCRqXBBPsE WeChat:yee5669 雙北新竹名單:https://t.me/tea698 台中彰化茶單:https://t.me/taimei52 南部每日好茶:https://t.me/gaox520 高檔茶推薦: https://t.me/sun56877 正妹分享私密約炮: https://t.me/tws668 佳人外送茶|迅速又安全 www.teas0204.com

Showing the 9 most recent of 9 posts we hold for @taimei52. 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.

Mentions

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.

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.

Cite this entry

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 10 October 2026 — this entry's latest reading, not the date you are reading this.

“台中彰化外送茶LINE:tea232” (@taimei52), 542 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/taimei52.

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.