Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 64% 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
33 measurements spanning 41 days, net -196,586. 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 1,882,094–2,137,656 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)
Subscribers
Change
17 Sept 2026, 07:57
1,911,582
-7,248
15 Sept 2026, 11:00
1,918,830
-5,331
13 Sept 2026, 22:22
1,924,161
-11,294
12 Sept 2026, 03:02
1,935,455
-12,157
9 Sept 2026, 15:55
1,947,612
-20,641
6 Sept 2026, 06:57
1,968,253
-12,765
4 Sept 2026, 03:39
1,981,018
-5,134
2 Sept 2026, 20:45
1,986,152
-7,577
1 Sept 2026, 17:34
1,993,729
-6,419
31 Aug 2026, 17:05
2,000,148
-5,556
30 Aug 2026, 17:58
2,005,704
-4,777
29 Aug 2026, 19:34
2,010,481
-4,905
28 Aug 2026, 17:54
2,015,386
-5,431
27 Aug 2026, 19:24
2,020,817
-1,227
26 Aug 2026, 17:17
2,022,044
-4,499
25 Aug 2026, 18:35
2,026,543
-4,620
24 Aug 2026, 20:54
2,031,163
-8,837
23 Aug 2026, 04:08
2,040,000
-7,492
21 Aug 2026, 15:59
2,047,492
-4,717
20 Aug 2026, 15:27
2,052,209
first reading
Engagement
57 posts held, back to 26 May 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 100 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
0.143%
avg views ÷ 1,911,582 subscribers
Avg views / post
2,740
30 posts measured
Reaction rate
0.497%
reactions ÷ views · ER floor
Posts in window
31
of 57 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 23 September 2026
Posts held
57 (26 May 2026 – 23 September 2026)
Views total
82,170
Reactions total
408
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
24 Sept 2026, 06:07 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
908
Videos
73
Links
925
Lifetime counters from Telegram’s own channel header, read 24 September 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.
Video runtime
11m 46s
Average length
59s
Measured directly from 12 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.
View velocity
How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.
Computed from 25 of this channel’s own posts over the last 30 days: across 25 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 22 hours of being posted; a typical post has already reached 22.7% of its 24-hour view count within the first hour, and 57.1% within the first six; the median 24-hour reach across those posts is 1,130 views — 0.059% of this channel’s own subscriber count (90th percentile 1,544).
8 most recently posted, with a view-velocity reading
Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed views is the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.
Reaction mix
1,273 reactions across 55 posts, in 20 distinct kinds. The most used accounts for 45.6% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
580
45.6%
❤
474
37.2%
👍
71
5.58%
❤🔥
31
2.44%
😁
30
2.36%
💯
15
1.18%
👏
14
1.10%
🤝
11
0.864%
👾
8
0.628%
🥰
8
0.628%
🙏
7
0.55%
🤔
6
0.471%
🏆
4
0.314%
👀
4
0.314%
🎃
3
0.236%
🆒
2
0.157%
🐳
2
0.157%
⚡
1
0.079%
🎄
1
0.079%
💘
1
0.079%
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 55 of the 57 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 1,273 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 57 most recent posts we hold, published 26 May 2026 to 23 September 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.
🔁 Explain it back
Today on X: what a "verifiable spend event" is - what's recorded (size + time, in your vault, under your MatchID)
Your turn: explain "verifiable spend event" to a friend in ONE sentence.
Best one gets pinned. Bonus if you can say what the rewards layer would do with it :)
🎙 Match Point - Friday 14:00 UTC, X Spaces
The CEO takes your questions on M² Card live, one at a time.
How to get yours in: log in at matchid.ai and submit the one question you'd like the CEO to answer. Intake closes Thursday 18:00 UTC. Only questions submitted through matchid.ai are read.
Mark your calendar 🗓️ https://x.com/i/spaces/1mxPaZmMBZbKN
📖 Chapter three is live: M² Card - the piece that closes the loop.
https://x.com/matchain_io/status/2102329450889355773
Short version: MatchID is the identity, MSD is your vault, URN (next chapter) is the reward. What was missing is an input - something that writes real life into the vault. The card is that input: every payment becomes a verifiable spend event you own, stripped of merchant and item detail.
Status i…
📍 The Matchain Map - chapter three: M² Card
Chapter one gave you an identity you control. Chapter two gave you a vault. This week: the piece that closes the loop - a card that writes real-world spend into your vault as a verifiable event you own.
Also this week, plainly, where the card programme stands. Up front, so nobody has to ask:
• Existing M² cardholders keep full use of their cards without new depositing (u…
✅ Quiz answers - chapter two
1. Any two of: spend events · behavioural patterns · your referral graph.
2. An explicit grant from you - with a scope and a duration, and revocable.
3. You do. Nobody queries without asking you first (including Matchain's own analytics).
4. $MAT.
Shout-outs: @Houssamzerrouni @Issam81zaio @Dmzid @eamalf
🎙 Match Point recap on Youtube: https://www.youtube.com/watch?v=noo9lkPbkiA
🧠 Friday quiz - chapter two
Four questions. Answers pinned tomorrow.
1. Name two of the three things MSD stores.
2. What has to exist before anyone can run a query against your vault?
3. Who decides who gets to ask?
4. When a merchant pays to query, what is the user's share paid in?
🎙 Match Point is live today 14:00 UTC https://twitter.com/i/spaces/1kKzDPdDvAaJv
🎬 Two flows, side by side
https://youtu.be/T1ABSbAQI9g
Where your data goes today vs where it goes with MSD, in five minutes on a whiteboard.
Also attached: a CONCEPT of the consent grant screen — what you'd see when a merchant asks. Not real UI, nothing final.
UX feedback wanted 👇
What would you need to see on that screen before you'd tap ""allow""? (scope? duration? who's asking? what you get?)"
🔁 Explain it back
Today on X we explained consent gating: grant → scope → revoke.
Your turn: explain "consent gating" to a friend in ONE message. What has to happen before anyone can read your vault?
Best one gets a shoutout. Bonus point if you can say why we call it privacy-by-architecture rather than privacy-by-policy.
🎙 Match Point - Friday 14:00 UTC Our CEO answers your questions on MSD, live on X Spaces (simulcast to YouTube).
One question at a time. How to submit: log in at www.matchid.ai and submit the one question you'd like answered.
Only questions submitted that way make the list. Intake closes Thursday 18:00 UTC.
📖 Chapter two is live: MSD explained - the data vault that pays you, not the platform.
https://x.com/matchain_io/status/2099820187705114753
Short version: there's a price list for you (location $0.10–0.60, inbox $40–120, medical history ~$300), and every right regulators have given you is a way to say no. MSD is a vault you control, where platforms have to ask, and a share of what they pay to ask comes to you.
Ques…
📍 The Matchain Map - chapter two: MSD
Chapter one in a line: identity, data and loyalty are three locks on the same door. This week we open the first one - your data.
What's coming:
• Tue —> the article: what your data sells for today, and how MSD changes who gets paid
• Wed —> consent gating explained (grant · scope · revoke)
• Thu —> the video: two flows side by side
• Fri —> quiz + 🎙 Match Point live with the CE…
🔥12👏6❤5🎃3❤🔥1
Showing the 12 most recent of 57 posts we hold for @matchain_fam. 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.
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.
Channels Telegram recommends alongside this one
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 7 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
MMPro Trust @mmprotrust · 725,788 Telegram ranks this channel #8 of 86 here — alongside 85 others — read 8 August 2026
Monad @MonadChannel3 · 29,688 Telegram ranks this channel #12 of 75 here — alongside 74 others — read 7 September 2026
CANO Kombat News @canoann · 31,752 Telegram ranks this channel #12 of 50 here — alongside 49 others — read 4 September 2026
SpunkySDX @SpunkySDX · 82,460 Telegram ranks this channel #14 of 78 here — alongside 77 others — read 7 September 2026
Coin.News by BabyDoge @coindotnewsann · 507,574 Telegram ranks this channel #14 of 86 here — alongside 85 others — read 9 August 2026
GraphDex @graphdex · 720,061 Telegram ranks this channel #15 of 87 here — alongside 86 others — read 8 August 2026
LayerNet Official @layernetofficial · 48,134 Telegram ranks this channel #16 of 75 here — alongside 74 others — read 22 September 2026
Hexacore RU @hexacore_ru · 27,000 Telegram ranks this channel #18 of 74 here — alongside 73 others — read 11 September 2026
Reserve @whiteswapfinance · 28,948 Telegram ranks this channel #18 of 66 here — alongside 65 others — read 8 September 2026
SafeFolioWallet ANNOUNCEMENT @SafeFolio · 69,834 Telegram ranks this channel #18 of 70 here — alongside 69 others — read 7 September 2026
Cryptogram @Kryptgram · 155,172 Telegram ranks this channel #19 of 88 here — alongside 87 others — read 12 August 2026
Prep 2 | Science | Mr.Ahmed ElBasha @mrahmedelbashaa · 31,480 Telegram ranks this channel #20 of 36 here — alongside 35 others — read 5 September 2026
ZaddyB 💰🌎 @zaddybempire · 21,919 Telegram ranks this channel #22 of 60 here — alongside 59 others — read 22 September 2026
Tabi Announcement @tabi_ann · 1,922,481 Telegram ranks this channel #22 of 88 here — alongside 87 others — read 7 August 2026
OverProtocol @OverProtocol · 23,104 Telegram ranks this channel #23 of 83 here — alongside 82 others — read 19 September 2026
TaleX @TaleX_chain · 24,491 Telegram ranks this channel #23 of 79 here — alongside 78 others — read 15 September 2026
OGCommunity @OGC_Announcements_Hub · 464,010 Telegram ranks this channel #23 of 89 here — alongside 88 others — read 9 August 2026
onchain @onchainchain · 753,397 Telegram ranks this channel #23 of 85 here — alongside 84 others — read 8 August 2026
Supermeow Updates @supermeowupdates · 195,706 Telegram ranks this channel #24 of 86 here — alongside 85 others — read 12 August 2026
ONUS Announcements @onus_newsroom · 210,133 Telegram ranks this channel #24 of 87 here — alongside 86 others — read 11 August 2026
HERE Wallet @herewallet · 1,134,407 Telegram ranks this channel #24 of 87 here — alongside 86 others — read 8 August 2026
Telgather Global @TelgatherMinigamesAnn · 33,092 Telegram ranks this channel #25 of 70 here — alongside 69 others — read 8 September 2026
AKEDO News @akedofun · 1,309,110 Telegram ranks this channel #25 of 84 here — alongside 83 others — read 8 August 2026
Symoria @symoria · 405,659 Telegram ranks this channel #26 of 87 here — alongside 86 others — read 14 August 2026
This channel appears in 443 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
Domains linked from posts
2 domains this channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.
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 17 September 2026 — this
entry's latest reading, not the date you are reading this.
“Matchain Fam” (@matchain_fam), 1,911,582 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/matchain_fam.
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.