Telegram RegisterThe public register of Telegram

Channel

HatPayNews (超级支付)

@HatPayHelp

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

16subscribers

+0 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1001679423551
TypeChannel
Username@HatPayHelp
Created31 August 2022measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held2
On Telegramt.me/HatPayHelp

Growth

168 August 2026 — 16 subscribers11 August 2026 — 16 subscribers8 August 202611 August 2026
2 measurements spanning 3 days. 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 15–17 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 22:3116no change
8 Aug 2026, 14:3016first reading

Engagement

14 posts held, back to 31 August 2022the 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 14 posts for this entry, the most recent from 5 September 2022. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
5
Videos
6
Links
1

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

Video runtime
2m 58s
Average length
30s

Measured directly from 6 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

5 Sept 2022, 11:31 UTC571 viewsread 11 August 2026
Photo

👍 使用 @HatPaybot 进行担保交易 - 资金全额托管到Bot,安全有保障 - 交易完成后由买家控制放行资金 - 交易完成后1天内可投诉卖家 - 交易可以分享到群里操作 - 目前不收任何手续费,方便快捷

5 Sept 2022, 10:54 UTC462 viewsread 11 August 2026
Video

@HatPayBot 钱包Bot支持发红包功能! 🧧 领完红包后,请去钱包Bot查看余额并提现。

5 Sept 2022, 10:45 UTC336 viewsread 11 August 2026
Video

⁉️ 如何向任意用户发送资金? 接收资金的用户无需提前开通钱包功能。 允许向个人用户、群组、频道发送资金,向群组和频道发送资金,谁先抢到就是谁的。 👉 钱包Bot @HatPayBot

5 Sept 2022, 10:11 UTC256 viewsread 11 August 2026
Video

⁉️ 如何转账? 跟着视频操作,视频中是使用的唯一链接,你还可以使用其他几种方法。 - 发送收款人的 @username - 转发一条收款人的消息到这里 - 点击📎图标,发送一个联系人 - 发送收款人的【钱包页面】->【账户ID】 👉 钱包Bot @HatPayBot

5 Sept 2022, 09:59 UTC224 viewsread 11 August 2026
Video

⁉️ 如何收钱? 请按照视频操作,最后把消息转发给你要收钱的人。 👉 钱包Bot @HatPayBot

5 Sept 2022, 09:55 UTC226 viewsread 11 August 2026
Video

⁉️ 如何提现? 请按照视频操作,以下切记: - 提币密码不要忘记,否则无法修改提币地址 - 提币需要审核,请耐心等待 - 提币有金额限制,要提额,请认证 👉 钱包Bot @HatPaybot

Showing the 12 most recent of 14 posts we hold for @HatPayHelp. 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 — 837,534 of 1,480,688entries 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.

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.

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

“HatPayNews (超级支付)” (@HatPayHelp), 16 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/HatPayHelp.

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.