Channel
@hd00000000001
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
5subscribers
+0 since we began measuring on 22 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002436782096 |
|---|---|
| Type | Channel |
| Username | @hd00000000001 |
| Description | 辉达第一人-亿人 |
| Created | 8 October 2024 — measured — dated from the channel’s first post |
| First recorded | 22 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/hd00000000001 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 11:31 | 5 | no change |
| 22 Aug 2026, 11:15 | 5 | first reading |
10 posts held, back to 8 October 2024 — 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 10 posts for this entry, the most recent from 18 January 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 22 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.
❤️亿人集团联系方式:【3个频道，5个飞机】❤️ 频道1：日常公布最新信息 @yirenjituan（时常更新） 频道2：亿人集团资料库 @yiren199 频道3：市场平台列表 @yiren1000 📣亿人一线： @yiren @yiren188 @yituandui（业务对接） 📣亿人二线： @yiren1314（细节沟通） 📣亿人三线： @yiren997 🔔内部吃瓜群: @yirenCG 📌全天在线 资金担保 代理扶持发展 📌量大合作者可安排出境办公 一站式全包
🌈 拉菲系列【发展 】🌈 🔺拉菲8风暴 1980+100+十日分红 详情 🔺拉菲9门徒 1990+50 +十日分红 详情 🔺拉菲10焦点 1980+60 +32%日红 详情 🔺拉菲11辉达 2000+50 +月分红 详情 🔥拉菲12益达 三种模式 A01 2000+40工资+50+月分红+占城10%（抽水） A02 1990+20工资+50+月分红+占城10%（不抽水） B03 1996+10工资+20+无分红+占城40%（不抽水）
拉菲系列第11个平台【辉达娱乐】 待遇 1900-2000 月结分红模式 实时结算工资 2000+50 实时工资+绩效工资 35+ 综合佣金100% 月分红 15%-25%，+10% 自由占成， 月结不累计 - 国内线路： https://888.hdna57.com https://888.hdcd89.com https://888.hdjw21.com https://888.hdks55.com https://888.hdnt32.com - 海外线路： https://666.hdef53.com https://666.hdvk27.com https://666.hdpc79.com https://666.hdls99.com https://666.hdka76.com 提供给您辉达电脑/手机通用网址： https://888.hdcd89.com 持续招商中，扶持有销量，有结构的…
#辉达娱乐
#辉达娱乐 国内线路： https://888.hdna57.com https://888.hdcd89.com https://888.hdjw21.com https://888.hdks55.com https://888.hdnt32.com - 海外线路： https://666.hdef53.com https://666.hdvk27.com https://666.hdpc79.com https://666.hdls99.com https://666.hdka76.com
❤️亿人集团联系方式:【3个频道，5个飞机】❤️ 频道1：日常公布最新信息 @yirenjituan（时常更新） 频道2：亿人集团资料库 @yiren199 频道3：市场平台列表 @yiren1000 📣亿人一线： @yiren @yiren188 @yituandui（业务对接） 📣亿人二线： @yiren1314（细节沟通） 📣亿人三线： @yiren997 🔔内部吃瓜群: @yirenCG 📌全天在线 资金担保 代理扶持发展 📌量大合作者可安排出境办公 一站式全包
❤️🔥 ❤️🔥 【 2024年最新平台甄选 】 ❤️🔥 ❤️🔥 ❤️🔥赢咖7极悦 1990+50 +十日分红 详情 ❤️🔥欧亿8星欧 1998+220+半月分红 详情 ❤️🔥拉菲11辉达 2000+50 +半月分红 详情 ❤️🔥恒行5 1990+45 +半月分红 详情 ❤️🔥新币 1960+100+30浮动 详情 🔥【2024年9月-12月即将开业平台】🔥 🧊🔥喜乐 1980+105 +25% 详情 🧊🔥天美3 1980+亏损佣金 详情 🧊🔥彩盈 1980+50+30浮动工资 详情 🧊🔥摩域2 1980+100+日红+半月红 详情 🧊🔥意昂3 1980+100 +半月分红 详情
❤️🔥【最安全-最靠谱-最火热平台甄选】❤️🔥 🔹赢咖系列【发展 】🔹 🧊赢咖5盛煌 1980+100+十日分红 详情 🧊赢咖6耀世 1980+90 +半月分红 详情 ❤️🔥赢咖7极悦 1990+50 +十日分红 详情 🔹 欧亿系列【发展】🔹 🧊欧亿6蓝狮 1990+65 +十日分红 详情 ❤️🔥欧亿7欧陆 1980+85 +半月分红 详情 ❤️🔥欧亿8星欧 1998+220+半月分红 详情 🔹 拉菲系列【发展】🔹 🧊拉菲9门徒 1990+50+十日分红 详情 ❤️🔥拉菲10焦点 1980+60+32%日红 详情 ❤️🔥拉菲11辉达 2000+50+半月分红 详情 🔹 天系列【发展】🔹 🧊富联 1980+85 +半月分红 详情 🧊万向 …
Channel photo updated
Channel created
Showing the 10 most recent of 10 posts we hold for @hd00000000001. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“辉达地址” (@hd00000000001), 5 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/hd00000000001.
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.