pay 支付门票 通道 https://www.kkday.com/ja https://www.kkday.com/zh-hk https://www.klook.com/zh-HK/experiences/list/japan-day-trips/g12-cate10/ https://www.headout.com/help/ https://www.pelago.co/ https://www.lonelyplanet.com/ https://feverup.com/m/114961 https://www.thrillophilia.com/ https://experiences.travel.rakuten.com/experiences/20093 https://www.traveloka.com/en-id/activities/singapore/product/universal…

Channel
公主-门票-ai-进算朋友圈
@HMZ518
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
1,043subscribers
+84 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 | -1003224139487 |
|---|---|
| Type | Channel |
| Username | @HMZ518 |
| Created | Between 1 October 2025 and 31 December 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 26 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 26 August 2026 |
| On Telegram | t.me/HMZ518 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Aug 2026, 09:46 | 1,043 | +23 |
| 23 Aug 2026, 02:06 | 1,020 | +3 |
| 19 Aug 2026, 11:57 | 1,017 | +8 |
| 16 Aug 2026, 21:18 | 1,009 | +43 |
| 8 Aug 2026, 16:05 | 966 | +7 |
| 8 Aug 2026, 00:48 | 959 | no change |
| 7 Aug 2026, 19:01 | 959 | first reading |
Engagement
18 posts held, back to 28 July 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 · 30 days
- 56.6%
- avg views ÷ 1,043 subscribers
- Avg views / post
- 590
- 17 posts measured
- Reaction rate
- 0.2%
- reactions ÷ views · ER floor
- Posts in window
- 18
- of 18 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 6 of 17 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 | 18 (28 July 2026 – 7 August 2026) |
| Views total | 10,037 |
| Reactions total | 7 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 00:48 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
- 9s
- Average length
- 9s
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
7 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 71.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 5 | 71.4% | |
| 👎 | 2 | 28.6% |
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 6 of the 18 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 7reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 28 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
无限收awsb 有的来报价 来号主,中介勿扰
无限收awsb 有的联系
https://dreamina.capcut.com/ja-jp/ 做日本环境 日本专区 🍎🔥 《挑头》 日本黑pp也可以支付 🍎🔥鱼给码就进 超级丝滑 看图下单 1️⃣0️⃣4️⃣0️⃣0️⃣日元 用微软邮箱注册 给我账号密码核销 一个账号打一笔 12840积分 长期要
以上频道通道长期收 收Claude 大 中 小额 收OAI T5 收OR 收Awsb 收Gemini T3 各种ai资源 日需100万美刀。欢迎各大工作室来对接,可上押,可⚡️⚡️。 收各种门票,冷门票代售 都是自己一手核销🙂😆🙂😆 ⚡️⚡️⚡️@HYL222222
👎2
https://openart.ai/suite/sign-in?callbackUrl=https%3A%2F%2Fopenart.ai%2Fsuite%2Fdirector&error=OAuthAccountNotLinked 最新ai通道 下单订阅每月10万积分账号 打之前截图问我
❤3
https://www.expedia.com/things-to-do/a.a190117.activity-details?startDate=2026-08-21&endDate=2026-08-24&rid=6140449&pwaDialog=offers-list-dialog-%3ARlpl5dd9%3A 香港迪士尼门票 谁能打 3 D通道 全球可射,电商,同步鱼 免3 欧美国家 法国 英国好近 今天打明天日期,快消 保票出 懂的来 日期不要选错了
❤2
https://console.x.ai/team/default/billing gok api 能充值的来
⚡️⚡️⚡️⚡️ 批量收克劳德官key 20刀
https://www.expedia.com/things-to-do/a.a190117.activity-details?startDate=2026-08-21&endDate=2026-08-24&rid=6140449&pwaDialog=offers-list-dialog-%3ARlpl5dd9%3A 香港迪士尼门票 谁能打 3 D通道 全球可射,电商,同步鱼 免3 欧美国家 法国 英国好近 今天打明天日期,快消 保票出 懂的来 日期不要选错了
https://openrouter.ai 可以自定义金额, 大小通吃 能出的 滴滴 全球料可射, 2d 3d 同步 电商鱼 通通可射 速刷《5️⃣分钟》 秒回款 懂的来 无限量收
公主-门票-ai-进算朋友圈 pinned «⚡️⚡️⚡️⚡️ 长期收全球景点门票自营店铺核销 , 韩国 新加坡 香港 越南 泰国 日本 等等全球门票 冷门票可以代售, ⚡️⚡️⚡️@HYL222222 🥰🥰🥰🥰🥰🥰»
Showing the 12 most recent of 18 posts we hold for @HMZ518. 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 — 1,519,786 of 1,604,161entries 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 26 August 2026 — this entry's latest reading, not the date you are reading this.
“公主-门票-ai-进算朋友圈” (@HMZ518), 1,043 subscribers as measured 26 August 2026. Telegram Register, tgregister.com/channel/HMZ518.
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.