Telegram RegisterThe public register of Telegram
Telegram profile photo for INRpay (五年老牌支付公司)

Channel

INRpay (五年老牌支付公司)

@GenesisPay001

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

130subscribers

-8 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1001967533471
TypeChannel
Username@GenesisPay001
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live11 November 2026
Measurements held11
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/GenesisPay001

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 26 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 2 other registered channels. This entry also sits inside a group of 3 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@GenesisPayEnglish/10623 Jul 2025, 12:12 UTC@GenesisPay001/481 · this entry23 Jul 2025, 12:12 UTC1.00under a minute
@GenesisPay001/483 · this entry14 Aug 2025, 04:22 UTC@GenesisPayEnglish/10714 Aug 2025, 04:22 UTC1.00under a minute
@GenesisPay001/486 · this entry6 Sept 2025, 07:06 UTC@GenesisPayEnglish/1086 Sept 2025, 07:06 UTC1.00under a minute
@GenesisPay001/488 · this entry17 Sept 2025, 01:30 UTC@GenesisPayEnglish/10917 Sept 2025, 01:30 UTC1.00under a minute
@GenesisPayEnglish/11010 Oct 2025, 04:58 UTC@GenesisPay001/490 · this entry10 Oct 2025, 04:58 UTC1.00under a minute
@GenesisPay001/493 · this entry29 Nov 2025, 06:10 UTC@GenesisPayEnglish/11129 Nov 2025, 06:10 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@GenesisPayEnglish8 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (6–2)
@GenesisPay78 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (6–2)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 4 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 18 comparable posts for this entry, running 23 July 2025 to 22 April 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 3 channels, the one whose matching posts we hold earliest is @GenesisPayEnglish. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 3 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

1301381349 August 2026 — 138 subscribers10 August 2026 — 138 subscribers17 August 2026 — 137 subscribers1 September 2026 — 136 subscribers10 September 2026 — 135 subscribers18 September 2026 — 134 subscribers2 October 2026 — 132 subscribers13 October 2026 — 131 subscribers19 October 2026 — 130 subscribers26 October 2026 — 131 subscribers11 November 2026 — 130 subscribers9 August 202611 November 2026
11 measurements spanning 94 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 129–139 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Nov 2026, 09:16130-1
26 Oct 2026, 19:17131+1
19 Oct 2026, 16:35130-1
13 Oct 2026, 08:39131-1
2 Oct 2026, 21:14132-2
18 Sept 2026, 08:18134-1
10 Sept 2026, 19:35135-1
1 Sept 2026, 16:35136-1
17 Aug 2026, 16:05137-1
10 Aug 2026, 05:36138no change
9 Aug 2026, 07:47138first reading

Engagement

20 posts held, back to 8 July 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 22 April 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

22 Apr 2026, 09:38 UTCviews —

The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 27 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.

9 Apr 2026, 14:05 UTC134 views0 reactionsread 9 August 2026

enesisPay Important Notice: ✅Game list: 🔥RBL corporate+ MQR 🔥Boi corporate + MQR 🔥J&k bank + MQR 🔥IDBI CORPORATE/retail New +MQR 🔥TMB + MQR 🔥KGB + MQR 🔥SIB + MQR 🔥TJSB + MQR 🔥Equitas 2id+ MQR 🔥KARNATAKA KBL ONE/retail +MQR 🔥DHANLAXMI RETAIL/CORPORATE+MQR 🔥BOM RETAIL/CORPORATE+MQR 🔥Indian bank + MQR 🔥Apgb bank + MQR 🔥Uco bank + MQR ==================================== ✅MIX: ☀️indus with bulk ☀️RBL corporate…

26 Dec 2025, 09:13 UTC175 viewsread 9 August 2026
Photo

印度原生通道24小时收付款!成功率稳定50%-70%%!额度无限!D0结算! 印度原生通道24小时收付款!成功率稳定50%-70%!额度无限!D0结算! 印度原生通道24小时收付款!成功率稳定50%-70%!额度无限!D0结算! 频道链接:https://t.me/FuturePayin

19 Dec 2025, 10:56 UTC183 viewsread 9 August 2026

印度大区有户的来!不缺量!axis indus 优先!可保量1000-20000万的户! 印度大区有户的来!不缺量!axis indus 优先!可保量1000-20000万的户! 印度大区有户的来!不缺量!axis indus 优先!可保量1000-20000万的户! 联系人:@indianbank03

11 Dec 2025, 08:01 UTC180 viewsread 9 August 2026

印度原生当前额度充足!成功率70% D0结算! 印度原生当前额度充足!成功率70% D0结算! 联系人:@indianbank03

5 Dec 2025, 06:16 UTC201 viewsread 9 August 2026

enesisPay Important Notice: ✅Game list: ✅SBI Witch CMP (MQR) ✅SBI Witch e-service (MQR) ✅J&amp;amp;K company account ✅IOB personal (retail)+ MQR ✅KVB Corporate Account (New) + MQR ✅TJSB Bank (New) + MQR ✅RBL Corporate + Retail+ MQR ==================================== 🔥The accounts required for mixed payment are as follows: 40L-80L can be run per day ✅Axis bank NEO for Corporation ✅Axis bank Corporati…

29 Nov 2025, 06:10 UTC135 viewsread 9 August 2026

enesisPay Important Notice: ✅SBI Witch CMP (MQR) ✅SBI Witch e-service (MQR) ✅J&amp;amp;K company account ✅IOB personal (retail)+ MQR ✅KVB Corporate Account (New) + MQR ✅TJSB Bank (New) + MQR ✅RBL Corporate + Retail+ MQR ==================================== 🔥The accounts required for mixed payment are as follows: 40L-80L can be run per day ✅Axis bank NEO for Corporation ✅Axis bank Corporation 2ID (Batc…

17 Nov 2025, 03:59 UTC144 viewsread 9 August 2026

GenesisPay印度通知: ✅二类拼车发车中 超低价格 需维护期7+ ✅一类跑分个人码代收付全天正常!限额200-50000 欢迎进单! ✅二类承兑开机! 欢迎报单!额度充足!IMPS/RTGS/NEFT 均有单子 🤝长期招募:印度公司账户!印度网关账户!以及印度承兑!资金类型为:游戏 股票 快杀! 👉 合作洽谈: @inrpay003

17 Oct 2025, 11:46 UTC196 viewsread 9 August 2026

印度三方系统出租 稳定出租,系统 · 全球通道技术支持 专为第三方支付系统提供高效稳定解决方案,支持唤醒 复制转帐 原生 线下卡接通道使用! 技术就是实力!6年资深团队,专注灰产、高并发场景下的系统部署与运维。 💻 全手码开发,纯净架构,零套件依赖,稳定率高达99.99%。 开发主要包括适配银行流水 插件 收款页面更新 Telegram自动查单补单机器人 技术团队24小时在线服务! 有需要的可以联系看测试网站效果 @GenesisPayin

10 Oct 2025, 04:58 UTC188 views0 reactionsread 9 August 2026

enesisPay Important Notice: Gaming funds require a large number of SBI 3ID-CMP accounts! Daily running of the account can guarantee a minimum of 5cr Gaming funds require a large number of SBI 3ID-CMP accounts! Daily running of the account can guarantee a minimum of 5cr ✅SBI Witch CMP (MQR) 5cr-10cr💰 ✅SBI Witch e-service (MQR) 5cr-10cr💰 ✅J&amp;amp;amp;K company account ✅IOB personal (retail)+ MQR =============…

17 Sept 2025, 01:30 UTCviews —

GenesisPay(创世纪支付) pinned «Genesis Payment:一类唤醒+扫码规则如下: 1.工作时间:7X24小时,不间断! 2.代收方式:24小时跑分upi轮巡 提醒客户不要保存支付,保存支付的订单不一定到账,只能配合商户尽量24小时内追回 3.代付方式:公户代付+ upi 代付(upi代付仅支持整数订单) 4.代收单笔额度:100~30000卢比 5.代付单笔额度:100~100000卢比(upi代付1000-10000出款较快)。 注意!单笔通道率收取不能到(12)的订单,按(12)收取 6.商户承接类型:目前只接一类信…»

17 Sept 2025, 01:30 UTC195 viewsread 9 August 2026

Genesis Payment:一类唤醒+扫码规则如下: 1.工作时间:7X24小时,不间断! 2.代收方式:24小时跑分upi轮巡 提醒客户不要保存支付,保存支付的订单不一定到账,只能配合商户尽量24小时内追回 3.代付方式:公户代付+ upi 代付(upi代付仅支持整数订单) 4.代收单笔额度:100~30000卢比 5.代付单笔额度:100~100000卢比(upi代付1000-10000出款较快)。 注意!单笔通道率收取不能到(12)的订单,按(12)收取 6.商户承接类型:目前只接一类信誉游戏/体育盘资金,白资(短盘,盖盘勿入) 一类资金需要保30天无客诉(无司法投诉不限时间) 结算规则: 1.代付余额,可立即使用 2.回U时间:北京时间12:00-次日00:00 3.回U金额20W起,U价按照市场价格会波动。请下发前询价。 账户冻结规则: 1.进量前需发送产品链接验盘登记,如进量产品与登记产品不符,冻结全额。 …

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

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

“INRpay (五年老牌支付公司)” (@GenesisPay001), 130 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/GenesisPay001.

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.