Channel

体育竞技💎赛事-播报💎Official Channel

@jldca

3 usernames

On this record: Previous handles · Growth · Engagement · Posts · Citations · Cite this entry

109subscribers

-3 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	-1002623463112
Type	Channel
Usernames	@dh_hhhhhh @dh_hhhhhhh @dh_hhhhhhhh
Created	Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded	9 August 2026
Last confirmed live	5 September 2026
Measurements held	7
Confirmed unchanged	1 time, most recently 5 September 2026
On Telegram	t.me/jldca

Previous handles

@jldca was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@jldca
held 9 August 2026 – 9 August 2026

Growth

7 measurements spanning 29 days, net -3. 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 13–125 and does not start at zero.

Measurement log — every subscribers count we have recorded
Measured (UTC)	Subscribers	Change
5 Sept 2026, 01:42	109	+83
4 Sept 2026, 10:21	26	-85
29 Aug 2026, 04:58	111	+85
27 Aug 2026, 20:03	26	-1
27 Aug 2026, 04:11	27	-85
9 Aug 2026, 06:32	112	no change
7 Aug 2026, 03:16	112	first reading

Engagement

20 posts held, back to 29 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 4 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 8 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

8 Aug 2026, 18:24 UTC2 viewsread 9 August 2026

Photo

#群组推荐 #群组互推 #相似推荐 🚀东皇集团“飞机导航”生态引领增长🌟 携手 @jpzxgo 最大化价值。⭐️ ⁣东皇担保专业铸就底气严选团队 👇以下博彩品牌均由： #海外担保 #东皇担保 #金山集团 #金米集团 #金宝集团 #西港集团 #东南亚集团 #诺亚集团 #联盛集团 #世博联盟 #OK担保 #PC担保 #天成担保 #铂莱国际 #东皇集团等各大知名企业联合为其娱乐品牌担保 #大额无忧 #放心娱乐 🏆 金宝娱乐城 · USDT入款 · RMB盘官方网站： https://jbylc520.com 🏆 西港娱乐城 · USDT入款 · RMB盘官方网站： https://xgylc888.com 🏆 金米娱乐城 · USDT入款 · 美金1:1 官方网站： https://jinmi158.com 🏆 金宝娱乐城 · USDT入款 · RMB盘官方网站： https://jbylc…

8 Aug 2026, 03:23 UTC6 viewsread 9 August 2026

Photo

7 Aug 2026, 12:23 UTC10 viewsread 9 August 2026

Photo

6 Aug 2026, 21:23 UTC7 viewsread 9 August 2026

Photo

6 Aug 2026, 16:56 UTCviews —

体育竞技💎赛事-播报💎Official Channel pinned Deleted message

6 Aug 2026, 06:23 UTC4 viewsread 9 August 2026

Photo

⁣东皇担保专业铸就底气严选团队 👇以下博彩品牌均由： #海外担保 #东皇担保 #金山集团 #金米集团 #金宝集团 #西港集团 #东南亚集团 #诺亚集团 #联盛集团 #世博联盟 #OK担保 #PC担保 #天成担保 #币安担保等各大知名企业联合为其娱乐品牌担保 #大额无忧 #放心娱乐 🏆 金宝娱乐城 · USDT入款 · RMB盘官方网站： https://jbylc520.com 🏆 西港娱乐城 · USDT入款 · RMB盘官方网站： https://xgylc888.com 🏆 金米娱乐城 · USDT入款 · 美金1:1 官方网站： https://jinmi158.com 🏆 沙龙会飞投 · USDT入款· 美金1:1 官方网站： https://t.me/SLHYL_bot?start=yaHpdB 🏆 西港娱乐城 · USDT入款 · RMB盘官…

5 Aug 2026, 15:23 UTC4 viewsread 9 August 2026

Photo

5 Aug 2026, 00:23 UTC5 viewsread 9 August 2026

Photo

4 Aug 2026, 09:23 UTC5 viewsread 9 August 2026

Photo

3 Aug 2026, 18:23 UTC5 viewsread 9 August 2026

Photo

3 Aug 2026, 05:48 UTCviews —

体育竞技💎赛事-播报💎Official Channel pinned Deleted message

3 Aug 2026, 03:23 UTC4 viewsread 9 August 2026

Photo

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

东皇日记 🎱极光导航⛳️@DongHuangDaoHang⛳️搜索引擎🎱Official Channel
@Emoji139 · 2823 posts

Names

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

东皇担保｜@DongHuangDanBao｜公信背书｜Official Channel
@Emoji119 · 28417 posts 宣传海报、广告/Banner动、动态/静态头像、LOGO设计 @PG99PG
@jpztn · 2817 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.

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

“体育竞技💎赛事-播报💎Official Channel” (@jldca), 109 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/jldca.

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.