Telegram RegisterThe public register of Telegram
Telegram profile photo for HKpayl印度支付源头l印度原生l印度代付l印度车队l印度承兑l海外支付

Channel

HKpayl印度支付源头l印度原生l印度代付l印度车队l印度承兑l海外支付

@HKPAYz

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

6,101subscribers

+900 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1003058950280
TypeChannel
Username@HKPAYz
CreatedBetween 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live18 November 2026
Measurements held28
Confirmed unchanged1 time, most recently 18 November 2026
On Telegramt.me/HKPAYz

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 12 September 2026 and assigned it the closest of 31 fixed categories, at 88% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Growth

2,8616,8454,8537 August 2026 — 5,201 subscribers7 August 2026 — 5,201 subscribers10 August 2026 — 5,196 subscribers14 August 2026 — 5,201 subscribers17 August 2026 — 5,207 subscribers20 August 2026 — 5,200 subscribers24 August 2026 — 5,354 subscribers27 August 2026 — 5,179 subscribers30 August 2026 — 4,670 subscribers2 September 2026 — 4,658 subscribers6 September 2026 — 4,665 subscribers11 September 2026 — 6,676 subscribers15 September 2026 — 6,654 subscribers19 September 2026 — 6,224 subscribers29 September 2026 — 5,950 subscribers6 October 2026 — 5,722 subscribers12 October 2026 — 2,985 subscribers16 October 2026 — 2,930 subscribers19 October 2026 — 2,861 subscribers22 October 2026 — 6,845 subscribers25 October 2026 — 6,764 subscribers28 October 2026 — 6,694 subscribers31 October 2026 — 6,607 subscribers2 November 2026 — 6,532 subscribers5 November 2026 — 6,487 subscribers9 November 2026 — 6,389 subscribers14 November 2026 — 6,259 subscribers18 November 2026 — 6,101 subscribers6,1017 August 202618 November 2026
28 measurements spanning 103 days, net +900. 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 2,263–7,443 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 28
Measured (UTC)SubscribersChange
18 Nov 2026, 22:016,101-158
14 Nov 2026, 01:516,259-130
9 Nov 2026, 01:316,389-98
5 Nov 2026, 14:196,487-45
2 Nov 2026, 20:006,532-75
31 Oct 2026, 00:066,607-87
28 Oct 2026, 05:486,694-70
25 Oct 2026, 15:016,764-81
22 Oct 2026, 20:086,845+3,984
19 Oct 2026, 13:062,861-69
16 Oct 2026, 02:212,930-55
12 Oct 2026, 20:382,985-2,737
6 Oct 2026, 09:585,722-228
29 Sept 2026, 09:385,950-274
19 Sept 2026, 12:576,224-430
15 Sept 2026, 04:366,654-22
11 Sept 2026, 17:176,676+2,011
6 Sept 2026, 19:024,665+7
2 Sept 2026, 06:494,658-12
30 Aug 2026, 02:454,670first reading

Engagement

30 posts held, back to 23 June 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 14 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
3.94%
avg views ÷ 6,101 subscribers
Avg views / post
241
6 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
6
of 30 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 5 November 2026
Posts held30 (23 June 2026 – 5 November 2026)
Views total1,443
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Nov 2026, 06:55 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
4s
Average length
2s

Measured directly from 2 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.

Reaction mix

11 reactions across 7 posts, in 2 distinct kinds. The most used accounts for 63.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤763.6%
👍436.4%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 8 of the 30 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 11 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 30 most recent posts we hold, published 23 June 2026 to 5 November 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

Telegram’s own ‘edited’ marker: 3 of 6 posts held from the last 30 days (50.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

5 Nov 2026, 19:57 UTC103 viewsread 7 November 2026
File

😀 RBL PAYOUT 05-11-2026 😀 1.1CR+ Account has been risk control by bank in half day, And 9,00,000 INR has been frozen, Else the result was around 2CR, if it has been used for full day Submit your account now. @HKPAYxx

4 Nov 2026, 16:09 UTC139 viewsread 7 November 2026
File

😀 RBL PAYOUT 04-11-2026 😀 93,00,000.00+ 😀 Company Accounts Required 😀 5-20M Volume every day 😀 DM: @HKPAYxx @HKPAYa

1 Nov 2026, 14:30 UTC250 viewsread 7 November 2026
Photo

✔️✔️✔️ A major scammer—Use fake USDT transaction screenshots to deceive people into handing over their funds. https://t.me/Jochih12398oop On verification deleted chat and blocked HKPAY representative. 🀄️🀄️🀄️🀄️🀄️ 😀😀😀

30 Oct 2026, 12:48 UTC269 viewsread 7 November 2026
Photo

DBS私户 ⚡️⚡️ ✔️额度 20W 😀 ✔️精聊 / 大区/资金盘/公检法 ✔️维护1+ 5+ 7+ ✔️单笔现存最低SGD 500- SGD1万 ✔️现存 / 网银 ( 同行网银单笔不超1999SGD) @SGD_HKPAY OCBC 私户⚡️⚡️ ✔️额度8万 😀 ✔️精聊 现存 ✔️单笔2000-20000SGD ❌不接公检法

27 Oct 2026, 18:25 UTC293 viewsread 7 November 2026
Video

新加坡GXS网银1w额度 精刷可来 --- 1000起 --- 😀😀

23 Oct 2026, 15:57 UTC389 viewsread 7 November 2026
File

⚡️⚡️⚡️⚡️⚡️ 😀 IOB + MQR 😀 4428823 INR 😀 @HKPAYxx @HKPAYa

22 Oct 2026, 14:09 UTC398 viewsread 7 November 2026

⚡️⚡️⚡️⚡️ 🀄️🀄️🀄️🀄️🀄️ 😀 😃 Stock fund receiving account : ( Company account ) 🔥 Axis Bank (OTP)😀 🔥 Indus (OTP) 🔥 BANDHAN corporate 🔥 Kotak-CMS 🔥 AU Corporate 🔥 CUB Corporate 🔥 Utkarsh Corporate 🔥 Unity Small finance Bank 🔥 CBI Corporate 😀 🔥 IDBI Bank 🔥 Fedral Bank 🔥 Saraswat CORPORATE 🔥 CSB Bank 😃 Payout account : ( Bulk upload ) 👉 Axis Bulk (Neo+Paypro)😀 👉 Jana small finance Bank 👉 SBM Corporate 👉 INDUS Bulk 👉 CB…

9 Oct 2026, 10:45 UTC487 viewsread 7 November 2026

⚡️⚡️⚡️⚡️ 🀄️🀄️🀄️🀄️🀄️ 😃 Stock Fund (Company Accounts) 😀 Axis Bank (OTP) 😀 Fedral Bank 😀 AU Corporate 😀 KOTAK+CMS 😀 Saraswat Bank 😀 Utkarsh Bank (UTK) 😀 Unity Small Finance Bank 😀 Central Bank of India 😀 CSB Bank 😀 IDBI Bank 😃 😀 HDFC 2ID (Domain) 😀 Bandhan CORPORATE 😀 Bank of Maharashtra 😀 City Union Bank (e-token) 😃OTP - F2F Work 😃F2f only available for special accounts 😃 Bulk-upload (Payout Accounts) 😀 IDFC First…

30 Sept 2026, 15:13 UTC605 viewsread 7 November 2026
File

😀Indus Bank (Payin) 😀 ₹83,00,000 😀 😀 We accept OTP transactions 😀 Processing time: 3–8 days. 😀 verify company official account 😀 Daily transaction volume is 5-20M 😀 DM: @HKPAYxx @HKPAYa

25 Sept 2026, 18:57 UTC959 viewsread 7 November 2026
Photo

😃😄😃😄😄 😀 😃 Indus PAYOUT (9.4 Million) 😄 Indus PAY-IN (4.9 Million) We need to process bulk payments from corporate accounts for game and stock funds. @HKPAYxx @HKPAYa 😀

24 Sept 2026, 16:41 UTC640 viewsread 7 November 2026
Photo

😃😄😃😄😄 🇸🇬 新加坡 🇸🇬 ⚡️⚡️⚡️⚡️ HSBC 私户 网银车⚡️⚡️ - 接精刷 7+ 3+ 料子 - 接一切网银1000起 - 可接 DBS / POSB DBS 私户 @SGD_HKPAY - 接精刷 7+ 3+ 料子 - 只接现存/插卡 ⚡️⚡️⚡️⚡️⚡️ 😀😀😀

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

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

“HKpayl印度支付源头l印度原生l印度代付l印度车队l印度承兑l海外支付” (@HKPAYz), 6,101 subscribers as measured 18 November 2026. Telegram Register, tgregister.com/channel/HKPAYz.

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.