Channel
@taimei52
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
523subscribers
+7 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002136570369 |
|---|---|
| Type | Channel |
| Username | @taimei52 |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/taimei52 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 11:44 | 523 | +5 |
| 14 Aug 2026, 21:46 | 518 | +1 |
| 8 Aug 2026, 10:02 | 517 | +1 |
| 8 Aug 2026, 04:04 | 516 | no change |
| 7 Aug 2026, 23:45 | 516 | first reading |
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 pageof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 1 of 9 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 9 (3 August 2026 – 7 August 2026) |
| Views total | 449 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 04:04 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.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 1reactions 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.
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
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
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
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
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
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
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
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
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.
Citation-graph rank — 42,638 of 1,583,249entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“台中彰化外送茶LINE：tea232” (@taimei52), 523 subscribers as measured 22 August 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.