Channel
@jnhdbgq
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
29,605subscribers
-9,020 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003979492511 |
|---|---|
| Type | Channel |
| Usernames | @jnhdbgq @jnhgq0 |
| Created | Between 1 April 2026 and 19 April 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 53 |
| Confirmed unchanged | 1 time, most recently 8 September 2026 |
| On Telegram | t.me/jnhdbgq |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 10:59 | 29,605 | -2 |
| 8 Sept 2026, 07:56 | 29,607 | -416 |
| 5 Sept 2026, 03:38 | 30,023 | no change |
| 5 Sept 2026, 02:01 | 30,023 | -119 |
| 3 Sept 2026, 10:23 | 30,142 | -74 |
| 3 Sept 2026, 09:23 | 30,216 | -87 |
| 2 Sept 2026, 02:45 | 30,303 | -75 |
| 2 Sept 2026, 00:04 | 30,378 | -63 |
| 1 Sept 2026, 00:18 | 30,441 | -35 |
| 31 Aug 2026, 20:36 | 30,476 | -50 |
| 30 Aug 2026, 22:25 | 30,526 | no change |
| 30 Aug 2026, 19:27 | 30,526 | -180 |
| 29 Aug 2026, 23:34 | 30,706 | no change |
| 29 Aug 2026, 20:28 | 30,706 | -156 |
| 29 Aug 2026, 00:53 | 30,862 | -123 |
| 28 Aug 2026, 23:25 | 30,985 | -56 |
| 28 Aug 2026, 03:35 | 31,041 | no change |
| 28 Aug 2026, 02:57 | 31,041 | -5 |
| 27 Aug 2026, 04:29 | 31,046 | no change |
| 27 Aug 2026, 02:09 | 31,046 | first reading |
20 posts held, back to 19 April 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 60 pages 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 April 2026. An engagement rate over an empty window would be a number about nothing.
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.
🛍 【嘉年华担保】综合业务导航 1、游戏类 Pc28/哈希游戏/骰子快三 KK游戏 电子游戏 体育游戏 2、手机口 手机口 催收口接听口快手抖音口短信口 3、账号类 账号租赁1区 账号买卖 租苹果ID Zmpc 4、金流类 卡接码接 APP跑分 全国送现 5、承兑类 代收代付/承兑 TRX闪兑/能量租赁 6、代发类 视频代发评论 话术单代聊/后续代打I 短信代发 7、推广类 Q拉 V拉 支拉 收粉收量 地推贴纸类 苹果/微信im 8、买卖类 香烟酒水药品 三网卡流量卡 数据买卖 其他实物 9、服务类 苹果ID贷款 TG业务 天眼查档 接码注册 美工设计 账号解封类 外围裸聊 开发搭建 代实名 …
🛍🛍🛍🛍🛍🛍 嘉年华官方永久联系方式公示 ➖➖➖➖➖➖➖➖ 嘉年华客服 @jnhdbbot ➖➖➖➖➖➖➖➖ 嘉年华巡查（投诉） @jnhboss ➖➖➖➖➖➖➖➖ 嘉年华公群负责人 @jnhaaa ➖➖➖➖➖➖➖➖ 嘉年华专群负责人 @jnhccc ➖➖➖➖➖➖➖➖ 嘉年华仲裁负责人 @jnhboss ➖➖➖➖➖➖➖➖ 嘉年华官方频道 @jnhdb ➖➖➖➖➖➖➖➖ 嘉年华公群 @jnhdbgq ➖➖➖➖➖➖➖➖ 重要备注说明 1、以上述 群组、频道、人员、均属于嘉年华担保持有，认准认清，谨防冒充、如有被骗 本担保方不承担任何责任； 2、仔细核对我们的担保交易地址。 3、担保人员不会主动私聊以及发送地址和任何交易； 4、线下有需要实地考察我们的真实性，随时欢迎咨询我们担保工作人员提供线下网点； 5、辨别我们担保方真假小技巧，从频道切入，稍微仔细阅读，添加备注； ➖➖➖➖➖➖➖➖ 骗子常用伎俩 🛍抄袭使用官方头像、昵称、…
🛍 嘉年华担保-待编辑 温馨提示：进群后注意区分真假公群管理员，谨防骗子冒充！只对公群经营的业务做担保，切勿私下进行其他业务。公群内进行业务请遵守公群规则！公群对接业务前请认真阅读 - 公群规则以及注意事项
🛍 嘉年华担保-待编辑 温馨提示：进群后注意区分真假公群管理员，谨防骗子冒充！只对公群经营的业务做担保，切勿私下进行其他业务。公群内进行业务请遵守公群规则！公群对接业务前请认真阅读 - 公群规则以及注意事项
🚫🚫🚫温馨提醒： 无论你是玩飞机的小白还是刚毕业的学生，还是其他无业游民，请不要相信任何私聊，不要相信任何招聘广告信息！不要相信任何要帮你找工作的任何人！你想要别人的钱就要小心别人要你的命! ⚠️⚠️⚠️君子爱才取之有道！我们始终坚守底线，很多涉及人口买卖业务或者人头公群出国劳务业务我们一律不接！点到为止，一切信息真假自行分辨！且行且珍惜！ 📌任何业务需要协助请找：@jnhboss
🛍 嘉年华担保-待编辑 温馨提示：进群后注意区分真假公群管理员，谨防骗子冒充！只对公群经营的业务做担保，切勿私下进行其他业务。公群内进行业务请遵守公群规则！公群对接业务前请认真阅读 - 公群规则以及注意事项
🛍 嘉年华担保-待编辑 温馨提示：进群后注意区分真假公群管理员，谨防骗子冒充！只对公群经营的业务做担保，切勿私下进行其他业务。公群内进行业务请遵守公群规则！公群对接业务前请认真阅读 - 公群规则以及注意事项
🛍 嘉年华担保-待编辑 温馨提示：进群后注意区分真假公群管理员，谨防骗子冒充！只对公群经营的业务做担保，切勿私下进行其他业务。公群内进行业务请遵守公群规则！公群对接业务前请认真阅读 - 公群规则以及注意事项
🛍 嘉年华担保-待编辑 温馨提示：进群后注意区分真假公群管理员，谨防骗子冒充！只对公群经营的业务做担保，切勿私下进行其他业务。公群内进行业务请遵守公群规则！公群对接业务前请认真阅读 - 公群规则以及注意事项
🛍 嘉年华担保-待编辑 温馨提示：进群后注意区分真假公群管理员，谨防骗子冒充！只对公群经营的业务做担保，切勿私下进行其他业务。公群内进行业务请遵守公群规则！公群对接业务前请认真阅读 - 公群规则以及注意事项
🛍 嘉年华担保-全国送现 温馨提示：进群后注意区分真假公群管理员，谨防骗子冒充！只对公群经营的业务做担保，切勿私下进行其他业务。公群内进行业务请遵守公群规则！公群对接业务前请认真阅读 - 公群规则以及注意事项
🛍 嘉年华担保-解封类点号类 温馨提示：进群后注意区分真假公群管理员，谨防骗子冒充！只对公群经营的业务做担保，切勿私下进行其他业务。公群内进行业务请遵守公群规则！公群对接业务前请认真阅读 - 公群规则以及注意事项
Showing the 12 most recent of 20 posts we hold for @jnhdbgq. 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.
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.
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 8 September 2026 — this entry's latest reading, not the date you are reading this.
“嘉年华担保|公群导航” (@jnhdbgq), 29,605 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/jnhdbgq.
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.