Telegram RegisterThe public register of Telegram

Channel

护盾数据 @hudun

@hudun

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

54subscribers

-2 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1003280569015
TypeChannel
Username@hudun
Description一手源头,海内外数据
Created6 January 2026measured — dated from the channel’s first post
First recorded10 August 2026
Last confirmed live10 August 2026
Measurements held3
On Telegramt.me/hudun

Growth

5456559 Aug 2026, 21:45 — 56 subscribers10 Aug 2026, 04:18 — 54 subscribers10 Aug 2026, 09:15 — 54 subscribers9 Aug 2026, 21:4510 Aug 2026, 09:15
3 measurements taken within a single day, net -2. 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 54–56 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 09:1554no change
10 Aug 2026, 04:1854-2
9 Aug 2026, 21:4556first reading

Engagement

13 posts held, back to 6 January 2026the 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 13 posts for this entry, the most recent from 16 February 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
6
Links
1

Lifetime counters from Telegram’s own channel header, read 10 August 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

16 Feb 2026, 05:14 UTC172 viewsread 10 August 2026

除夕到,福气绕,祝大家新的一年,钱袋鼓鼓,烦恼少少,身体棒棒,日子红红,马年大吉,万事胜意!祝各位老板除夕快乐!新年快乐!

31 Jan 2026, 13:30 UTC262 viewsread 10 August 2026

新年将至,提前进入半休息状态,有事没回复的留言就行,看到会第一时间回复!

28 Jan 2026, 08:07 UTC279 viewsread 10 August 2026

慧妍8888U,天鼎9999U!直接给权限!年前最后一波股票!各位老板把握机会! 欢迎咨询:@baoluo 售后联系:@huofo

24 Jan 2026, 14:19 UTC295 viewsread 10 August 2026

美股拿下!懂的来!支持埋雷! https://www.webull.com/ 欢迎咨询: @baoluo 售后联系: @huofo

18 Jan 2026, 15:26 UTC319 viewsread 10 August 2026

慧妍投顾,打包权限8888U带走!支持埋雷验证!3天内交付! 欢迎咨询:@baoluo 售后联系:@huofo

18 Jan 2026, 15:23 UTC192 viewsread 10 August 2026
Photo

成功打趴一个资金盘!打到他无能为力,发公告求助!接任何行业的ddos攻击! 拿人钱财,替人消灾。——六哥

18 Jan 2026, 15:22 UTC169 viewsread 10 August 2026
Photo

股票-天鼎 从今天起,送10天福利!老客户每人每天送10000条!新客户每天每人领2000条测试!共计送出88万条!送完即止!送的料子全部保一手料!欢迎各大盘口/中介洽谈合作! 欢迎咨询: @baoluo 售后联系: @huofo

18 Jan 2026, 15:20 UTC140 viewsread 10 August 2026
Photo

ddos开工中!8.00起床开工,主打一个敬业!有敌对网站的发过来打!同行业最低价!主打一个靠谱! 欢迎咨询: @baoluo 售后联系: @huofo

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

Citation-graph rank

Citation-graph rank — 780,476 of 1,350,102entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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.

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

“护盾数据 @hudun” (@hudun), 54 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/hudun.

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.