Telegram RegisterThe public register of Telegram
Telegram profile photo for 美娜的后花园

Channel

美娜的后花园

@meina6687

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

708subscribers

+42 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1003749174823
TypeChannel
Username@meina6687
CreatedBetween 1 February 2026 and 24 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live19 September 2026
Measurements held6
Confirmed unchanged2 times, most recently 19 September 2026
On Telegramt.me/meina6687

Topic

Other / unclassifiable — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 88% 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

6667086878 August 2026 — 666 subscribers8 August 2026 — 666 subscribers16 August 2026 — 671 subscribers24 August 2026 — 676 subscribers31 August 2026 — 690 subscribers10 September 2026 — 708 subscribers8 August 202610 September 2026
6 measurements spanning 33 days, net +42. 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 660–714 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Sept 2026, 12:20708+18
31 Aug 2026, 14:23690+14
24 Aug 2026, 18:58676+5
16 Aug 2026, 06:07671+5
8 Aug 2026, 12:30666no change
8 Aug 2026, 12:17666first reading

Engagement

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

What this channel posts

Video runtime
10s
Average length
10s

Measured directly from 1 video 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

3 reactions across 2 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3100.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 2 of the 20 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 3 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

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

3 Aug 2026, 05:51 UTC467 views1 reactionsread 8 August 2026
Forwarded from @zzclbgPhoto

【时间】:2026-07-07 【老师】:苍井美娜 【留名】:大富豪 【人照】:9 【颜值】:9.5 【身材】:9 【服务】:9.5 【态度】:9 【环境】:9 【综合】:9.17 【过程】:进门就像是回家的感觉,教室很干净,一进来老师先是问累不累,让我坐下休息会儿再开始,休息期间会问我喝不喝水,情绪价值拉满,然后我抽了根烟,接着就是共浴,老师洗澡洗的很细心细致,在浴室就开始调情,那感觉太舒服了,飘飘欲仙,洗完后会贴心的帮我擦干身体和脚,接着就是做服务,69,毒🐲服务一样也不少,🐍吻很上瘾,口的也舒服,深喉yyds,我只能说太贴心了叭!老师的胸型特别好,看着鸡吧就硬了,做完一整套服务,戴上小🌂,然后开始做爱,让我没想到的是老师好多水啊,太舒服了,就像和女朋友做爱一样,简直巴适得板,这是我约过的做爱最舒服的一位老师,太棒啦,有机会还会去N刷的,哈哈,最后鸡吧的抽插声混着水声,中枢神经一下兴奋了,射了好多,射完之后也不会催,还做事后

1

31 Jul 2026, 09:32 UTC564 views2 reactionsread 8 August 2026

【时间】:2026-07-30 【老师】:苍井美娜 【留名】:匿名 【人照】:9 【颜值】:9.2 【身材】:9 【服务】:9.7 【态度】:9.5 【环境】:9 【综合】:9.23 【过程】:遥控上楼,老师看着挺养眼,进门课室氛围好极好,跟老师聊了一会交水费,手牵手一起洗澡,洗澡过程中有ab面服务,好家伙,有水中萧,老师口技很厉害,坚持不住了赶紧结束洗澡,上床之后也有ab面服务,第一次体验毒龙,太厉害了,后面就是持枪上阵,犹豫今天状态不对,而且老师口技太厉害,这回真123了。喜欢服务类老师可以冲!总的来说莞式服务一流,老师性格时而温柔时而火辣,细枝硕果,把玩起来很舒服,服务过程老师接受程度高,很配合,也放的开,不催时间,结束时间还跟老师聊了一会天,不健谈,女友感,情绪价值还是有的。走的时候老师还温柔再见。下次会反。

2

Showing the 12 most recent of 20 posts we hold for @meina6687. 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.

Forward network

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.

Mentions

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.

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

“美娜的后花园” (@meina6687), 708 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/meina6687.

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.