Channel

【聚鼎娱乐官网】真人视讯｜电子｜棋牌｜捕鱼｜体育｜彩票

@Hmdbgx

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

284subscribers

+8 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID	-1002662669408
Type	Channel
Username	@Hmdbgx
Created	Between 1 March 2025 and 6 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded	8 August 2026
Last confirmed live	14 August 2026
Measurements held	4
Confirmed unchanged	1 time, most recently 14 August 2026
On Telegram	t.me/Hmdbgx

Growth

4 measurements spanning 7 days, net +8. 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 275–285 and does not start at zero.

Measurement log — every subscribers count we have recorded
Measured (UTC)	Subscribers	Change
14 Aug 2026, 17:07	284	+7
8 Aug 2026, 08:35	277	no change
7 Aug 2026, 14:14	277	+1
7 Aug 2026, 10:35	276	first reading

Engagement

20 posts held, back to 6 July 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 pageof 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 12 April 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime: 1m 33s
Average length: 31s

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.

Recent posts

12 Apr 2026, 21:45 UTC221 viewsread 8 August 2026

Photo

天子德利全面升级为「聚鼎娱乐」全新平台 · 更高待遇 · 更优福利诚邀加入，共创巅峰！聚鼎娱乐官方客服：https://t.me/jdkf666666 聚鼎娱乐官方网址：https://www.jd666.vip 聚鼎娱乐备用网址：https://www.jd222.vip

4 Aug 2025, 08:59 UTC866 views0 reactionsread 8 August 2026

Video

🎉《新人充值活动详情》🎉 首充就送 · 自动到账 · 拿到手软 💰充值金额 🎁赠送彩金 📜提现要求 200 元 38 元 3 倍流水 500 元 108 元 3 倍流水 1000 元 188 元 3 倍流水 2000 元 288 元 3 倍流水 5000 元 588 元 3 倍流水 10000 元 1288 元 3 倍流水 30000 元 2188 元 3 倍流水 50000 元 5188 元 3 倍流水 100000 元 10888 元 3 倍流水 🔥【额外福利】 ☑️ 充值每一笔额外再送 3%，不限次数，充得越多送得越多！ ☑️ 洗码双边1.0倍，全程高返！ ☑️ 负盈利回馈高达20%起，玩得越猛，回得越多！ 🏆 平台名称：天子德利综合娱乐 🎯 安全稳定 · 秒充秒提 · 福利拉满！ 📲 立即加入，天天送钱！ 😅 天子官网商务合作洽谈：@tzzsb888 😆 24小时在…

1 Aug 2025, 03:55 UTC653 viewsread 8 August 2026

Photo

28 Jul 2025, 07:14 UTC422 viewsread 8 August 2026

Photo

27 Jul 2025, 06:35 UTC311 viewsread 8 August 2026

Photo

26 Jul 2025, 06:34 UTC235 viewsread 8 August 2026

Photo

24 Jul 2025, 11:15 UTC172 viewsread 8 August 2026

Photo

23 Jul 2025, 12:32 UTC143 viewsread 8 August 2026

Photo

22 Jul 2025, 09:12 UTC113 viewsread 8 August 2026

Photo

18 Jul 2025, 12:06 UTC120 viewsread 8 August 2026

Photo

16 Jul 2025, 03:10 UTC108 viewsread 8 August 2026

Photo

14 Jul 2025, 10:58 UTC91 viewsread 8 August 2026

Photo

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

Names

Channels on the register whose handles appear in this channel's posts.

缅甸佤邦小勐拉老街博彩频道
@tz16899 · 2719 posts 新世界客服新世界APP
@tzzsb888 · 819 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: 1; 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: 1; vacant every time we have ever looked

@Hmdbgx named 1 handle 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.

@tzcr999
named in 19 posts, 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 14 August 2026 — this entry's latest reading, not the date you are reading this.

“【聚鼎娱乐官网】真人视讯｜电子｜棋牌｜捕鱼｜体育｜彩票” (@Hmdbgx), 284 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/Hmdbgx.

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.