Telegram RegisterThe public register of Telegram
Telegram profile photo for 虫八半火主频道

Channel

虫八半火主频道

@QBBHNB

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

29,348subscribers

+319 since we began measuring on 20 August 2026

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

Register entry

Telegram ID-1002479232077
TypeChannel
Username@QBBHNB
Description虫八yyds
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded20 August 2026
Last confirmed live30 August 2026
Measurements held10
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/QBBHNB

Growth

29,02929,34829,188.520 August 2026 — 29,029 subscribers21 August 2026 — 29,071 subscribers22 August 2026 — 29,264 subscribers24 August 2026 — 29,296 subscribers25 August 2026 — 29,319 subscribers26 August 2026 — 29,328 subscribers27 August 2026 — 29,344 subscribers28 August 2026 — 29,346 subscribers29 August 2026 — 29,347 subscribers30 August 2026 — 29,348 subscribers20 August 202630 August 2026
10 measurements spanning 10 days, net +319. 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 28,981–29,396 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 12:0429,348+1
29 Aug 2026, 09:0829,347+1
28 Aug 2026, 11:0229,346+2
27 Aug 2026, 08:4229,344+16
26 Aug 2026, 07:0729,328+9
25 Aug 2026, 05:3529,319+23
24 Aug 2026, 05:0629,296+32
22 Aug 2026, 14:5229,264+193
21 Aug 2026, 04:5629,071+42
20 Aug 2026, 17:4529,029first reading

Engagement

51 posts held, back to 10 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 24 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
10.7%
avg views ÷ 29,348 subscribers
Avg views / post
3,130
49 posts measured
Reaction rate
1.57%
reactions ÷ views · ER floor
Posts in window
51
of 51 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 August 2026
Posts held51 (10 August 202631 August 2026)
Views total153,314
Reactions total2,402
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken31 Aug 2026, 10:05 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
423
Videos
59
Links
109

Lifetime counters from Telegram’s own channel header, read 31 August 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
39s
Average length
13s

Measured directly from 3 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,402 reactions across 49 posts, in 22 distinct kinds. The most used accounts for 80.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1,92480.1%
🍌1164.83%
1034.29%
😍371.54%
🕊281.17%
😁251.04%
🤬240.999%
🤡230.958%
😘200.833%
🤩200.833%
😡170.708%
🤓130.541%
🐳120.5%
👏120.5%
😭110.458%
🎃30.125%
💋30.125%
😈30.125%
🥰30.125%
🎉20.083%
2 further kinds30.125%

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

Measured over the 51 most recent posts we hold, published 10 August 2026 to 31 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

31 Aug 2026, 07:53 UTC135 views13 reactionsread 31 August 2026
Forwarded from @ohbojvi

从现在开始 我会代替小乐 售卖 日韩 越南 台湾 账号 目前不支持回收账号 我会持续发布账号 如果等不了的可以去找 @ahswbb 淘号 日韩账号价格100-99999 越南账号价格500-99999 台湾账号价格1000-99999

👍111🕊1

Signed (在线秒回) 阿海

31 Aug 2026, 04:07 UTC462 views24 reactionsread 31 August 2026

去频道里面下载新的

👍231

Signed 虫 八

31 Aug 2026, 04:07 UTC461 views25 reactionsread 31 August 2026

工艺了 上面安装包更新了

👍232

Signed 虫 八

31 Aug 2026, 02:46 UTC516 views18 reactionsread 31 August 2026
Forwarded from @ZTRBHNBFile

猪头肉公益半火🌟 卡密:D132CCA46094E363E5A6CE149B7C4C8E 适配游戏客户端(64bit) 🎮 全球 🎮 越南 🎮 日韩 🎮 台湾 功能介绍: ✅自瞄增强 三模式+倒地不瞄+范围调节 ✅无后座 枪械据点 射程提升 防抖等功能 ✅除草 除雾 黑天 人物上色8种颜色功能 ✅自定义人物速度和自定义调节广角功能 ✅武器枪魂 枪械变大 人物变大娱乐功能 ✅大厅金色名字 水印 Logo 加载画面功能 ✅猪头肉所有功能包括娱乐功能安全 猪头肉半火官方频道 @ZTRBHNB ( 觉得好用的记得宣传支持就是更新的动力)

👍152🤬1

Signed 虫 八

30 Aug 2026, 03:00 UTC≈1,170 views35 reactionsread 31 August 2026

剧本演给大爷大妈看

👍34🤬1

Signed HOPE负责人(远程请提供订单截图)

29 Aug 2026, 18:42 UTC≈1,340 views72 reactionsread 31 August 2026

你们要开学了我怎么办

👍33🤡18😭11🍌3👏3🙈21🤬1

Signed 虫 八

27 Aug 2026, 04:16 UTC≈2,590 views42 reactionsread 31 August 2026

这一看就是尸体美化

👍34💋3😘31🤬1

Signed 秋小成

27 Aug 2026, 03:25 UTC≈2,680 views39 reactionsread 31 August 2026

羡慕了,已经报J

👍35🕊4

Signed 相柳

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

21 Aug 2026, 10:52 UTCAnonymous Poll2,530 voters approx.

我该支持谁

  1. 春圣54%
  2. 故雪30%
  3. 假话16%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 51 most recent posts we hold, published 10 August 2026 to 31 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Citation-graph rank

Citation-graph rank — 355,427 of 1,628,524entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

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

“虫八半火主频道” (@QBBHNB), 29,348 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/QBBHNB.

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.