Telegram RegisterThe public register of Telegram
Telegram profile photo for 际会主频道

Channel

际会主频道

@JHNBQQ

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

9,864subscribers

-494 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001935436339
TypeChannel
Username@JHNBQQ
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live7 September 2026
Measurements held22
Confirmed unchanged1 time, most recently 7 September 2026
On Telegramt.me/JHNBQQ

Topic

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

9,86410,35810,1117 August 2026 — 10,358 subscribers7 August 2026 — 10,358 subscribers8 August 2026 — 10,341 subscribers9 August 2026 — 10,317 subscribers10 August 2026 — 10,288 subscribers11 August 2026 — 10,278 subscribers12 August 2026 — 10,248 subscribers13 August 2026 — 10,230 subscribers15 August 2026 — 10,213 subscribers16 August 2026 — 10,172 subscribers17 August 2026 — 10,151 subscribers18 August 2026 — 10,138 subscribers19 August 2026 — 10,113 subscribers20 August 2026 — 10,103 subscribers21 August 2026 — 10,085 subscribers23 August 2026 — 10,065 subscribers24 August 2026 — 10,038 subscribers25 August 2026 — 10,014 subscribers26 August 2026 — 9,994 subscribers30 August 2026 — 9,957 subscribers2 September 2026 — 9,921 subscribers7 September 2026 — 9,864 subscribers7 August 20267 September 2026
22 measurements spanning 31 days, net -494. 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 9,790–10,432 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 22
Measured (UTC)SubscribersChange
7 Sept 2026, 05:189,864-57
2 Sept 2026, 08:369,921-36
30 Aug 2026, 00:559,957-37
26 Aug 2026, 17:149,994-20
25 Aug 2026, 15:3410,014-24
24 Aug 2026, 18:1610,038-27
23 Aug 2026, 04:1610,065-20
21 Aug 2026, 18:0610,085-18
20 Aug 2026, 14:3610,103-10
19 Aug 2026, 15:0510,113-25
18 Aug 2026, 16:5510,138-13
17 Aug 2026, 18:0510,151-21
16 Aug 2026, 17:3810,172-41
15 Aug 2026, 02:1610,213-17
13 Aug 2026, 17:4910,230-18
12 Aug 2026, 17:5710,248-30
11 Aug 2026, 18:2110,278-10
10 Aug 2026, 19:5710,288-29
9 Aug 2026, 16:3710,317-24
8 Aug 2026, 14:4610,341first reading

Engagement

21 posts held, back to 20 September 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 36 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.436%
avg views ÷ 9,864 subscribers
Avg views / post
43.0
1 post measured
Reaction rate
9.30%
reactions ÷ views · ER floor
Posts in window
1
of 21 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 26 August 2026
Posts held21 (20 September 202526 August 2026)
Views total43
Reactions total4
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Aug 2026, 04:22 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

Video runtime
47s
Average length
47s

Measured directly from 1 video 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

33 reactions across 14 posts, in 7 distinct kinds. The most used accounts for 63.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2163.6%
👍412.1%
❤‍🔥26.06%
😨26.06%
😱26.06%
🎉13.03%
🤔13.03%

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

Measured over the 21 most recent posts we hold, published 20 September 2025 to 26 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

19 Jun 2026, 07:10 UTC460 views2 reactionsread 29 August 2026
Forwarded from @XSBYNBFile

#define GNames_Offset 0xA5A1F38 #define GEngine_Offset 0x13022970 //ULocalPlayer #define GEngine_Offset 0x13048328 //UEngine #define GUObject_Offset 0x12D84B80 #define GetActorArray_Offset 0xD3EA0FC #define GNativeAndroidApp_Offset 0x12ABBBA8 #define Actors_Offset 0xA0 #define LaunchBP_Offset 0x875FAC0 #define ShootBulletInner_Offset 0xD9A4D74 #define UpdateVolleyShootParameters_Offset 0x80A7AE4 #define GetCameraRot

2

Signed 秦始皇

19 Jun 2026, 07:08 UTC413 views1 reactionsread 29 August 2026
Forwarded from @XSBYNBFile

国体 4.5.3 64位 @XSBYNB

🎉1

Signed 秦始皇

7 Jun 2026, 02:42 UTC646 viewsread 29 August 2026

高考加油!祝各位考生金榜题名!

Signed 世界小九 共同号

5 May 2026, 04:44 UTC968 viewsread 29 August 2026
Video

全网独家一颗子弹多段伤害,实现了你们最喜欢的颗秒

Signed 世界小九 共同号

25 Apr 2026, 05:02 UTC≈1,130 views3 reactionsread 29 August 2026

谁知道哪里有卖6月24号之前的老号的

3

Signed

10 Apr 2026, 11:23 UTC≈1,390 views2 reactionsread 29 August 2026
File

#define GNames_Offset 0xA19DAFC #define GEngine_Offset 0x12A909F0 //ULocalPlayer #define GEngine_Offset 0x12AB6358 //UEngine #define GUObject_Offset 0x127F30A0 #define GetActorArray_Offset 0xCFF8204 #define Canvas_Map_Offset 0x12A86230 #define GNativeAndroidApp_Offset 0x12537998 #define Actors_Offset 0xA0 以上偏移应该是正确的 @XSBYNB

2

Signed 秦始皇

7 Mar 2026, 12:22 UTC≈1,550 views2 reactionsread 29 August 2026
File

国体4.3.4 64位SDK集成 内置偏移

2

Signed 秦始皇

28 Feb 2026, 17:07 UTC≈1,610 views2 reactionsread 29 August 2026
File

学生妹国体追踪: 简化的流畅绘制结构 内置双函数SH/UP可切换 功能广角、射速、瞬击、枪械一键 超精准追踪瞄准 TG:@XSBYNB ----- #国体 #追踪

2

Signed 秦始皇

21 Dec 2025, 11:49 UTC≈1,950 views1 reactionsread 29 August 2026
Forwarded from @TUSHAMODFile

本优国体追踪5.1.1 适配最新4.2.3 32&64 优化代码逻辑 优化掉帧 修复自动开火闪退 修复探头路飞没效果 『必开自瞄』 有任何问题联系: @SJNP66 >======配置路径======< 32&64路径: /data/data/com.tencent.igce/Shijie.ini >======跨进程======< https://www.123912.com/s/nu2bjv-RSk63 >=======频道=======< 官方频道: @TUSHAMOD

1

Signed 世界 (淡网)

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

Republished by

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

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

“际会主频道” (@JHNBQQ), 9,864 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/JHNBQQ.

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.