Technology — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 55% 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
48 measurements spanning 80 days, net +5,942. 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 21,294–29,018 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 48
Measured (UTC)
Subscribers
Change
26 Oct 2026, 16:20
28,127
+30
25 Oct 2026, 16:28
28,097
+28
24 Oct 2026, 13:18
28,069
+37
23 Oct 2026, 12:16
28,032
+44
22 Oct 2026, 10:57
27,988
+48
21 Oct 2026, 00:57
27,940
+77
19 Oct 2026, 22:28
27,863
+45
19 Oct 2026, 01:26
27,818
+34
18 Oct 2026, 04:38
27,784
+59
17 Oct 2026, 02:31
27,725
+67
16 Oct 2026, 01:09
27,658
+56
15 Oct 2026, 00:09
27,602
+121
13 Oct 2026, 18:55
27,481
+237
10 Oct 2026, 02:38
27,244
+113
5 Oct 2026, 20:35
27,131
+276
30 Sept 2026, 12:40
26,855
+794
18 Sept 2026, 01:58
26,061
+137
15 Sept 2026, 18:01
25,924
+220
14 Sept 2026, 02:01
25,704
+179
12 Sept 2026, 07:55
25,525
first reading
Engagement
45 posts held, back to 5 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 117 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
24.4%
avg views ÷ 28,127 subscribers
Avg views / post
6,870
11 posts measured
Reaction rate
0.962%
reactions ÷ views · ER floor
Posts in window
11
of 45 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
Window
Rolling 30 days · latest post in window 27 October 2026
Posts held
45 (5 June 2026 – 27 October 2026)
Views total
75,587
Reactions total
727
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
27 Oct 2026, 08:47 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
Photos
96
Videos
1
Links
96
Lifetime counters from Telegram’s own channel header, read 27 October 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.
Reaction mix
2,182 reactions across 45 posts, in 29 distinct kinds. The most used accounts for 42.2% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
920
42.2%
👍
290
13.3%
🤡
286
13.1%
😭
250
11.5%
🔥
149
6.83%
💔
72
3.30%
🤔
58
2.66%
👏
28
1.28%
🤷♂
27
1.24%
❤🔥
16
0.733%
😱
14
0.642%
😁
11
0.504%
👀
8
0.367%
🌚
6
0.275%
🍾
6
0.275%
😘
6
0.275%
🙊
6
0.275%
🫡
6
0.275%
👌
4
0.183%
😴
4
0.183%
9 further kinds
15
0.687%
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 45 of the 45 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 2,182 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 45 most recent posts we hold, published 5 June 2026 to 27 October 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.
📢 ‼️ MPay Service Maintenance Notice
In compliance with Visa's system upgrade, all MPay cards will be temporarily unavailable starting at 00:00 UTC on October 28, 2026.
⚠️ During this period:
• Card payments will be unavailable
• Transactions will be unavailable
• Card top-ups will be unavailable
🕒 Expected restoration: 00:00 UTC on October 29, 2026
No action is needed on your part — your data and funds remain fully …
🔵 Google, handled by MPAY!
A cloud bill here.
A Play charge there.
An ad budget running.
A storage plan renewing.
Google has a lot of ways to charge you.
MPAY has one card that handles every one.
💳 VISA virtual card. Global. Instant.
👉Web |🚀Twitter |✅Channel |⚡️Ins
🤖 AI is everywhere now. One card that keeps up!💳
Writing your emails. Debugging your code. Editing your videos. Answering your questions.
One thing it still needs? A card that works.
💳 MPAY VISA virtual card. USDT-funded. AI-ready.🚀
Subscribe to what you use.
👉Web |🚀Twitter |✅Channel |⚡️Ins
💳 A little reminder before you enter your card details
✅ CVV — 3-digit code in the top right corner
✅ Expiration date — month/year in the bottom left corner
These are the two most common mistakes.
⚠️ Repeated incorrect entries → Temporary account lockout
One extra look saves a lot of trouble.
👉Web |🚀Twitter |✅Channel |⚡️Ins
📢 ‼️ MPay Service Upgrade Notice
✅ Existing cards are back in use!
Due to a security upgrade on the VISA card platform, new card applications are temporarily paused. We expect to reopen them in a few days.
⚠️ Please use your card responsibly to avoid triggering risk controls that could result in your VISA card being locked.
Thank you for your understanding. ❤️
👉Web |🚀Twitter |✅Channel |⚡️Ins
📢 ‼️ MPay Service Upgrade Notice
In conjunction with a Visa system upgrade, MPay will undergo maintenance starting October 12, 2026.
⚠️ Some users may experience temporary disruptions. Services will be restored gradually.
No action needed — your data and funds are fully secure.
We apologize for the inconvenience and appreciate your support! ❤️
👉Web |🚀Twitter |✅Channel |⚡️Ins
🛒 Temu. MPAY. Sorted.
Temu has the deals.
You have the cart.
MPAY has the card that checks out.
💳 VISA virtual card. Global. Instant.
Shopping, sorted.
👉Web |🚀Twitter |✅Channel |⚡️Ins
📢 Before You Deposit USDT or USDC
We only accept deposits via these networks:
USDT → BEP20 · ERC20 · TRC20
USDC → BEP20 · ERC20 · Base
⚠️ Common mistakes to avoid:
❌ TRX on TRC20 → not accepted
❌ BNB on BEP20 → not accepted
If you send either, it won't be credited.
Other networks and crypto assets will not be credited either. Please double-check before sending.
🔒 Your security is our priority. Questions? Reach…
🌍 Your whole trip. One card.
🏨 Booking. 🚕 Uber. ⛴ Stena Line. ✈️ Qatar Airways.
Hotel. Ride. Ferry. Flight.
Every leg of the journey needs a payment that goes through.
💳 MPAY VISA virtual card. USDT-funded. Global acceptance.
One card. Every stop.
👉Web |🚀Twitter |✅Channel |⚡️Ins
✅✅New Security Feature: Lock Your Card Anytime!
🔒 One-Tap Lock
Not using your card? Lock it with one tap. Unlock anytime.
⚡️ Self-Unlock After 24h
Locked due to incorrect details? You can unlock it yourself after 24 hours.
No waiting. No support tickets. You're in control.
Just tap the button below your card. 👇
👉Web |🚀Twitter |✅Channel |⚡️Ins
🎁 Two Levels. More Ways to Earn!
1️⃣ Invite friends
2️⃣ Their invites count too
💰 Earn from both levels
💵 Get paid in USDT
⚡️ Withdraw anytime
One link. Two levels. Start earning 👇
👉Web |🚀Twitter |✅Channel |⚡️Ins
❤20❤🔥9🔥4
Showing the 12 most recent of 45 posts we hold for @MpayCard. 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 4 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.
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 26 October 2026 — this
entry's latest reading, not the date you are reading this.
“Mpay” (@MpayCard), 28,127 subscribers as measured 26 October 2026. Telegram Register, tgregister.com/channel/MpayCard.
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.