Channel
@HpayFan
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
5subscribers
+0 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001772918530 |
|---|---|
| Type | Channel |
| Username | @HpayFan |
| Description | We are a fan organized decentralized advocacy organization for Himalaya Pay, Himalaya Dollar, Himalaya Coin, and Himalaya Exchange . https://hpay.info |
| Created | Between 1 December 2021 and 3 January 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 2 |
| On Telegram | t.me/HpayFan |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 04:01 | 5 | no change |
| 12 Aug 2026, 07:47 | 5 | first reading |
20 posts held, back to 3 January 2023 — 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 20 posts for this entry, the most recent from 14 February 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 13 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.
Measured directly from 7 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.
🦠 The Origin Tracing of the Cov19 Virus 🔗 [Read More](https://paymap.org/n) The origin of the Cov19 virus remains a global concern. Discover the latest research, evidence, and perspectives on its true origins. Click the link to learn more and join the discussion! 🛡️ What You Need to Know About Cov19 🔗 [Read More](https://paymap.org/3) Essential insights on Cov19, including its origins, risks, and potential solutio…
Signed PayMap.org
Hpay.info pinned «Himalaya Exchange Fan Community 📢 Join our Telegram Groups: • English 👉 HpayFan • Chinese 👉 HpayNews 🌐 Official Websites: • Chinese: hpay.news • English: hpay.info We are a decentralized fan community (DAO) supporting Himalaya Exchange and its ecosystem…»
Himalaya Exchange Fan Community 📢 Join our Telegram Groups: • English 👉 HpayFan • Chinese 👉 HpayNews 🌐 Official Websites: • Chinese: hpay.news • English: hpay.info We are a decentralized fan community (DAO) supporting Himalaya Exchange and its ecosystem, including Himalaya Pay, Himalaya Dollar (HDO), and Himalaya Coin (HCN). This is a fan-driven initiative and not an official communication channel of Himalaya …
Signed PayMap.org
4月11日 周二 Reddit分享交流会内容 过去Reddit团队在45天中，取得了近一亿的总流量。本次我们邀请到在Reddit团队工作中的组员，为大家分享经验，欢迎大家参加。 会议主持：红山 1.白菜小哥 币圈新闻解读 10分钟 2.Reddit推广团队 经验分享 30分钟 海賊王7 mins 野猫 6-7 mins 子兵 6-7 mins Chinadoll 6-7 mins 3.无线礼服招募组员 5分钟 4.分享讨论 30分钟 美东时间：上午10：00～11:15 盘古时间：晚上10:00～11:15 土耳其时间：下午5:00～6:15 会议链接 ：https://discord.gg/r2rbBds4Xp 说明：如果您是新加入战友，请在新人报道区新人报到区 留言申请加Reddit 身份标签…
Signed 商业组 Dafei (大飞)#6760
今日《币圈新闻解读》，将在稍后1小时，由 白菜🥬小哥 为您在盖特HPAYinfo频道 直播呈现。 新闻稿，详见👇Gnews 文章 https://gnews.org/threads/1085305
Signed 商业组 Dafei (大飞)#6760
联盟HPAY推广平台 Reddit推广团队分享交流会 美国纽约时间，每周二、周四 上午10点，在盖特hpayinfo频道直播推流！ 加入联盟HPAY推广平台Reddit推广团队： https ://linktr.ee/hpayinfo 盖特同步直播频道：https://gettr.com/user/hpayinfo
Signed 商业组 Dafei (大飞)#6760
https://youtu.be/_dYIDtO1zbg
Signed 商业组 Dafei (大飞)#6760
https://youtu.be/MTtNSuK6oq0
Signed 商业组 Dafei (大飞)#6760
The future digital currency exchanges must fulfill three immediate requests to ensure the safety of digital assets 1. to find a third-party to hold its customer’s funds; 2. to implement blockchain-based audit 3. to store digital asset data in satellites https://gettr.com/post/p23xv6of6fd
Signed 商业组 Dafei (大飞)#6760
https://gnews.org/articles/762820
Signed 商业组 Dafei (大飞)#6760
https://gnews.org/articles/599887?biz=75865542&eu=54367826&t=AxXUpir&gref=
Signed 商业组 Dafei (大飞)#6760
https://gnews.org/articles/622395?biz=75865542&eu=54367826&t=Sg2qkEJ&gref=
Signed 商业组 Dafei (大飞)#6760
Showing the 12 most recent of 20 posts we hold for @HpayFan. 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.
@HpayFan 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.
References a handle that is not a live channel — we have no record it ever was one.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“Hpay.info” (@HpayFan), 5 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/HpayFan.
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.