$ARB RISK FREE🦈
👍3
Signed Matin | future125

Channel
@MawtinCrypto_vip
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · View velocity · Reactions · Stars · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Telegram's recommendations · Domains linked from posts · Cite this entry
5,653,700subscribers
+1,013,146 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among the largest entries.
| Telegram ID | -1001091293599 |
|---|---|
| Type | Channel |
| Usernames | @matincrypto_vip @MawtinCrypto_vip |
| Created | 19 August 2016 — measured — dated from the channel’s first post |
| First recorded | 6 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 20 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/MawtinCrypto_vip |
Crypto & trading — 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 100% 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.
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.
Posts published here appear word for word on 12 other registered channels. They sit inside a group of 464 channels that share the same post bodies 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @MawtinCrypto_vip/29629 · this entry22 Jun 2025, 02:30 UTC | @AdsVipz/537222 Jun 2025, 02:35 UTC | 1.00 | 4 minutes |
| @AdsVipz/751723 Jun 2025, 16:35 UTC | @MawtinCrypto_vip/30140 · this entry23 Jun 2025, 22:46 UTC | 1.00 | 6.2 hours |
| @AdsVipz/851224 Jun 2025, 02:18 UTC | @MawtinCrypto_vip/30227 · this entry24 Jun 2025, 02:19 UTC | 1.00 | under a minute |
| @AdsVipz/884024 Jun 2025, 06:29 UTC | @MawtinCrypto_vip/30260 · this entry24 Jun 2025, 06:29 UTC | 1.00 | under a minute |
| @MawtinCrypto_vip/30416 · this entry24 Jun 2025, 12:23 UTC | @AdsVipz/922424 Jun 2025, 12:32 UTC | 1.00 | 8 minutes |
| @MawtinCrypto_vip/30733 · this entry26 Jun 2025, 19:57 UTC | @AdsVipz/1216026 Jun 2025, 20:06 UTC | 1.00 | 10 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @AdsVipz | 63 (8/8 hand-verifiable sample passed) | 1.00 | 8 minutes | @AdsVipz (35–28) |
| @km_ap | 34 (8/8 hand-verifiable sample passed) | 0.96 | 12 minutes | this entry (22–12) |
| @fo_rk | 28 (8/8 hand-verifiable sample passed) | 0.92 | 4 minutes | @fo_rk (18–10) |
| @ne_wg | 26 (8/8 hand-verifiable sample passed) | 0.94 | 4 minutes | @ne_wg (20–6) |
| @khabari | 26 (8/8 hand-verifiable sample passed) | 0.96 | 17 minutes | @khabari (14–12) |
| @akhbarefori | 26 (8/8 hand-verifiable sample passed) | 0.97 | 7 minutes | @akhbarefori (19–7) |
| @pezeshkian_com | 20 (8/8 hand-verifiable sample passed) | 0.95 | 11 minutes | @pezeshkian_com (13–7) |
| @khabarfouri | 18 (8/8 hand-verifiable sample passed) | 0.94 | 9 minutes | even |
| @se_pz | 17 (8/8 hand-verifiable sample passed) | 0.98 | 2 minutes | this entry (11–6) |
| @ga_os | 14 (8/8 hand-verifiable sample passed) | 0.98 | 2 minutes | this entry (9–5) |
| @M0_HM | 11 (8/8 hand-verifiable sample passed) | 0.92 | 32 minutes | @M0_HM (6–5) |
| @farsna | 11 (8/8 hand-verifiable sample passed) | 0.92 | 11 minutes | @farsna (11–0) |
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 181 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 4,565 comparable posts for this entry, running 29 September 2023 to 7 August 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.
Across the whole group of 464, the earliest publisher we hold is @akharinkhabar. That is a statement about our reading window, not a claim of authorship.
On 160 of the 225 posts we watched over 30days, the view counter climbed while the reaction counter stayed where it was — by more than this channel’s own reactions-per-view rate can account for. That rate, measured on this entry, is 0.0068 reactions per view.
| Post | Over | Views | Reactions | Expected |
|---|---|---|---|---|
| /437238 Aug 2026, 18:36 UTC | 30 minutes | 3,090 → 5,400at least +2,300 | 136 → 136at most +1 | +15.6 |
| /437238 Aug 2026, 18:36 UTC | 55 minutes | 6,550 → 8,100at least +1,540 | 136 → 136at most +1 | +10.4 |
| /437238 Aug 2026, 18:36 UTC | 39 minutes | 8,100 → 9,590at least +1,480 | 136 → 136at most +1 | +10.0 |
| /437238 Aug 2026, 18:36 UTC | 65 minutes | 9,600 → 14,100at least +4,400 | 136 → 136at most +1 | +29.8 |
| /437248 Aug 2026, 18:36 UTC | 30 minutes | 3,200 → 5,340at least +2,130 | 127 → 127at most +1 | +14.4 |
| /437248 Aug 2026, 18:36 UTC | 55 minutes | 6,760 → 8,410at least +1,640 | 127 → 127at most +1 | +11.1 |
| /437248 Aug 2026, 18:36 UTC | 39 minutes | 8,410 → 10,100at least +1,590 | 127 → 127at most +1 | +10.8 |
| /437248 Aug 2026, 18:36 UTC | 65 minutes | 10,100 → 14,700at least +4,500 | 127 → 127at most +1 | +30.5 |
| /437258 Aug 2026, 18:36 UTC | 30 minutes | 2,910 → 5,330at least +2,410 | 116 → 116at most +1 | +16.3 |
| /437258 Aug 2026, 18:36 UTC | 55 minutes | 6,440 → 8,060at least +1,610 | 116 → 116at most +1 | +10.9 |
| /437258 Aug 2026, 18:36 UTC | 39 minutes | 8,060 → 9,960at least +1,890 | 116 → 116at most +1 | +12.8 |
| /437258 Aug 2026, 18:36 UTC | 65 minutes | 9,980 → 14,500at least +4,420 | 116 → 116at most +1 | +30.0 |
| /437268 Aug 2026, 18:36 UTC | 30 minutes | 2,820 → 5,240at least +2,410 | 139 → 139at most +1 | +16.3 |
| /437268 Aug 2026, 18:36 UTC | 55 minutes | 6,380 → 7,980at least +1,590 | 140 → 140at most +1 | +10.8 |
| /437268 Aug 2026, 18:36 UTC | 39 minutes | 7,980 → 9,580at least +1,590 | 140 → 140at most +1 | +10.8 |
| /437268 Aug 2026, 18:36 UTC | 65 minutes | 9,590 → 14,300at least +4,610 | 140 → 140at most +1 | +31.3 |
| /4383412 Aug 2026, 22:47 UTC | 30 minutes | 8,700 → 10,800at least +2,000 | 237 → 237at most +1 | +13.6 |
| /4383412 Aug 2026, 22:47 UTC | 30 minutes | 10,800 → 12,600at least +1,700 | 237 → 237at most +1 | +11.5 |
| /4383412 Aug 2026, 22:47 UTC | 31 minutes | 12,600 → 14,600at least +1,900 | 237 → 237at most +1 | +12.9 |
| /4383412 Aug 2026, 22:47 UTC | 30 minutes | 16,300 → 19,300at least +2,900 | 239 → 239at most +1 | +19.7 |
| /4388214 Aug 2026, 17:20 UTC | 34 minutes | 5,740 → 7,270at least +1,520 | 107 → 107at most +1 | +10.3 |
| /4388214 Aug 2026, 17:20 UTC | 30 minutes | 7,280 → 9,750at least +2,460 | 107 → 107at most +1 | +16.7 |
| /4388214 Aug 2026, 17:20 UTC | 31 minutes | 10,400 → 12,200at least +1,700 | 107 → 107at most +1 | +11.5 |
| /4388214 Aug 2026, 17:20 UTC | 12 hours | 13,000 → 17,600at least +4,500 | 107 → 108at most +2 | +30.5 |
| /4388314 Aug 2026, 17:24 UTC | 34 minutes | 5,910 → 7,450at least +1,530 | 115 → 115at most +1 | +10.4 |
| /4388314 Aug 2026, 17:24 UTC | 30 minutes | 7,460 → 9,990at least +2,520 | 115 → 115at most +1 | +17.1 |
| /4388314 Aug 2026, 17:24 UTC | 31 minutes | 10,600 → 12,700at least +2,000 | 115 → 115at most +1 | +13.6 |
| /4388314 Aug 2026, 17:24 UTC | 11 hours | 13,600 → 17,900at least +4,200 | 115 → 115at most +1 | +28.5 |
| /4388514 Aug 2026, 17:49 UTC | 34 minutes | 5,860 → 8,080at least +2,210 | 256 → 256at most +1 | +15.0 |
| /4388514 Aug 2026, 17:49 UTC | 30 minutes | 8,090 → 10,200at least +2,010 | 256 → 256at most +1 | +13.6 |
| /4388514 Aug 2026, 17:49 UTC | 31 minutes | 11,100 → 12,900at least +1,700 | 256 → 256at most +1 | +11.5 |
| /4388514 Aug 2026, 17:49 UTC | 12 hours | 14,000 → 18,200at least +4,100 | 256 → 256at most +1 | +27.8 |
| /4389614 Aug 2026, 19:11 UTC | 34 minutes | 2,880 → 4,440at least +1,550 | 24 → 24at most +1 | +10.5 |
| /4389614 Aug 2026, 19:11 UTC | 34 minutes | 5,580 → 7,100at least +1,510 | 25 → 25at most +1 | +10.2 |
| /4389614 Aug 2026, 19:11 UTC | 30 minutes | 8,940 → 11,800at least +2,760 | 144 → 144at most +1 | +18.7 |
| /4389614 Aug 2026, 19:11 UTC | 31 minutes | 12,700 → 14,800at least +2,000 | 144 → 144at most +1 | +13.6 |
| /436797 Aug 2026, 13:08 UTC | 35 minutes | 3,250 → 5,810at least +2,550 | 150 → 151at most +2 | +17.3 |
| /436797 Aug 2026, 13:08 UTC | 30 minutes | 5,810 → 8,810at least +2,990 | 151 → 151at most +1 | +20.3 |
| /436797 Aug 2026, 13:08 UTC | 35 minutes | 8,810 → 10,800at least +1,890 | 151 → 152at most +2 | +12.8 |
Expectedis the view gain multiplied by this channel’s own prior reactions-per-view rate over the same post — not a corpus average, so a channel whose audience never reacts is compared only against itself. Every interval is credited in the direction that makes the observation harder to record, never easier: t.me renders views and reactions to three significant figures above ~1,000, so a raw delta can be a rendering step. Every delta below is at least 4 x the coarser reading's step, the view gain is discounted by a full step and the reaction gain credited with one. Measured by tgregister velocity.py (our own t.me/s/ readings).
What this does and does not say.It says the two counters moved apart, by more than rounding and more than this channel’s own history predicts. It asserts no cause. Views arriving from outside Telegram, an embedded or forwarded copy of the post, and a burst of readers who simply do not react all produce this shape. This detector has recorded very few observations across the whole register, and its precision has not been measured; treat it as an anomaly worth looking at, not as a finding.
Recorded under the keys clone_copy · clone_mutual · view_reaction_decoupling, last confirmed 16 August 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.
This channel’s posts match, word for word or near enough, posts on 463 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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.
413 more channels are in this same group but not listed individually here.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 04:12 | 5,653,700 | -2,987 |
| 15 Aug 2026, 20:54 | 5,656,687 | +131,406 |
| 14 Aug 2026, 13:54 | 5,525,281 | +11,973 |
| 14 Aug 2026, 09:35 | 5,513,308 | +12,856 |
| 13 Aug 2026, 04:58 | 5,500,452 | -2,459 |
| 12 Aug 2026, 22:46 | 5,502,911 | +12,454 |
| 12 Aug 2026, 01:33 | 5,490,457 | +5,284 |
| 11 Aug 2026, 20:16 | 5,485,173 | +3,563 |
| 11 Aug 2026, 02:31 | 5,481,610 | +27,603 |
| 10 Aug 2026, 17:31 | 5,454,007 | +31,102 |
| 10 Aug 2026, 04:42 | 5,422,905 | +34,528 |
| 9 Aug 2026, 17:42 | 5,388,377 | +31,795 |
| 9 Aug 2026, 04:12 | 5,356,582 | +54,874 |
| 8 Aug 2026, 14:26 | 5,301,708 | +149,221 |
| 8 Aug 2026, 05:05 | 5,152,487 | +332,303 |
| 7 Aug 2026, 13:10 | 4,820,184 | +60,174 |
| 7 Aug 2026, 02:41 | 4,760,010 | +100,150 |
| 6 Aug 2026, 10:21 | 4,659,860 | +19,306 |
| 6 Aug 2026, 05:30 | 4,640,554 | no change |
| 6 Aug 2026, 05:22 | 4,640,554 | first reading |
29,412 posts held, back to 19 August 2016 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 5,537 pagesof Telegram’s post history, 20 posts per page.
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. It is computed over the 870 of 876 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 16 August 2026 |
|---|---|
| Posts held | 29,412 (19 August 2016 – 16 August 2026) |
| Views total | 17,557,040 |
| Reactions total | 166,921 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 16 Aug 2026, 05:22 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.
Measured directly from 7 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.
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 229 of this channel’s own posts over the last 30 days (7 of the 24-hour readings behind this are interpolated, not measured directly): across 186of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 9.0 hours of being posted; a typical post has already reached 12.2% of its 24-hour view count within the first hour, and 38.8% within the first six; the median 24-hour reach across those posts is 20,100 views — 0.356% of this channel’s own subscriber count (90th percentile 20,900).
| Post | Readings | Latest reading | Curve | 24h reach | Half of last-observed views by |
|---|---|---|---|---|---|
| /4394816 Aug 2026, 05:02 UTC | 119 minutes – 19 minutes old | 1,530 views ~3 reactions | no checkpoint reading yet | not yet at 24h | not measurable yet |
| /4394716 Aug 2026, 05:02 UTC | 120 minutes – 20 minutes old | 1,220 views ~14 reactions | no checkpoint reading yet | not yet at 24h | not measurable yet |
| /4394615 Aug 2026, 17:52 UTC | 1417 minutes – 11 hours old | 10,400 views ~8 reactions | 60 minutes: 878 → 3.0 hours: 2,087 interp. → 6.0 hours: 4,666 interp. → 12 hours: 10,400still climbing at last reading | not yet at 24h | 6.6 hoursprovisional — final view count still climbing |
| /4394515 Aug 2026, 17:48 UTC | 1421 minutes – 12 hours old | 10,300 views ~8 reactions | 60 minutes: 943 → 3.0 hours: 2,098 interp. → 6.0 hours: 4,634 interp. → 12 hours: 10,300still climbing at last reading | not yet at 24h | 6.6 hoursprovisional — final view count still climbing |
| /4394415 Aug 2026, 17:48 UTC | 1421 minutes – 12 hours old | 10,400 views ~11 reactions | 60 minutes: 969 → 3.0 hours: 2,126 interp. → 6.0 hours: 4,680 interp. → 12 hours: 10,400still climbing at last reading | not yet at 24h | 6.6 hoursprovisional — final view count still climbing |
| /4394315 Aug 2026, 17:28 UTC | 1517 minutes – 12 hours old | 9,150 views ~150 reactions | 60 minutes: 908 interp. → 3.0 hours: 2,050 → 6.0 hours: 3,949 interp. → 12 hours: 9,150still climbing at last reading | not yet at 24h | 7.0 hoursprovisional — final view count still climbing |
| /4394215 Aug 2026, 17:28 UTC | 1518 minutes – 12 hours old | 8,710 views ~161 reactions | 60 minutes: 1,000 interp. → 3.0 hours: 2,100 → 6.0 hours: 3,968 interp. → 12 hours: 8,710still climbing at last reading | not yet at 24h | 6.6 hoursprovisional — final view count still climbing |
| /4394115 Aug 2026, 17:28 UTC | 1518 minutes – 12 hours old | 9,020 views ~128 reactions | 60 minutes: 965 interp. → 3.0 hours: 2,100 → 6.0 hours: 3,927 interp. → 12 hours: 9,020still climbing at last reading | not yet at 24h | 6.9 hoursprovisional — final view count still climbing |
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 viewsis 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.
31,695 reactions across 239 posts, in 2 distinct kinds. The most used accounts for 99.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 31,472 | 99.3% | |
| 👎 | 223 | 0.704% |
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 978 of the 1,000 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 205,456reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 15 July 2026 to 16 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @MawtinCrypto_vip. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 1,000 most recent posts we hold for this entry (the sample is capped at 1,000), published 15 July 2026 to 16 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
$ARB RISK FREE🦈
👍3
Signed Matin | future125
درود💖
👍14
Signed Matin | future125
Voice message, posted without a caption
👍7👎1
Signed Matin | future125
همین الان از WhatsApp پیام بده بنویس "سیگنال" برات بفرستم 👍 https://wa.me/989120456035
👍7👎1
Signed Matin | future125
سیگنال فیوچر بعدیم ام آمادست 👍
👍11
Signed Matin | future125
Video, posted without a caption
👍150
Signed Matin | future125
MARKET
👍161
Signed Matin | future125
$ARB SHORT
👍128
Signed Matin | future125
👌
Signed Matin | future125
رفقا ری اکشن بزنید سیگنال بعدی هم بریم👍
👍33
Signed Matin | future125
رفقا اینجا کسی حق مسخره کردن نداره! هرکی نسبت به مارجین خودش ترید میزنه پس خجالت نکشید و شات ورود هاتون رو بفرستید تا براتون میدیریتش کنم👍
👍147
Signed Matin | future125
خخخ داداش با این مبلغ مارجین که شما گذاشتید آدم روش نمیشه عکس بفرسته
👍136
Signed Matin | future125
Showing the 12 most recent of 29,412 posts we hold for @MawtinCrypto_vip. 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.
@MawtinCrypto_vip edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Citation-graph rank — 578,482 of 1,481,217entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
@MawtinCrypto_vip named 28 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was 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 8 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.
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.
This channel appears in 73 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.
28 domainsthis 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 16 August 2026 — this entry's latest reading, not the date you are reading this.
“Matin Crypto | ارز دیجیتال” (@MawtinCrypto_vip), 5,653,700 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/MawtinCrypto_vip.
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.