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 53% 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.
Previous handles
@monocraftlive was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
@thearefcrypto held 6 August 2026 – 6 August 2026
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 word for word on 1 other registered channel. 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 (1 of the pairs behind the counts below)
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 0 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 215 comparable posts for this entry, running 1 February 2025 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.
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).
Across the whole group of 2, the earliest publisher we hold is @thearefcrypto — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_mutual, last confirmed 7 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.
Also posting the same content
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, 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.
30 measurements spanning 30 days, net -179,007. 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 2,342,485–2,575,194 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 30
Measured (UTC)
Subscribers
Change
5 Sept 2026, 01:22
2,369,336
-7,391
3 Sept 2026, 10:14
2,376,727
-8,020
2 Sept 2026, 04:55
2,384,747
-6,790
1 Sept 2026, 02:46
2,391,537
-4,478
31 Aug 2026, 03:48
2,396,015
-7,202
30 Aug 2026, 00:15
2,403,217
-6,416
29 Aug 2026, 00:52
2,409,633
-5,915
27 Aug 2026, 21:53
2,415,548
-3,972
27 Aug 2026, 01:15
2,419,520
-5,545
26 Aug 2026, 02:34
2,425,065
-5,587
25 Aug 2026, 04:23
2,430,652
-7,096
24 Aug 2026, 02:27
2,437,748
-9,377
22 Aug 2026, 14:00
2,447,125
no change
22 Aug 2026, 13:45
2,447,125
-4,377
22 Aug 2026, 00:38
2,451,502
-7,715
20 Aug 2026, 16:13
2,459,217
-3,477
19 Aug 2026, 14:43
2,462,694
-6,057
18 Aug 2026, 17:38
2,468,751
-5,620
17 Aug 2026, 19:54
2,474,371
-5,960
16 Aug 2026, 21:36
2,480,331
first reading
Engagement
1,095 posts held, back to 9 July 2024 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 3,625 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
0.305%
avg views ÷ 2,369,336 subscribers
Avg views / post
7,220
24 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
28
of 1,095 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 28 August 2026
Posts held
1,095 (9 July 2024 – 28 August 2026)
Views total
173,340
Reactions total
—
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
7 Sept 2026, 17:13 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
1
Videos
1
Links
2
Lifetime counters from Telegram’s own channel header, read 7 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
52s
Average length
52s
Measured directly from 1 video 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 22 of this channel’s own posts over the last 30 days (1 of the 24-hour readings behind this are interpolated, not measured directly): across 22 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 38 hours of being posted; a typical post has already reached 18.9% of its 24-hour view count within the first hour, and 52.0% within the first six; the median 24-hour reach across those posts is 2,580 views — 0.109% of this channel’s own subscriber count (90th percentile 3,084).
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.
🎯 THINK YOU’RE GOOD AT FPS?
It’s time to prove it—and play for real money.
⚔️ Enter fast-paced Mono Strike matches
💰 Earn $1 for every kill
🔥 Challenge real players
🎮 Practice free before entering cash matches
Aim sharp. Move fast. Get paid.
👉 Play the web version now: https://monocraft.live/
🚨 MONOCRAFT WEB IS LIVE
Enter Mono Strike directly from your browser—no download required.
💰 $1 PER KILL
🎯 Kill. Earn. Repeat.
⚔️ Choose your operative and weapon
🔥 Practice for free or enter real-money matches
The battlefield is open. Are you ready to earn?
👉 Play now: https://monocraft.live/
BREAKING: 🇺🇸🇮🇷 President Trump threatens to bomb Oman if they "get in the way" of US efforts to reopen the Strait of Hormuz and end the war with Iran.
Showing the 12 most recent of 1,095 posts we hold for @monocraftlive. 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.
Polls
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 1,000 most recent posts we hold (the sample is capped at 1,000), published 20 February 2025 to 28 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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
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.
Handles this channel named that no longer answer
Dead references
4
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
4
vacant every time we have ever looked
@monocraftlive named 4 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@arefnkteam named in 17 posts, 8 August 2026 – 8 August 2026
@timelessai named in 2 posts, 8 August 2026 – 8 August 2026
@arefnkmarketingteam named in 1 post, 8 August 2026 – 8 August 2026
@tonstakerhub named in 1 post, 8 August 2026 – 8 August 2026
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 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.
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.
Timetrade @timetradedex · 1,215,663 Telegram ranks this channel #3 of 90 here — alongside 89 others — read 8 August 2026
هوش مصنوعی با عارف @aiarefai · 716,459 Telegram ranks this channel #5 of 84 here — alongside 83 others — read 8 August 2026
فرصت های ۱۰۰x @xcrypto100x · 903,582 Telegram ranks this channel #22 of 87 here — alongside 86 others — read 8 August 2026
This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
Domains linked from posts
14 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.
xdrop.one1 post · 9 December 2025 – 9 December 2025 · example postNot linked — blocklisted domain
1 of 14 shown as text only, not a link. The exact host, not merely a domain it shares a registrable root with, matches a threat-intelligence blocklist this register already checks elsewhere (see methodology) — the link still appearing in a post is still a measured fact and is still shown, but no anchor is rendered here, so no click and no link equity passes to it from this page.
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 5 September 2026 — this
entry's latest reading, not the date you are reading this.
“$1 per Kill - Monocraft” (@monocraftlive), 2,369,336 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/monocraftlive.
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.
