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

Channel

葫芦娃公益小家庭

@HLWNHNBB

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

17,166subscribers

+7,119 since we began measuring on 11 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1002597307391
TypeChannel
Username@HLWNHNBB
Description葫芦二娃 @HLWNHNBB
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live4 November 2026
Measurements held53
Confirmed unchanged1 time, most recently 4 November 2026
On Telegramt.me/HLWNHNBB

Topic

Gaming — 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 11 August 2026 and assigned it the closest of 31 fixed categories, at 43% 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.

Growth

10,04717,16613,606.511 August 2026 — 10,047 subscribers12 August 2026 — 10,155 subscribers13 August 2026 — 10,348 subscribers15 August 2026 — 10,527 subscribers16 August 2026 — 10,762 subscribers17 August 2026 — 10,863 subscribers18 August 2026 — 10,990 subscribers19 August 2026 — 11,089 subscribers20 August 2026 — 11,185 subscribers22 August 2026 — 11,305 subscribers23 August 2026 — 11,510 subscribers25 August 2026 — 11,613 subscribers26 August 2026 — 11,758 subscribers27 August 2026 — 11,876 subscribers28 August 2026 — 12,010 subscribers29 August 2026 — 12,124 subscribers30 August 2026 — 12,230 subscribers31 August 2026 — 12,349 subscribers1 September 2026 — 12,476 subscribers2 September 2026 — 12,585 subscribers3 September 2026 — 12,753 subscribers5 September 2026 — 12,941 subscribers8 September 2026 — 13,314 subscribers11 September 2026 — 13,605 subscribers13 September 2026 — 13,858 subscribers14 September 2026 — 14,078 subscribers16 September 2026 — 14,216 subscribers18 September 2026 — 14,477 subscribers25 September 2026 — 15,062 subscribers3 October 2026 — 15,865 subscribers8 October 2026 — 16,053 subscribers12 October 2026 — 16,275 subscribers14 October 2026 — 16,337 subscribers15 October 2026 — 16,401 subscribers16 October 2026 — 16,411 subscribers17 October 2026 — 16,472 subscribers18 October 2026 — 16,519 subscribers19 October 2026 — 16,584 subscribers20 October 2026 — 16,654 subscribers21 October 2026 — 16,672 subscribers22 October 2026 — 16,724 subscribers23 October 2026 — 16,806 subscribers24 October 2026 — 16,876 subscribers25 October 2026 — 16,911 subscribers27 October 2026 — 16,939 subscribers28 October 2026 — 16,966 subscribers29 October 2026 — 16,995 subscribers30 October 2026 — 16,980 subscribers31 October 2026 — 17,050 subscribers1 November 2026 — 17,076 subscribers2 November 2026 — 17,129 subscribers3 November 2026 — 17,157 subscribers4 November 2026 — 17,166 subscribers11 August 20264 November 2026
53 measurements spanning 85 days, net +7,119. 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 8,979–18,234 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 53
Measured (UTC)SubscribersChange
4 Nov 2026, 10:0617,166+9
3 Nov 2026, 07:1117,157+28
2 Nov 2026, 05:0617,129+53
1 Nov 2026, 07:4617,076+26
31 Oct 2026, 09:4417,050+70
30 Oct 2026, 09:2816,980-15
29 Oct 2026, 06:4916,995+29
28 Oct 2026, 02:4716,966+27
27 Oct 2026, 00:3416,939+28
25 Oct 2026, 23:0516,911+35
24 Oct 2026, 22:3616,876+70
23 Oct 2026, 22:4516,806+82
22 Oct 2026, 22:0116,724+52
21 Oct 2026, 15:5716,672+18
20 Oct 2026, 10:1716,654+70
19 Oct 2026, 10:3616,584+65
18 Oct 2026, 10:1816,519+47
17 Oct 2026, 06:5616,472+61
16 Oct 2026, 05:3916,411+10
15 Oct 2026, 07:5816,401first reading

Engagement

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

ERR · 30 days
55.1%
avg views ÷ 17,166 subscribers
Avg views / post
9,450
12 posts measured
Reaction rate
0.362%
reactions ÷ views · ER floor
Posts in window
12
of 49 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 31 October 2026
Posts held49 (7 July 2026 – 31 October 2026)
Views total113,450
Reactions total411
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken4 Nov 2026, 15:56 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
32
Videos
5
Links
35

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

Reaction mix

1,496 reactions across 49 posts, in 17 distinct kinds. The most used accounts for 49.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍73449.1%
❤67445.1%
🫡483.21%
🔥100.668%
🎉30.201%
👨‍💻30.201%
😁30.201%
🙉30.201%
🤪30.201%
🥰30.201%
🍌20.134%
👎20.134%
👏20.134%
🤔20.134%
🤯20.134%
👌10.067%
😍10.067%

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

Measured over the 49 most recent posts we hold, published 7 July 2026 to 31 October 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

Telegram’s own ‘edited’ marker: 9 of 12 posts held from the last 30 days (75.0%) 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).

30 Oct 2026, 14:32 UTC≈3,990 views59 reactionsread 4 November 2026
File

葫芦娃和平内核更新日志 修复最新闪框加密 优化已知bug 葫芦娃PUBG内核更新日志 修复载具异常显示,新增敞篷载具显示 对接twt驱动 葫芦娃三角洲内核更新日志 适配最新三角洲千人千面udp解密 葫芦娃频道: @HLWNHNBB

👍48❤11

27 Oct 2026, 00:45 UTC≈5,190 views29 reactionsread 4 November 2026
Forwarded from @gtqnb0000File

👀👀👀三角洲解密公益: 更新内容 不动任何内存! 更新坐标解密 维护所有解密 更新新版豆包驱动 卡密@gtqnb000 绘制:人物细节 容器 物资 盒子等很多细节 适配:Ka 淋雨 豆包 paradise twt驱动 几乎适配全机型适配率很高看大家喜欢使用 解密方式:算法解密 Udp解密 模拟解密等 丝滑流畅支持vk opengl cpu三种渲染方式 支持漏打自瞄可选择部位等很多演戏的细节 不动内存上色内透

👍17❤12

23 Oct 2026, 11:37 UTC≈8,120 views50 reactionsread 4 November 2026
File

葫芦娃和平🎮更新日志: 修开启坐标解密后不绘制乘坐载具的玩家的问题 更新超体职业 修无目标压枪 对接TWT驱动,适配新系列驱动机型用户可以用twt 葫芦娃PUBG🎮更新日志: 适配英文界面,支持中英语音切换(Supports English interface and Chinese-English voice switching) 修复载具缺失bug

👍36❤11🙉2🔥1

20 Oct 2026, 23:09 UTC≈9,080 views18 reactionsread 4 November 2026
File

❤️修复三角洲最新千人千面加密

👍13❤4😁1

16 Oct 2026, 00:47 UTC≈12,400 views23 reactionsread 4 November 2026
File

🎮修复和平精英闪框解密 ❤️修复三角洲最新遁地千人千面加密 来自UC网盘分享文件: 「葫芦娃内核」 链接: https://drive.uc.cn/s/a26899aca9bb4?public=1

👍12❤10🔥1

12 Oct 2026, 23:48 UTC≈13,200 views28 reactionsread 4 November 2026
File

❤️三角洲更新最新解密,修复千人千面加密 🎮PUBG更新最新闪框解密 来自UC网盘分享文件: 「葫芦娃内核」 链接: https://drive.uc.cn/s/a27b258126914?public=1

❤13👍13🤔2

11 Oct 2026, 07:16 UTC≈13,200 views41 reactionsread 4 November 2026
File

修复和平密钥解密失效

👍31❤10

10 Oct 2026, 15:20 UTC≈11,600 views29 reactionsread 4 November 2026
File

修复三角洲解密失效 来自UC网盘分享文件: 「葫芦娃内核」 链接: https://drive.uc.cn/s/481c2ea19cae4?public=1

👍24❤5

8 Oct 2026, 13:38 UTC≈12,100 views31 reactionsread 4 November 2026
File

开放三角洲内核陀螺仪自瞄功能 优化解密二效率 来自UC网盘分享文件: 「葫芦娃内核」 链接: https://drive.uc.cn/s/3c091e0ffba64?public=1

👍20❤8🥰1😁1🙉1

6 Oct 2026, 15:07 UTC≈12,800 views40 reactionsread 4 November 2026
File

❤️修复三角洲解密1解密2失效,并适配最新千人千面加密 🎮修复和平精英最新闪框加密 🎮PUBG对接Paradise驱动,以及自带的内核陀螺仪瞄准 主频道: @appletzpd0 ✍️光头强频道: @gtqnb0000 🎉葫芦娃频道 :@HLWNHNBB 👍万能搜索 @Tab99811111111

👍27❤12👏1

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

@HLWNHNBB edited 2 posts 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
25 August 2026
Most recent edit
30 August 2026

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

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

“葫芦娃公益小家庭” (@HLWNHNBB), 17,166 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/HLWNHNBB.

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.