14号开可以约,提前一天约就好,怕太久忘啦!下午4点开,在万象城 @qawsed521
❤1🥰1

Channel
@hhgg5201
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Cite this entry
7,478subscribers
+1,318 since we began measuring on 2 October 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002454388818 |
|---|---|
| Type | Channel |
| Username | @hhgg5201 |
| Description | 上课找萌宝 @qawsed521 双向联系 @mengbao5201_bot 聊天群 https://t.me/+Km9og532YykxZGI9 |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 2 October 2026 |
| Last confirmed live | 15 November 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 15 November 2026 |
| On Telegram | t.me/hhgg5201 |
Adult — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 20 October 2026 and assigned it the closest of 31 fixed categories, at 55% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Nov 2026, 17:58 | 7,478 | -12 |
| 10 Nov 2026, 05:49 | 7,490 | -86 |
| 7 Nov 2026, 03:31 | 7,576 | -352 |
| 4 Nov 2026, 03:56 | 7,928 | +502 |
| 31 Oct 2026, 17:46 | 7,426 | +49 |
| 28 Oct 2026, 22:40 | 7,377 | +184 |
| 26 Oct 2026, 07:36 | 7,193 | -112 |
| 23 Oct 2026, 05:47 | 7,305 | +256 |
| 19 Oct 2026, 23:54 | 7,049 | +87 |
| 16 Oct 2026, 19:08 | 6,962 | +344 |
| 13 Oct 2026, 11:07 | 6,618 | -815 |
| 7 Oct 2026, 08:38 | 7,433 | +1,273 |
| 2 Oct 2026, 22:22 | 6,160 | no change |
| 2 Oct 2026, 21:47 | 6,160 | first reading |
22 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 33 pages of Telegram’s post history, 20 posts per page.
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 7 of 9 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 13 November 2026 |
|---|---|
| Posts held | 22 (16 August 2026 – 13 November 2026) |
| Views total | 18,305 |
| Reactions total | 25 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 19 Nov 2026, 18:02 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.
Lifetime counters from Telegram’s own channel header, read 19 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
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.
59 reactions across 17 posts, in 4 distinct kinds. The most used accounts for 89.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 53 | 89.8% | |
| 😁 | 2 | 3.39% | |
| 😭 | 2 | 3.39% | |
| 🥰 | 2 | 3.39% |
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 18 of the 22 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 59 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 22 most recent posts we hold, published 16 August 2026 to 13 November 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.
Telegram’s own ‘edited’ marker: 2 of 9 posts held from the last 30 days (22.2%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
14号开可以约,提前一天约就好,怕太久忘啦!下午4点开,在万象城 @qawsed521
❤1🥰1
🎉🎉🎉 开奖通知 🎉🎉🎉 🔖 防伪编号:H179413131518 🎰 萌宝宝半价/P ⚠️ 抽奖说明: 中奖后请24小时内联系萌宝宝老师(@qawsed521 ),无出击意向不要参与,在三天内完成出击、作业报告向 @chasecdxc_bot 提交 💁 参与情况:69达标 / 73报名 🔋 人品加成:62票 ⚡️× 9 🎅 联系领奖:@野寻·南门 1. DJJ gg 奖品:萌宝宝半价/P 祝大家心想事成好运连连!
明天下午开
❤2
🎰 萌宝宝半价/P 📮 参与条件: 🌏️ 归属地 四川,重庆 🪪 必须设置用户名 🎫 加入-野寻·成都打卡通告群 └ 🔑 发送口令﹝萌萌宝宝﹞ 🎫 加入-萌宝宝后花园 🎫 加入-野寻·成都学生交流群 └ 🎟️ 发言数大于 6 条 🎫 加入-野寻·成都活动公告 🎫 加入-野寻·成都修车档案 ❗ 口令提示: 请先参与抽奖,再发送口令激活 🎁 奖品内容: 💰️ 萌宝宝半价/P × 1 ⚠️ 抽奖说明: 中奖后请24小时内联系萌宝宝老师(@qawsed521 ),无出击意向不要参与,在三天内完成出击、作业报告向 @chasecdxc_bot 提交 🔋 人品加成:⚡️× 9 规则 📅 开奖日期:(北京时间) 2026年11月11日 18时00分00秒
❤1
9号开可以约了宝宝🌚🌚
【妹子花名】:萌宝宝 【妹子车牌】: @qawsed521 【验证留名】:每一天 【验证时间】:9月 【所在位置】:成华 【修车水费】:6 【身高身材】:完美 【妹子年龄】: 18 【湿度紧度昆度评分】: 湿紧 【颜值评分】:10 【身材评分】:9.8 【态度机车评分】:无 【女友感评分】:9 【服务评分】:9 【时间管理评分】:10 【性价比评分】:9.8 【综合评分】:9.9 【优点缺点】:身材好 【是否值得回锅】: 非常值得回锅 【推荐程度】:SSS 【个人发挥】 :在看到宝宝的那一刻就想征服她了,服装千变万化每一样都是一种享受,但每次都是事与愿违,这次终于遇上了,就是没有提前说服装的事情但也没事,主要是宝宝在就行了。 小心的把门打开,看到宝宝在床边坐着,站起身来迎接我来,看着宝宝的妆容非常好看,越看越好看哈哈😗,我主动着与宝宝聊天,宝宝一直说好尴尬呀,嘻嘻,一直在与宝宝聊天破局,然后准备去浴室了,在宝…
❤6🥰1
爱上朵朵要多久
❤3😁1
明天开始认真的开🥰!!!可以预约
❤3
💗南门严选💗 ⌚️ 评价时间:2026-10-22 👩🏻🎓 服务老师:萌宝宝 👨🏻💻 留名:匿名 颜值:9 环境:9 身材:9.4 态度:9.5 服务:9 人照:10 综合:9.32 💌 服务过程 : 临时在群里看到老师,被身材面容吸引到了,随即约了。到了老师的住所,房间蛮不错,进门就被萌宝妹妹白嫩翘臀配上大长腿的身材和可爱迷人的颜值吸引了,妹妹穿了一身黑,显得身材更加有型,很有气质。妹妹脱光了白皙嫩滑的肌肤更是让人血脉喷张。忍不住上手爱抚,触感更是让人流连忘返,吹弹可破丝滑柔嫩的肌肤,忍不住紧紧将她拥入怀里。妹妹的奶子更是柔软细腻。完美的腿型,完美的细腰都很符合我的品味。还要一提的是妹妹绝美的小逼,堪称艺术。大战三百回合后,后入式出货。妹妹女友感满满,颜值在线,值得下次 🔗 老师资料 :https://t.me/chasecd_lsda/1675
❤5😁1
人的眼泪要怎么仰望才能接住悲伤呢
❤5
红休
我曾以为有情可解世间一切遗憾
❤7
Showing the 12 most recent of 22 posts we hold for @hhgg5201. 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.
We recorded 4 posts on @hhgg5201 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
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.
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.
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.
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 15 November 2026 — this entry's latest reading, not the date you are reading this.
“萌宝宝后花园” (@hhgg5201), 7,478 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/hhgg5201.
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.