Telegram RegisterThe public register of Telegram
Telegram profile photo for 美妇安娜预览

Channel

美妇安娜预览

@meifu

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

52subscribers

-6,901 since we began measuring on 13 August 2026

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

Register entry

Telegram ID-1003895653711
TypeChannel
Username@meifu
CreatedBetween 1 February 2026 and 30 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live30 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/meifu

Growth

529,4024,72713 August 2026 — 6,953 subscribers14 August 2026 — 7,109 subscribers17 August 2026 — 7,782 subscribers20 August 2026 — 8,124 subscribers24 August 2026 — 8,999 subscribers27 August 2026 — 9,402 subscribers30 August 2026 — 52 subscribers13 August 202630 August 2026
7 measurements spanning 17 days, net -6,901. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 15:3752-9,350
27 Aug 2026, 16:119,402+403
24 Aug 2026, 11:348,999+875
20 Aug 2026, 11:058,124+342
17 Aug 2026, 19:057,782+673
14 Aug 2026, 17:087,109+156
13 Aug 2026, 20:026,953first reading

Engagement

32 posts held, back to 24 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 15 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
14817.3%
avg views ÷ 52 subscribers
Avg views / post
7,710
20 posts measured
Reaction rate
0.3%
reactions ÷ views · ER floor
Posts in window
20
of 32 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 28 August 2026
Posts held32 (24 July 202628 August 2026)
Views total154,100
Reactions total462
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Aug 2026, 06:41 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.

What this channel posts

Video runtime
11m 21s
Average length
21s

Measured directly from 32 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.

Reaction mix

658 reactions across 32 posts, in 14 distinct kinds. The most used accounts for 48.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
32148.8%
🔥22233.7%
😈324.86%
🥰294.41%
👏233.50%
💯91.37%
👍81.22%
🌭30.456%
🍌20.304%
😁20.304%
😍20.304%
😱20.304%
🦄20.304%
🤪10.152%

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 32 of the 32 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 658 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 32 most recent posts we hold, published 24 July 2026 to 28 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

28 Aug 2026, 10:07 UTC≈2,010 views19 reactionsread 29 August 2026
Video

穿着夹趾袜的漂亮妈妈上一刻还坐在椅子上听儿子贴着耳朵说悄悄话,一转身就蹲在窗边、趴在床沿,开档黑丝把屁股和逼全露出来取悦金主。 更多反差日常在VIP @suoai1024_bot

🔥95😈3🥰2

27 Aug 2026, 13:23 UTC≈2,930 views25 reactionsread 29 August 2026
Video

从陪娃的优雅妈妈,到床上浪叫的开档骚货……安娜完美演绎什么叫双面淫母! 更多反差场景在 @suoai1024_bot

🔥126💯4🍌2🥰1

26 Aug 2026, 12:05 UTC≈3,900 views27 reactionsread 29 August 2026
Video

乖巧妈妈的外表欺骗了所有人,实际上她是金主们随意泄欲的肉便器,骚逼被操得又红又肿。 更多反差在 @suoai1024_bot

14🥰4😈4🌭3👏1🔥1

25 Aug 2026, 12:14 UTC≈4,630 views22 reactionsread 29 August 2026
Video

谁能想到刚才还笑着和儿子比耶的女人,现在正被金主抓着裙子后入,整张脸都贴在桌子上发出浪叫。 更多反差日常在 @suoai1024_bot

17😈3🔥2

24 Aug 2026, 12:34 UTC≈5,280 views20 reactionsread 29 August 2026
Video

谁能想到被金主们轮流当玩具操到浪叫不止的红裙肉便器,带娃时竟然是那样自然的温柔与优雅。 更多反差日常在 @suoai1024_bot

15🔥5

23 Aug 2026, 11:37 UTC≈6,030 views21 reactionsread 29 August 2026
Video

带娃时是温柔的白裙妈妈,转眼就变成金主们专属的插尾巴骚母狗,跪着把屁股高高翘起任人轮流狠插。 看更多美妇反差日常打开 @suoai1024_bot

13🔥5😈2🥰1

22 Aug 2026, 11:44 UTC≈6,620 views21 reactionsread 29 August 2026
Video

带娃时的优雅黑丝美妇,儿子一转身就自己把腿打开、屁股翘起,彻底沉沦成只会发骚的野外母狗。 更多沉沦日常在 @suoai1024_bot

🔥125💯3👍1

21 Aug 2026, 10:47 UTC≈7,480 views32 reactionsread 29 August 2026
Video

儿子还在旁边时是端庄的红裙妈妈,转眼间就被一群肥头大耳的野男人扒光光戴上肛塞。几部手机同时录下美妇被按在落地窗前轮流狂操的全过程。 真实反差母狗日常,打开 @suoai1024_bot

🔥1613😈2🦄1

20 Aug 2026, 13:02 UTC≈7,550 views18 reactionsread 29 August 2026
Video

儿子一走,温柔妈妈秒变骚母狗。金主下令后她马上把黑色束身衣全露出来。 自己蹲下去把骚穴对准镜头,羞耻地把尿一点点撒出来。 更多金主的任务在 @suoai1024_bot

14🔥3🥰1

19 Aug 2026, 12:32 UTC≈7,690 views26 reactionsread 29 August 2026
Video

优雅美妇上一秒还和儿子同饮一杯饮料,场面很温馨。 一转眼就蹲下把骚逼坐进假阳具里上下骑乘,眼神勾人对着镜头取悦金主们。 更多美妇沉沦场景打开 @suoai1024_bot

👏128🔥5😈1

18 Aug 2026, 12:01 UTC≈7,820 views22 reactionsread 29 August 2026
Video

儿子眼里还是那个温柔体贴的好妈妈,一转身就沦为金主们随意玩弄的骚母狗。粉嫩骚逼被大鸡巴狠狠捅进去狂干,每一下都顶到最深,浪叫都压不住…… 更反差的内容尽在 @suoai1024_bot

🔥127🥰3

17 Aug 2026, 15:22 UTC≈8,150 views19 reactionsread 29 August 2026
Video

儿子还在旁边的时候装得那么正经,他一走就躺下把腿分到最开,让金主轮流用真假鸡巴整根捅进骚穴疯狂抽插。 看更骚的美妇来 @suoai1024_bot

🔥115😈3

Showing the 12 most recent of 32 posts we hold for @meifu. 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 3 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 30 August 2026 — this entry's latest reading, not the date you are reading this.

“美妇安娜预览” (@meifu), 52 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/meifu.

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.