Telegram RegisterThe public register of Telegram
Telegram profile photo for 真航母,假一赔十

Channel

真航母,假一赔十

@hangmu797864

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

297subscribers

+88 since we began measuring on 22 August 2026

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

Register entry

Telegram ID-1004410328284
TypeChannel
Username@hangmu797864
CreatedBetween 1 June 2026 and 16 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded22 August 2026
Last confirmed live16 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/hangmu797864

Topic

Giveaways & airdrops — 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 23 September 2026 and assigned it the closest of 31 fixed categories, at 67% 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

20929725322 August 2026 — 209 subscribers23 August 2026 — 218 subscribers30 August 2026 — 260 subscribers7 September 2026 — 295 subscribers16 September 2026 — 297 subscribers22 August 202616 September 2026
5 measurements spanning 25 days, net +88. 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 196–310 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 00:41297+2
7 Sept 2026, 16:00295+35
30 Aug 2026, 09:03260+42
23 Aug 2026, 03:34218+9
22 Aug 2026, 09:15209first reading

Engagement

20 posts held, back to 16 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 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 22 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
9s
Average length
5s

Measured directly from 2 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

2 reactions across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤2100.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 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 2 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 16 August 2026 to 22 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

22 Aug 2026, 07:16 UTC61 viewsread 22 August 2026
Photo

🎉 惠州逍遥阁赞助【航母】 🎁 奖品清单 • 200 优惠劵 × 2 🛡️ 参与条件 • 加入 惠州逍遥阁 • 加入 真航母,假一赔十 • 加入 惠州逍遥阁新公开榜 • 需消耗嫩妹币:22 • 必须设置用户名 🔮 祝福加持 • 祝福消耗:22嫩妹币 • 祝福上限:35次 • 祝福一次增加一个抽奖号,提高中奖率 ⌛ 开奖时间 • 2026-08-24 16:19:00 📜 抽奖说明 刷屏、灌水、纯表情、复制粘贴、无意义对话、撤回内容等,一律视为无效发言,不计入统计! 再次重申:灌水无意义发言都不兑奖!请用心交流。 活动最终解释权归 惠州逍遥阁 管理团队所有。 中奖的联系(@hangmu676)约时间 24小时内预约时间,七天内出击,过时自动作废,老师休息,自动延期 炸号需找管理验证,无法验证,奖品放回奖池重新抽奖 中奖需本人出击不得转让 用了优惠劵要写报告! 不去不要参加! ✨ 愿好运伴随每一位参与者,祝大家好运!

20 Aug 2026, 09:13 UTC169 viewsread 22 August 2026
Forwarded from @lzcxdd6

惠州逍遥阁报告模板-叁 【出击老师】: #航母 @hangmu6666 【提交学生】:西池(笔名) 【实际支付费用】:7张 【服务日期】: 八月二十四号 【服务地区】:麦地 【环境与卫生】:老小区房整体还行 【人照片相符度】:相符 (很相符 /基本相符 /差异较大) 【身高与体型参考】:f!有感觉吗 【目测年龄(估计)】: 二十四左右 【服务内容简略】:胸推毒龙🐍都有 (例如:#kiss #舌吻 #六九 #洗吹做 #鸳鸯浴 #水中萧 ) 【态度/沟通】: 配合度高 【需要改进的/需要加强的方面】:整体还行 【是否愿意回访/推荐】:会 【建议与出击体验总结】:按照约定的时间,来到老师地方。在一个小区内,比较安全。 老师个子小小的,人照一致。缴费,洗澡。老师脱光衣服,胸是真的太大啦,屁股大有肉。老师会用奶子涂上沐浴露,然后两人抱在一起摩擦。 洗完,上床。老师开始服务,上身到处舔,舔了好久。然后开始吃蛋蛋吃…

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

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.

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

“真航母,假一赔十” (@hangmu797864), 297 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/hangmu797864.

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.