Telegram RegisterThe public register of Telegram
Telegram profile photo for GenesisPay (English channel)

Channel

GenesisPay (English channel)

@GenesisPayEnglish

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

72subscribers

-7 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-1002365888922
TypeChannel
Username@GenesisPayEnglish
CreatedBetween 1 September 2024 and 28 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live18 November 2026
Measurements held8
Confirmed unchanged2 times, most recently 18 November 2026
On Telegramt.me/GenesisPayEnglish

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 28 September 2026 and assigned it the closest of 31 fixed categories, at 46% 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/100 · this entry15 May 2025, 04:44 UTC@GenesisPay7/56615 May 2025, 04:45 UTC1.00under a minute
@GenesisPayEnglish/104 · this entry4 Jul 2025, 08:47 UTC@GenesisPay7/5704 Jul 2025, 08:47 UTC1.00under a minute
@GenesisPayEnglish/105 · this entry20 Jul 2025, 07:26 UTC@GenesisPay7/57120 Jul 2025, 07:26 UTC1.00under a minute
@GenesisPayEnglish/106 · this entry23 Jul 2025, 12:12 UTC@GenesisPay7/57223 Jul 2025, 12:12 UTC1.00under a minute
@GenesisPay7/57314 Aug 2025, 04:22 UTC@GenesisPayEnglish/107 · this entry14 Aug 2025, 04:22 UTC1.00under a minute
@GenesisPay7/5785 Dec 2025, 06:16 UTC@GenesisPayEnglish/112 · this entry5 Dec 2025, 06:16 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
@GenesisPay711 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (7–4)
@GenesisPay0018 (8/8 hand-verifiable sample passed)1.00under a minute@GenesisPay001 (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 10 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 28 March 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 — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_mutual, 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

727975.59 August 2026 — 79 subscribers9 August 2026 — 79 subscribers25 August 2026 — 77 subscribers1 September 2026 — 76 subscribers10 September 2026 — 75 subscribers4 October 2026 — 74 subscribers13 October 2026 — 73 subscribers9 November 2026 — 72 subscribers9 August 20269 November 2026
8 measurements spanning 92 days, net -7. 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 71–80 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Nov 2026, 12:3672-1
13 Oct 2026, 17:5673-1
4 Oct 2026, 00:2274-1
10 Sept 2026, 23:1875-1
1 Sept 2026, 22:3676-1
25 Aug 2026, 13:5377-2
9 Aug 2026, 19:3079no change
9 Aug 2026, 07:4679first reading

Engagement

18 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 18 posts for this entry, the most recent from 22 April 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

3 reactions across 3 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍3100.0%

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

Measured over the 18 most recent posts we hold, published 28 March 2025 to 22 April 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

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:06 UTC46 viewsread 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…

9 Apr 2026, 14:05 UTC31 viewsread 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…

5 Dec 2025, 06:16 UTC68 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 UTC47 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…

10 Oct 2025, 04:58 UTC65 viewsread 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 UTC62 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.进量前需发送产品链接验盘登记,如进量产品与登记产品不符,冻结全额。 …

6 Sept 2025, 07:06 UTC71 viewsread 9 August 2026

🥇🥇🥇We, Genesispay, have been focusing on the game payment business in the Indian market for 3 years 🤼‍♀️ We need local Indian partners who can provide corporate bank accounts 🏦 Currently, we need a corporate bank account with SIB-3id. The following is our current daily settlement data for a single SIB-3id ☎️ If you can provide a SIB-3ID account, please contact us. Our funding type is pure game funding 🙆‍♂️ Lookin…

14 Aug 2025, 04:22 UTC78 viewsread 9 August 2026

✅Gaming funds 【2.6%】TMB corperate+ MQR 【2.6%】J&amp;K(Jammu and Kashmir Bank) corperate+ MQR 【2.6%】KARNATAKA one+MQR 【2.6%】Kerala Gramin bank corporate +MQR (New) 【2.8%】SBI3ID, SBI CMP ❗️Please note that game fund cooperation requires a minimum deposit of 2000USDT ==================================== ✅For Stock payouts use, now need 【3.5%】Axis bank NEO for Corporation 【3.5%】Axis bank Corporation 2ID (Batc…

23 Jul 2025, 12:12 UTC95 viewsread 9 August 2026

✅Gaming funds 【2.6%】TMB corperate+ MQR 【2.6%】J&amp;K(Jammu and Kashmir Bank) corperate+ MQR 【2.6%】KARNATAKA one+MQR 【2.6%】Kerala Gramin bank corporate +MQR (New) 【2.8%】SBI3ID, SBI CMP ❗️Please note that game fund cooperation requires a minimum deposit of 2000USDT

20 Jul 2025, 07:26 UTC94 viewsread 9 August 2026

✅Gaming funds 【2.6%】TMB corperate+ MQR 【2.6%】J&amp;K(Jammu and Kashmir Bank) corperate+ MQR 【2.6%】KARNATAKA one+MQR 【2.6%】Kerala Gramin bank corporate +MQR (New) 【2.8%】SBI3ID, SBI CMP ❗️Please note that game fund cooperation requires a minimum deposit of 2000USDT ==================================== ✅For Stock payouts use, now need 【3.5%】Axis bank NEO for Corporation 【3.5%】Axis bank Corporation 2ID (Batc…

4 Jul 2025, 08:47 UTC93 viewsread 9 August 2026

✅Gaming funds 【2.6%】TMB corperate+ MQR 【2.6%】J&amp;K(Jammu and Kashmir Bank) corperate+ MQR 【2.6%】KARNATAKA one+MQR 【2.8%】SBI3ID, SBI CMP ❗️Please note that game fund cooperation requires a minimum deposit of 2000USDT ==================================== ✅For Stock payouts use, now need 【3.5%】Axis bank NEO for Corporation ❗️Please note that Stock payouts fund cooperation requires a minimum deposit of 2000USD…

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

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.

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

“GenesisPay (English channel)” (@GenesisPayEnglish), 72 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/GenesisPayEnglish.

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.