Telegram RegisterThe public register of Telegram
Telegram profile photo for 葫芦娃公益大家庭

Channel

葫芦娃公益大家庭

@HLWNHNB

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

110,364subscribers

+17,970 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID-1003536983205
TypeChannel
Username@HLWNHNB
Description<<<<<<<<<<<<<<< 免责声明 >>>>>>>>>>>>>>> 开发者不会主动联系你 本项目也没有任何收费及内部 葫芦娃不会诋毁任何人及项目 网络上任何流言也要注意甄别 本项目仅供逆向学习研究 体验者的任何行为与作者无关 若有侵权违法行为,请联系我删除内容 请在24小时内删除本应用[下载代表同意本协议] 开发者: https://t.me/jiekenhkm 欢迎使用葫芦娃和平精英公益辅助
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live24 September 2026
Measurements held33
Confirmed unchanged1 time, most recently 24 September 2026
On Telegramt.me/HLWNHNB

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 22 August 2026 and assigned it the closest of 31 fixed categories, at 48% 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

92,394110,364101,3797 August 2026 — 92,394 subscribers7 August 2026 — 92,459 subscribers8 August 2026 — 92,675 subscribers9 August 2026 — 93,140 subscribers10 August 2026 — 93,821 subscribers11 August 2026 — 94,529 subscribers12 August 2026 — 94,910 subscribers14 August 2026 — 95,428 subscribers15 August 2026 — 96,190 subscribers16 August 2026 — 96,844 subscribers17 August 2026 — 97,133 subscribers18 August 2026 — 97,440 subscribers19 August 2026 — 97,725 subscribers20 August 2026 — 98,021 subscribers22 August 2026 — 98,643 subscribers24 August 2026 — 99,347 subscribers25 August 2026 — 99,729 subscribers26 August 2026 — 100,326 subscribers27 August 2026 — 101,339 subscribers28 August 2026 — 102,149 subscribers29 August 2026 — 102,878 subscribers30 August 2026 — 103,604 subscribers31 August 2026 — 104,193 subscribers1 September 2026 — 104,798 subscribers2 September 2026 — 105,360 subscribers4 September 2026 — 106,301 subscribers7 September 2026 — 107,086 subscribers10 September 2026 — 107,445 subscribers12 September 2026 — 108,136 subscribers14 September 2026 — 108,531 subscribers16 September 2026 — 108,739 subscribers18 September 2026 — 109,113 subscribers24 September 2026 — 110,364 subscribers7 August 202624 September 2026
33 measurements spanning 48 days, net +17,970. 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 89,699–113,060 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
24 Sept 2026, 21:39110,364+1,251
18 Sept 2026, 14:15109,113+374
16 Sept 2026, 04:20108,739+208
14 Sept 2026, 08:54108,531+395
12 Sept 2026, 14:16108,136+691
10 Sept 2026, 11:56107,445+359
7 Sept 2026, 05:56107,086+785
4 Sept 2026, 10:19106,301+941
2 Sept 2026, 20:36105,360+562
1 Sept 2026, 16:57104,798+605
31 Aug 2026, 16:34104,193+589
30 Aug 2026, 15:19103,604+726
29 Aug 2026, 12:05102,878+729
28 Aug 2026, 13:44102,149+810
27 Aug 2026, 10:53101,339+1,013
26 Aug 2026, 08:07100,326+597
25 Aug 2026, 05:1699,729+382
24 Aug 2026, 03:5499,347+704
22 Aug 2026, 09:2398,643+622
20 Aug 2026, 21:1498,021first reading

Engagement

138 posts held, back to 22 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 121 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
25.6%
avg views ÷ 110,364 subscribers
Avg views / post
28,200
69 posts measured
Reaction rate
0.454%
reactions ÷ views · ER floor
Posts in window
69
of 138 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 27 September 2026
Posts held138 (22 July 2026 – 27 September 2026)
Views total1,947,110
Reactions total8,832
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Sept 2026, 03:11 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

Photos
66
Videos
13
Links
18

Lifetime counters from Telegram’s own channel header, read 28 September 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.

Video runtime
43s
Average length
22s

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

17,099 reactions across 138 posts, in 15 distinct kinds. The most used accounts for 67.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍11,55567.6%
❤3,03417.7%
😍8014.68%
😭5613.28%
🍌3672.15%
🔥1450.848%
🤓1320.772%
🤩1020.597%
🗿950.556%
🌚740.433%
🤗660.386%
🦄610.357%
🥰520.304%
🌭460.269%
😘80.047%

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

Measured over the 138 most recent posts we hold, published 22 July 2026 to 27 September 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

27 Sept 2026, 15:15 UTC≈3,280 views106 reactionsread 28 September 2026
Forwarded from @appletzpdFile

小烧鸡和平🎮 修复侧边血条不能改颜色 增加血条显示距离调节 小烧鸡PUBG🎮 修复真人人机识别bug 主频道: @appletzpd 无广频道: @GAMEyunduan

👍94❤8🍌2😍2

27 Sept 2026, 14:34 UTC≈10,200 views108 reactionsread 28 September 2026
File

葫芦娃三角洲公益解密内核 修复解密部分用户失效 老版本解密有效果的可以不用换 频道: @HLWNHNB

👍100❤8

27 Sept 2026, 03:07 UTC≈9,820 views156 reactionsread 28 September 2026

三角洲解密正在优化中,心急吃不了热几把

👍132🌚11🍌6❤4🥰3

26 Sept 2026, 01:28 UTC≈17,400 views187 reactionsread 28 September 2026

三角洲解密没效果的报一下 手机型号: 安卓版本: 内核版本号:

👍155❤16🗿8😍8

25 Sept 2026, 13:40 UTC≈45,600 views188 reactionsread 28 September 2026
File

尝试修复三角洲解密第二局失效 解决三角洲千人千面加密,目前找了5台不同的设备测试都有效果,你们先试试吧,没效果我再看看 频道: @HLWNHNB

👍145❤38🥰5

25 Sept 2026, 10:34 UTC≈20,900 views137 reactionsread 28 September 2026

啥情况,三角洲解密有效果的出来吱个声,我自己测试没毛病啊

👍117❤15🔥5

25 Sept 2026, 09:19 UTC≈21,200 views147 reactionsread 28 September 2026

解密没效果的换网络再试试,移动运营商就换到电信联通的运营商试试,换完网络重新开一下解密

👍126❤16🔥5

25 Sept 2026, 08:57 UTC≈26,800 views165 reactionsread 28 September 2026
File

优化解密兼容性,解决部分用户三角洲解密失效 频道: @HLWNHNB 永久公益解密内核

👍146❤15🔥4

25 Sept 2026, 02:11 UTC≈22,300 views123 reactionsread 28 September 2026

等会儿优化一下三角洲解密兼容,应该可以解决大部分解密没效果的问题

👍109❤14

24 Sept 2026, 15:49 UTC≈36,400 views186 reactionsread 28 September 2026
File

葫芦娃 更新闪框解密 修复安卓10适配问题 修复新版本空投绘制问题 @HLWNHNB

👍155❤22🤗5🤓4

24 Sept 2026, 13:23 UTC≈23,600 views152 reactionsread 28 September 2026

三角洲所有人都没效果还是什么情况 有没有有效果的

👍138❤7🍌7

24 Sept 2026, 12:25 UTC≈43,600 views170 reactionsread 28 September 2026
File

更新解密 驱动par,之前发的压缩包里面有 @HLWNHNB 永久公益解密内核

👍150❤11😭4🔥3🦄2

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

Posts edited after publishing

@HLWNHNB edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
16 September 2026
Most recent edit
16 September 2026

Forward network

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 15 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.

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

“葫芦娃公益大家庭” (@HLWNHNB), 110,364 subscribers as measured 24 September 2026. Telegram Register, tgregister.com/channel/HLWNHNB.

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.