Telegram RegisterThe public register of Telegram
Telegram profile photo for 海童Q上货频道

Channel

海童Q上货频道

@haitongqun

2 usernames

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

1,237subscribers

-10 since we began measuring on 17 August 2026

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

Register entry

Telegram ID-1001959099218
TypeChannel
Usernames@haitongqun @htvip
Description一手号商欢迎各位老板合作 售后问题可直接联系平台在线客服 1 联系飞机:@htqq 2 飞机群:@ooooooo 专注QQ十余载 感谢新老客户支持厚爱
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded17 August 2026
Last confirmed live3 October 2026
Measurements held12
On Telegramt.me/haitongqun

Topic

Hacking & security — 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 18 September 2026 and assigned it the closest of 31 fixed categories, at 87% 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

1,2301,2481,23917 August 2026 — 1,247 subscribers18 August 2026 — 1,248 subscribers21 August 2026 — 1,246 subscribers24 August 2026 — 1,245 subscribers27 August 2026 — 1,243 subscribers30 August 2026 — 1,242 subscribers2 September 2026 — 1,241 subscribers8 September 2026 — 1,235 subscribers12 September 2026 — 1,234 subscribers16 September 2026 — 1,230 subscribers1 October 2026 — 1,234 subscribers3 October 2026 — 1,237 subscribers1,23717 August 20263 October 2026
12 measurements spanning 47 days, net -10. 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 1,227–1,251 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Oct 2026, 18:221,237+3
1 Oct 2026, 12:391,234+4
16 Sept 2026, 03:561,230-4
12 Sept 2026, 15:411,234-1
8 Sept 2026, 07:161,235-6
2 Sept 2026, 21:271,241-1
30 Aug 2026, 21:241,242-1
27 Aug 2026, 22:281,243-2
24 Aug 2026, 20:541,245-1
21 Aug 2026, 09:281,246-2
18 Aug 2026, 06:221,248+1
17 Aug 2026, 20:151,247first reading

Engagement

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

ERR · 30 days
35.4%
avg views ÷ 1,237 subscribers
Avg views / post
438
15 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
15
of 35 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 3 October 2026
Posts held35 (21 July 2026 – 3 October 2026)
Views total6,568
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Oct 2026, 18: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

Photos
201
Links
26

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

Recent posts

3 Oct 2026, 14:47 UTC132 viewsread 3 October 2026

如到期需要续费的话 到期以后想续费多久 网站直接直接买你需要续费的天数的卡密就可以

3 Oct 2026, 14:43 UTC138 viewsread 3 October 2026
Photo

如出现扫码二维码失效的 点你的客服台里的复制链接 完事去网页打开就有个全新的二维码 在发给客户扫就可以了 生成的二维码有时效的 尽快让客户去扫

3 Oct 2026, 09:33 UTC218 viewsread 3 October 2026
Photo

网站新上AI微信登录网址 https://qaiic.com/ 具体操作和qq 一样方式

30 Sept 2026, 05:21 UTC504 viewsread 3 October 2026

网站新上注册卡密 价格上调,大家测试也都测试过了,时间按输入密钥开始计时 被加次数无限制,质量非常完美

30 Sept 2026, 03:29 UTC531 viewsread 3 October 2026
Photo

网站新上注册卡密 时间按输入密钥开始计时 价格给力 被加次数无限制

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

Mentions

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.

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

“海童Q上货频道” (@haitongqun), 1,237 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/haitongqun.

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.