Channel

🇮🇳印度UPI|印度PTM|印度卡卡|

@PAYTM_XDpay

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

231subscribers

+8 since we began measuring on 7 August 2026

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

Register entry

Telegram ID	-1001245753334
Type	Channel
Username	@PAYTM_XDpay
Created	Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded	8 August 2026
Last confirmed live	13 October 2026
Measurements held	9
Confirmed unchanged	1 time, most recently 13 October 2026
On Telegram	t.me/PAYTM_XDpay

Topic

Hacking & security — 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 23 September 2026 and assigned it the closest of 31 fixed categories, at 34% 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 why it has no browse page of its own yet.

Growth

9 measurements spanning 67 days, net +8. 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 218–233 and does not start at zero.

Measurement log — every subscribers count we have recorded
Measured (UTC)	Subscribers	Change
13 Oct 2026, 01:38	231	+1
1 Oct 2026, 20:20	230	+1
18 Sept 2026, 04:57	229	+3
9 Sept 2026, 13:58	226	-1
31 Aug 2026, 19:36	227	+4
24 Aug 2026, 05:13	223	+3
16 Aug 2026, 06:23	220	-3
8 Aug 2026, 10:31	223	no change
7 Aug 2026, 09:49	223	first reading

Engagement

20 posts held, back to 28 March 2025 — 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 2 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

59 reactions across 18 posts, in 5 distinct kinds. The most used accounts for 40.7% of them.

Every reaction kind recorded on the sample, most used first
Reaction	Count	Share
❤	24	40.7%
🔥	18	30.5%
👍	9	15.3%
🤝	7	11.9%
👏	1	1.69%

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 18 of the 20 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 59 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 28 March 2025 to 2 August 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

2 Aug 2026, 10:11 UTC69 views3 reactionsread 8 August 2026

🇮🇳六年支付公司🌎值得信赖 ✅原生唤醒跑分承接：游戏、综合盘、棋牌、Rummy、外汇 ✅线下卡卡承接：股票、精聊、外汇 ✅24小时代收代付 ✅稳定通道，费率冰点，D0结算，24H随时下发。 ❤️全网最稳定通道 24小时代收无限额度 24小时代付公司频道 @PAYTM_XDpay 商务咨询 @xdpay_2 @xdpay22

❤1🔥1🤝1

5 Nov 2025, 01:22 UTC984 views4 reactionsread 8 August 2026

🇮🇳印度🔥 PTM全唤醒+upi转账代收接一二类产品♥️ ✅原生全唤醒+UPI转账 24小时稳定代收代付 🔥新盘支持小户扶持 🔥尾盘提供专门盖盘户 ❤️全网最稳定通道 24小时代收无限额度 24小时代付 ✅印度线下卡接回U，接全行业，专业 🔥线下UPI 🔥线下UPI 🔥线下UPI ✅印度线下卡卡每天都会有大额户公户🔥 ✅单笔100万起安全性高🔥 可接大区料 ✅大额户不会群发需要喊卡哦🔥 ✅有线下卡卡专户供应♥️ ✅❤️另增加线下卡卡❤️进就算线下卡（到账就上分）❤️ 🔥大区股转来量❤️ ✅印度🔥进算卡 🟢进算卡2000起会群发。 🟢到账就算无视料子精聊刷单公检法 🟢入算卡接额度有限先到先得 🟢查账快上分快 🟢储蓄，活期都有 🟢大额10万起可以报备拿其它卡哦 ⚠️进算卡尽量维护当天。公司频道 @PAYTM_XDpay 商务咨询 @xdpay_2 @xdpay22

❤2👏1🔥1

26 Oct 2025, 01:56 UTC800 views3 reactionsread 8 August 2026

❤1👍1🔥1

15 Oct 2025, 01:59 UTC612 views3 reactionsread 8 August 2026

❤1👍1🔥1

10 Oct 2025, 03:06 UTC489 views4 reactionsread 8 August 2026

❤2👍1🔥1

1 Oct 2025, 16:17 UTC394 views6 reactionsread 8 August 2026

❤3🔥2👍1

7 Sept 2025, 08:53 UTC409 views3 reactionsread 8 August 2026

❤1👍1🔥1

2 Sept 2025, 05:01 UTC347 views3 reactionsread 8 August 2026

❤1👍1🔥1

11 Aug 2025, 02:39 UTC374 views3 reactionsread 8 August 2026

❤1👍1🔥1

1 Jul 2025, 03:02 UTC415 views5 reactionsread 8 August 2026

❤3👍1🔥1

9 Jun 2025, 09:09 UTC402 views3 reactionsread 8 August 2026

❤1🔥1🤝1

26 May 2025, 02:25 UTC395 views3 reactionsread 8 August 2026

❤1🔥1🤝1

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

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

🇮🇳 印度支付xdpay
@xdpay6 · 91 post

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.

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.

🇮🇳 印度支付xdpay
@xdpay6 · 95 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 13 October 2026 — this entry's latest reading, not the date you are reading this.

“🇮🇳印度UPI|印度PTM|印度卡卡|” (@PAYTM_XDpay), 231 subscribers as measured 13 October 2026. Telegram Register, tgregister.com/channel/PAYTM_XDpay.

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.