Channel
@crypto_leaksss
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Posts · Citations · Cite this entry
1,370subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001706091401 |
|---|---|
| Type | Channel |
| Username | @crypto_leaksss |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/crypto_leaksss |
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 1 other registered channel. They sit inside a group of 3 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 |
|---|---|---|---|
| @WhalesHuntersOfficial/738710 May 2026, 18:02 UTC | @crypto_leaksss/6445 · this entry10 May 2026, 18:02 UTC | 1.00 | under a minute |
| @crypto_leaksss/6451 · this entry10 May 2026, 20:02 UTC | @WhalesHuntersOfficial/739710 May 2026, 20:02 UTC | 1.00 | under a minute |
| @crypto_leaksss/6453 · this entry11 Jun 2026, 19:01 UTC | @WhalesHuntersOfficial/740011 Jun 2026, 19:01 UTC | 1.00 | under a minute |
| @WhalesHuntersOfficial/740215 Jul 2026, 18:53 UTC | @crypto_leaksss/6454 · this entry15 Jul 2026, 18:53 UTC | 1.00 | under a minute |
| @WhalesHuntersOfficial/740321 Jul 2026, 16:01 UTC | @crypto_leaksss/6455 · this entry21 Jul 2026, 16:01 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @WhalesHuntersOfficial | 5 (5/5 hand-verifiable sample passed) | 1.00 | under a minute | @WhalesHuntersOfficial (5–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 5 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 10 May 2026 to 6 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 3, the earliest publisher we hold is @WhalesHuntersOfficial. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, 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 2 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 01:47 | 1,370 | -2 |
| 11 Aug 2026, 00:01 | 1,372 | +1 |
| 7 Aug 2026, 13:40 | 1,371 | -1 |
| 7 Aug 2026, 05:16 | 1,372 | no change |
| 7 Aug 2026, 05:03 | 1,372 | first reading |
20 posts held, back to 10 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 1 pageof 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.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 20 (10 May 2026 – 6 August 2026) |
| Views total | 230 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 05:16 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.
#BTC Market Analysis August has always been one of BTC's most unpredictable months, with the median return sitting at -6.99% even though the average leans slightly positive. Translation: when August turns red, it tends to turn red hard, with 2022 at -13.88%, 2018 at -9.27%, and 2015 at -18.67% as the reminders nobody wants to remember. This doesn't mean a dump is guaranteed, but the historical pattern favors cautio…
📌 SIGNAL ID: #B330 COIN: #DOT/USDT (3-5x) Direction: LONG | Type: Swing ➖➖➖➖➖➖➖ ENTRY: 0.846 - 0.850 TARGETS: 0.880 - 0.915 - 0.955 - 1.000 - 1.060 - 1.120 - 1.180 - 1.250 STOP LOSS: 0.785 DOT reclaimed the 0.840–0.850 demand zone with a strong 6H impulse, confirming a bullish structure flip off the ascending trendline support built from the late-June lows. Momentum is building as price pushes back above 0.855 after…
📌 SIGNAL ID: #B329 COIN: #ONDO/USDT (3-5x) Direction: LONG | Type: Swing ➖➖➖➖➖➖➖ ENTRY: 0.328 - 0.329 TARGETS: 0.342 - 0.356 - 0.375 - 0.400 - 0.425 - 0.450 STOP LOSS: 0.300 ONDO reclaimed the 0.3220–0.3280 demand zone with a strong 4H impulse candle, confirming a bullish structure flip off the ascending trendline support. Momentum is building as price snaps back above the 0.3365 level after tagging the rising trend…
📌 SIGNAL ID: #B328 COIN: #ATOM/USDT (3-5x) Direction: LONG | Type: Swing ➖➖➖➖➖➖➖ ENTRY: 1.89 - 1.90 TARGETS: 1.95 - 2.00 - 2.07 - 2.17 - 2.30 - 2.50 STOP LOSS: 1.75 ATOM reclaimed the 1.820–1.838 demand zone with a strong 8H impulse, confirming a bullish structure flip. Momentum is building with price already pushing toward 1.983. Key level to watch: hold above 1.900 on any retest to keep the move toward 2.500 valid…
#LTC Market Analysis LTC/USDT is trading at 42.48 on the 8h after a steep multi-week breakdown from the 61.00 highs, with price now stabilizing just above the descending trendline drawn from the February swing low near 45.00. The recent flush to 40.80 tagged this long-term trendline before bouncing, with the 41.00 to 43.00 area now forming a tight base as sellers and buyers contest the broader structure. Bull case:…
📌 SIGNAL ID: #B327 COIN: #ATOM/USDT (3-5x) Direction: LONG | Type: Swing ➖➖➖➖➖➖➖ ENTRY: 2.03 - 2.04 TARGETS: 2.05 - 2.07 - 2.10 - 2.13 - 2.19 STOP LOSS: 1.96 ATOM shows a clean bullish alignment with the daily trend and 4H structure both positive, supported by an EMA ribbon stacked upward. MACD just crossed bullish with increasing momentum, while RSI nears overbought but still room to run. Key level to watch: hold a…
#APT Market Analysis APT/USDT is in a strong bullish trend, trading near the upper Bollinger Band with MACD confirming upward momentum. RSI above 77 signals overbought conditions but supports sustained strength for now. Bull case: hold above 1.0024 to target the next resistance at 1.0597. Bear case: lose 0.9783 and risk a deeper pullback toward key support at 0.9633. Watch 1.0024 closely for the next directional mov…
#UNI Market Analysis UNI/USDT is in a strong bullish trend, trading near the upper Bollinger Band with RSI above 75, signaling overbought momentum but sustained strength. MACD remains bullish, confirming upward pressure despite the stretched conditions. Hold above 3.44 to target fresh highs around 3.50 and beyond. Bear case triggers if price drops below 3.27, risking a pullback to key supports near 3.21. Watch 3.44 …
#SEI Market Analysis SEI/USDT showing strong bullish momentum with price near the upper Bollinger Band and MACD confirming upward trend. RSI above 76 signals overbought conditions but doesn't negate short-term strength. Holding above 0.0591 supports continuation toward resistance at 0.0620. Bear case triggers below 0.0585, risking a deeper pullback to key supports near 0.0579. Watch 0.0591 as the pivot for bulls and…
#SUI Market Analysis SUI/USDT shows strong bullish momentum with price riding near the upper Bollinger Band and MACD confirming the uptrend. RSI is overbought at 86.6, signaling potential short-term exhaustion but not a reversal yet. Holding above 0.961 supports continuation toward the 1.003 resistance target. If price drops below 0.926, watch for increased selling pressure risking a deeper pullback to 0.916. Mainta…
#SOL Market Analysis SOL/USDT shows strong bullish momentum with price near the upper Bollinger Band and MACD confirming upward strength. RSI is heavily overbought at 81, signaling potential short-term exhaustion despite the uptrend. Key supports at 92.76 and 87.94 provide solid floors for continuation. Bull case: Hold above 92.76 to target 100+ as momentum remains intact. Bear case: Lose 87.94 and risk a pullback …
📌 SIGNAL ID: #B326 COIN: #SUI/USDT (3-5x) Direction: LONG | Type: Swing ➖➖➖➖➖➖➖ ENTRY: 1.32 - 1.33 TARGETS: 1.35 - 1.37 - 1.41 - 1.46 - 1.54 STOP LOSS: 1.28 SUI/USDT confirms a bullish breakout on the 4H with volume surge and EMA ribbon alignment supporting the daily uptrend. MACD bullish cross with rising momentum and RSI near overbought signals strong continuation potential. Enter 1.32-1.33, watch key support at 1…
Showing the 12 most recent of 20 posts we hold for @crypto_leaksss. 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 — 725,922 of 1,480,688entries 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.
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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“FREE Bitcoin Bullets Vip DRVKICH” (@crypto_leaksss), 1,370 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/crypto_leaksss.
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.