Telegram RegisterThe public register of Telegram

Channel

茉莉花开

@mlhkyyf

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

1,669subscribers

+116 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1003979145371
TypeChannel
Username@mlhkyyf
CreatedBetween 1 April 2026 and 20 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/mlhkyyf

Growth

1,5531,6691,6117 August 2026 — 1,553 subscribers7 August 2026 — 1,559 subscribers7 August 2026 — 1,559 subscribers10 August 2026 — 1,654 subscribers14 August 2026 — 1,669 subscribers7 August 202614 August 2026
5 measurements spanning 7 days, net +116. 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 1,536–1,686 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 06:371,669+15
10 Aug 2026, 14:221,654+95
7 Aug 2026, 21:311,559no change
7 Aug 2026, 16:211,559+6
7 Aug 2026, 14:311,553first reading

Engagement

16 posts held, back to 20 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
72.6%
avg views ÷ 1,669 subscribers
Avg views / post
1,210
14 posts measured
Reaction rate
0.311%
reactions ÷ views · ER floor
Posts in window
16
of 16 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. It is computed over the 5 of 14 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held16 (20 July 20267 August 2026)
Views total16,960
Reactions total19
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 21:31 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
16s
Average length
16s

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

19 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 84.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1684.2%
315.8%

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

Measured over the 16 most recent posts we hold, published 20 July 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, 15:10 UTC354 viewsread 7 August 2026

emby清理了机器人 先有空位 https://t.me/+GWgi0z8hWWw1ZDFl

27 Jul 2026, 09:48 UTC≈2,030 views0 reactionsread 7 August 2026

前提:服务器被打 或者压力就不搞了 勿泄露地址 茉莉花emby(测试)https://t.me/mlhembylt 现开放60名注册 资源用户共建 不签到不保号

27 Jul 2026, 08:19 UTC≈1,930 viewsread 7 August 2026
Photo

【茉莉花音乐服 · 赞助群专属福利】EchoBox 内测名额开放申请 各位茉莉花的朋友们好~ 有个群友老哥做了一款音乐播放器 App,叫 EchoBox,这次特意为咱们茉莉花做了些专属适配(比如逐字歌词特效),现在开放一批 iOS TestFlight 内测名额给赞助群,大家可以先体验一下~ 开发者自己说的:之前基本是闭门造车,主要是满足自己用着顺手,所以肯定还有不少毛病和不完善的地方,体验的时候多多担待,也欢迎大家帮忙挑挑刺~ 名额:10 个,先到先得,发完即止 怎么申请: 发一封邮件到 📮 [email protected],简单写一下: 你的 Apple ID 邮箱(用于开通 TestFlight 测试资格) 想说的一句话都行(没有也没关系) 收到邀请后记得关注一下 TestFlight 的邮件通知~ 体验后: 欢迎加入反馈交流群,有什么问题、建议、bug 都可以在里面提: 👉 https://t

27 Jul 2026, 05:01 UTC956 viewsread 7 August 2026
Photo

茉莉emby用户共建服 测试阶段 如若遇到泄露IP等被攻击 停服 如果有后续 可能需要用户提供些不用的网盘来扩建 第一批需要自己有搜索光鸭云盘链接 磁力种子等能力

26 Jul 2026, 05:53 UTC874 viewsread 7 August 2026

所有bot已恢复正常 如若有用户bot没有恢复 请使用 /bind 命令进行绑定Navidrome账号即可

24 Jul 2026, 11:14 UTC≈1,300 views0 reactionsread 7 August 2026
Photo

🎉 茉莉音乐服 🎁 抽奖活动已开始! ━━━━━━━━━━━━━━ 🎰 开奖模式:刮刮乐 🎁 奖品: ▸ 1号机器人注册码 x30 📣 发布群组: ▸ 茉莉公益音乐服(无损) ▸ 茉莉花开 📋 参与要求: ▸ 订阅 茉莉公益音乐服(无损) ▸ 订阅 茉莉花开 ━━━━━━━━━━━━━━ 🍀 祝所有参与者好运!

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

Citation-graph rank — 576,433 of 1,478,351entries 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.

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

“茉莉花开” (@mlhkyyf), 1,669 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/mlhkyyf.

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.