✅花火担保•新增公群上押 公群编号:016 公群昵称:老姚直收色粉 Q群/天马 上押金额:5000U 公群老板: @laoyao677 公群链接: https://t.me/+12QAcB95pj9iZTI9 花火担保负责人: @hhdb 点击查询花火担保所有公群 禁止私下交易 无报备产生纠纷不予处理

Channel
花火担保•新开公群 @hhdb
@HHGQ999
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
1,769subscribers
-26 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001860757612 |
|---|---|
| Type | Channel |
| Username | @HHGQ999 |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 7 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 7 September 2026 |
| On Telegram | t.me/HHGQ999 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Sept 2026, 08:36 | 1,769 | -10 |
| 2 Sept 2026, 17:27 | 1,779 | -6 |
| 30 Aug 2026, 16:14 | 1,785 | -5 |
| 27 Aug 2026, 12:28 | 1,790 | +2 |
| 24 Aug 2026, 18:47 | 1,788 | -6 |
| 21 Aug 2026, 11:48 | 1,794 | -2 |
| 18 Aug 2026, 08:12 | 1,796 | -2 |
| 15 Aug 2026, 10:44 | 1,798 | +4 |
| 12 Aug 2026, 03:42 | 1,794 | +1 |
| 9 Aug 2026, 00:53 | 1,793 | -2 |
| 8 Aug 2026, 10:18 | 1,795 | first reading |
Engagement
20 posts held, back to 29 December 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 19 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
✅花火担保•新增公群上押 公群编号:009 公群昵称:炮王收粉 已押5000U 上押金额:5000U 公群老板: @P_W22 公群链接: https://t.me/+taBmxFpRAaVmNTU1 花火担保负责人: @hhdb 点击查询花火担保所有公群 禁止私下交易 无报备产生纠纷不予处理
✅花火担保•新增公群上押 公群编号:004 公群昵称:皇甫端收粉 已押5000U 上押金额:5000U 公群老板: @huanghu888 公群链接: https://t.me/+IX6lnsVrr0AzOTg0 花火担保负责人: @hhdb 点击查询花火担保所有公群 禁止私下交易 无报备产生纠纷不予处理
✅花火担保•新增公群上押 公群编号:016 公群昵称:热血收粉 已押5000U 上押金额:5000U 公群老板: @rexueAA 公群链接: https://t.me/+12QAcB95pj9iZTI9 花火担保负责人: @hhdb 点击查询花火担保所有公群 禁止私下交易 无报备产生纠纷不予处理
✅花火担保•新增公群上押 公群编号:019 公群昵称:鸭子直收全系粉 已押5000U 上押金额:5000U 公群老板: @yazibr 公群链接: https://t.me/+6YXU639nkkI1ODJl 花火担保负责人: @hhdb 点击查询花火担保所有公群 禁止私下交易 无报备产生纠纷不予处理
✅花火担保•新增公群上押 公群编号:017 公群昵称:虾海收全渠道粉 已押5000U 上押金额:5000U 公群老板: @OKJ777 @fczs2023 公群链接: https://t.me/+57fVHnC7yrAyYWVl 花火担保负责人: @hhdb 点击查询花火担保所有公群 禁止私下交易 无报备产生纠纷不予处理
✅花火担保•新增公群上押 公群编号:016 公群昵称:炮总直收色粉 已押5000U 上押金额:5000U 公群老板: @FM88666 公群链接: https://t.me/+WQynjgoLW_phMGU1 花火担保负责人: @hhdb 点击查询花火担保所有公群 禁止私下交易 无报备产生纠纷不予处理
✅花火担保•新增公群上押 公群编号:009 公群昵称:政亿集团收色粉 已押5000U 上押金额:5000U 公群老板: @lele6786788 公群链接: https://t.me/+J0WxuVG_xjxhNmVl 花火担保负责人: @hhdb 点击查询花火担保所有公群 禁止私下交易 无报备产生纠纷不予处理
✅花火担保•新增公群上押 公群编号:012 公群昵称:高山集团收色粉 已押5000U 上押金额:5000U 公群老板: @Fengshao1234 公群链接: https://t.me/+fOJWWxIyWIdkY2Yx 花火担保负责人: @hhdb 点击查询花火担保所有公群 禁止私下交易 无报备产生纠纷不予处理
✅花火担保•新增公群上押 公群编号:009 公群昵称:安信 一手盘直收粉 已押5000U 上押金额:5000U 公群老板: @anxin0987 公群链接: https://t.me/+iLC4swWNdrRmOGJl 花火担保负责人: @hhdb 点击查询花火担保所有公群 禁止私下交易 无报备产生纠纷不予处理
✅花火担保•新增公群上押 公群编号:088 公群昵称:赖师傅收粉 已押5000U 上押金额:5000U 公群老板: @LSF7777 公群链接: https://t.me/+G-zyCYm1pythZTk9 花火担保负责人: @hhdb 点击查询花火担保所有公群 禁止私下交易 无报备产生纠纷不予处理
✅花火担保•新增公群上押 公群编号:013 公群昵称:盛鑫集团直收 已押5000U 上押金额:5000U 公群老板: @SX985 公群链接: https://t.me/+UDdUuQjXarpjZDA1 花火担保负责人: @hhdb 点击查询花火担保所有公群 禁止私下交易 无报备产生纠纷不予处理
Showing the 12 most recent of 20 posts we hold for @HHGQ999. 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 1 registered channel — 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.
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.
Handles this channel named that no longer answer
- Dead references
- 5
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 5
- vacant every time we have ever looked
@HHGQ999 named 5 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
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.
“花火担保•新开公群 @hhdb” (@HHGQ999), 1,769 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/HHGQ999.
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.