Channel
@EarnCryptoLegits
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
535subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001196145095 |
|---|---|
| Type | Channel |
| Username | @EarnCryptoLegits |
| Description | Best crypto signals (bitmex & binance) For primium-: @kim800 |
| Created | Between 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 6 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/EarnCryptoLegits |
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 11 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 5 other registered channels. They sit inside a group of 377 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 |
|---|---|---|---|
| @BinanceScalpingCalls/340717 Aug 2024, 05:19 UTC | @EarnCryptoLegits/38398 · this entry7 Aug 2024, 05:19 UTC | 1.00 | under a minute |
| @EarnCryptoLegits/38401 · this entry20 Aug 2024, 08:14 UTC | @BinanceScalpingCalls/3407420 Aug 2024, 08:14 UTC | 1.00 | under a minute |
| @BinanceScalpingCalls/3409629 Aug 2024, 05:50 UTC | @EarnCryptoLegits/38422 · this entry29 Aug 2024, 05:50 UTC | 1.00 | under a minute |
| @BinanceScalpingCalls/3409729 Aug 2024, 05:50 UTC | @EarnCryptoLegits/38423 · this entry29 Aug 2024, 05:50 UTC | 1.00 | under a minute |
| @BinanceScalpingCalls/3409929 Aug 2024, 05:50 UTC | @EarnCryptoLegits/38425 · this entry29 Aug 2024, 05:50 UTC | 1.00 | under a minute |
| @BinanceScalpingCalls/3410029 Aug 2024, 05:50 UTC | @EarnCryptoLegits/38426 · this entry29 Aug 2024, 05:50 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @BinanceScalpingCalls | 20 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (20–0) |
| @Bybitbinancsignals | 20 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (20–0) |
| @Binancefuturestradin | 20 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @Binancefuturestradin (20–0) |
| @officialpumpexperts | 18 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (18–0) |
| @binance_announcements | 17 (8/8 hand-verifiable sample passed) | 1.00 | 6.2 hours | @binance_announcements (17–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 37 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 20 comparable posts for this entry, running 5 August 2024 to 3 October 2024. 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 377, the earliest publisher we hold is @mash. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_copy · clone_source, last confirmed 8 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 376 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.
326 more channels are in this same group but not listed individually here.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Aug 2026, 18:19 | 535 | no change |
| 6 Aug 2026, 05:11 | 535 | first reading |
20 posts held, back to 5 August 2024 — 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 pageof 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 20 posts for this entry, the most recent from 3 October 2024. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 6 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
#BTC/USDT ANALYSIS Bitcoin is rebounding from the Ichimoku Cloud, which is acting as support, while the 100MA presents a resistance barrier above the price action. A breakout above both the 100MA and the horizontal resistance zone could signal the start of a strong bullish rally in the market.
📍Coin : #ENA/USDT 🟢 LONG 👉 Entry: 0.2280 - 0.2130 🌐 Leverage: 20x 🎯 Target 1: 0.2302 🎯 Target 2: 0.2325 🎯 Target 3: 0.2348 🎯 Target 4: 0.2371 🎯 Target 5: 0.2395 🎯 Target 6: 0.2421 ❌ StopLoss: 0.2080
📍Coin : #GMT/USDT 🔴 SHORT 👉 Entry: 0.1308 - 0.1367 🌐 Leverage: 20x 🎯 Target 1: 0.1295 🎯 Target 2: 0.1280 🎯 Target 3: 0.1265 🎯 Target 4: 0.1245 🎯 Target 5: 0.1223 🎯 Target 6: 0.1192 ❌ StopLoss: 0.1445
Binance Launches Zero Fee Promotion on EUR/USDC and EUR/USDT Trading Pairs for VIP 2 - 9 users and Spot Liquidity Providers https://www.binance.com/en/support/announcement/5563091ba0384fc69cad2abf04da33a2
Binance Will Support the Kaia (KLAY) Network Upgrade & Hard Fork https://www.binance.com/en/support/announcement/a5a0edbe81ff4724887d7fcdb12cfd15
Earn Wednesday: New Limited-Time Offers Available Now! (2024-08-28) https://www.binance.com/en/support/announcement/995ccfa758c047598ef2aa9a85efbf3b
New Loanable Assets Available on Binance Loans (Flexible Rate) and VIP Loan - 2024-08-28 https://www.binance.com/en/support/announcement/0ca7613f87cf4ebb82c30a747c22f740
Notice of Removal of Spot Trading Pairs - 2024-08-30 https://www.binance.com/en/support/announcement/f6c1a549e5374ecaa8591b536b2b138f
Binance Will Support the Polygon (MATIC) Token Swap to Polygon (POL) https://www.binance.com/en/support/announcement/6a6de383727f4659a3050f7982e1620f
Binance Adds Eurite (EURI) on Convert and “Buy Crypto” https://www.binance.com/en/support/announcement/909f18e513f848d2aa5152eb620ce0a9
Wallet Maintenance for The Open Network (TON) - 2024-08-26 https://www.binance.com/en/support/announcement/87fa32e4a1ec4da7a152bbf9d82281ed
Limited-Time Spot Trading ROI Competition - Win a Share of $100,000 in BNB Rewards and Exclusive Binance VIP Swag! https://www.binance.com/en/support/announcement/5b27b4cc75f747729185d5a335fb372d
Showing the 12 most recent of 20 posts we hold for @EarnCryptoLegits. 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.
Citation-graph rank — 999,423 of 1,151,006entries 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.
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.
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 6 August 2026 — this entry's latest reading, not the date you are reading this.
“BITMEX & BINANCE TARGET ™️” (@EarnCryptoLegits), 535 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/EarnCryptoLegits.
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.