💊 TOTAL3 is losing the 200-Week MA This is bad. VERY BAD Be mentally prepared for capitulation

Channel
Cryptomadness 📉
@cryptomadnessofficially
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Cite this entry
261,536subscribers
-54,744 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
Register entry
| Telegram ID | -1002050135069 |
|---|---|
| Type | Channel |
| Username | @cryptomadnessofficially |
| Description | manager @greenlandmanager @tocatcrypto |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 November 2026 |
| Measurements held | 66 |
| Confirmed unchanged | 1 time, most recently 18 November 2026 |
| On Telegram | t.me/cryptomadnessofficially |
Topic
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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Nov 2026, 01:47 | 261,536 | -1,550 |
| 14 Nov 2026, 22:47 | 263,086 | -1,601 |
| 11 Nov 2026, 21:16 | 264,687 | -942 |
| 9 Nov 2026, 20:56 | 265,629 | -664 |
| 8 Nov 2026, 13:39 | 266,293 | -784 |
| 7 Nov 2026, 04:01 | 267,077 | -492 |
| 6 Nov 2026, 06:18 | 267,569 | -503 |
| 5 Nov 2026, 08:28 | 268,072 | -643 |
| 4 Nov 2026, 10:57 | 268,715 | -275 |
| 3 Nov 2026, 13:07 | 268,990 | -540 |
| 2 Nov 2026, 14:46 | 269,530 | -495 |
| 1 Nov 2026, 13:36 | 270,025 | -720 |
| 31 Oct 2026, 14:27 | 270,745 | -525 |
| 30 Oct 2026, 14:34 | 271,270 | -615 |
| 29 Oct 2026, 13:37 | 271,885 | -734 |
| 28 Oct 2026, 12:20 | 272,619 | -419 |
| 27 Oct 2026, 10:39 | 273,038 | -830 |
| 26 Oct 2026, 10:49 | 273,868 | -243 |
| 25 Oct 2026, 11:31 | 274,111 | -322 |
| 24 Oct 2026, 15:06 | 274,433 | first reading |
Engagement
56 posts held, back to 28 April 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 210 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 2.42%
- avg views ÷ 261,536 subscribers
- Avg views / post
- 6,330
- 29 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 29
- of 56 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.
| Window | Rolling 30 days · latest post in window 16 November 2026 |
|---|---|
| Posts held | 56 (28 April 2026 – 16 November 2026) |
| Views total | 183,514 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 18 Nov 2026, 03:36 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
- 243
- Videos
- 4
- Links
- 100
Lifetime counters from Telegram’s own channel header, read 18 November 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.
Reaction mix
22 reactions across 6 posts, in 3 distinct kinds. The most used accounts for 68.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 15 | 68.2% | |
| 🤝 | 4 | 18.2% | |
| 💊 | 3 | 13.6% |
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 6 of the 56 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 22 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 56 most recent posts we hold, published 28 April 2026 to 16 November 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.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 29 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
💊 If July 1st ($57,750) was the bear market bottom, then it was the shortest $BTC bear market But don't write off the bears just yet, they still have enough time to fight back: October 4th would match the 2018 bear market bottom October 17th would…Time to return to this post
💊 $BTC 1D update PERFECT! We just made a Higher High exactly as I expected I'd like to be wrong, but in my opinion this is the final pump before the 2-month correction I had $68k as the bottom for this 2-month correction (that I perfectly called a month before it even started)But I don't like that $BTC lost the 200-Day MA The 200-Week MA is our last hope
💊 What I’m watching closely right now is this potential inverse Head & Shoulders on the $SUI daily chart Breakout Target would be $2.2-2.5You can buy this $SUI dip with me on Bybit https://partner.bybit.com/b/cryptobullet Up to 30,000 USDT Welcome Bonus for new users when they register, deposit & trade!
💊 NASDAQ chose $PYTH for real-time market data That's why I'm still bullish on $PYTH NYSE picked PythNetwork to distribute its real-time equity data, NYSE BQT.Nasdaq joined back in late September, so now two of the biggest stock exchanges send live data through Pyth $PYTH
💊 $ETH 1W chart $ETH has lost the 200-Week MA confirming a mid-term correction Buy The Dip Zone: $2000-2300 $ETH has reached the 0.618 Fib level Regardless of where it goes next, not buying some spot $ETH here is a mistake
💊 I don't know about you guys, but I'm not gonna miss this entry on Bitcoin I've started buying heavilyOn this day 4 years ago
💊 $BTC The price of Bitcoin has fallen to an important support zone: there is dynamic support here, as well as the 0.5 Fibonacci level. There’s a high probability that buyers will step in actively at this level, so you can buy for the medium term (spot) or look for an entry point for a long position (futures). Later, we’ll see what’s happening with the top altcoins.
💊 $CRV 1M chart I really like that $CRV held the August 2024 low and printed a giant Double Bottom in June 2026IMO $CRV will easily reach major Resistance at $1.30 The Target of the Double Bottom is $6 ($15B FDV)
💊 $SUI 1M chart Highest Monthly Close since December 2025! Highest Monthly Volume since November 2024! $SUI looks so strong A dip to $0.9-1 would be welcome (not guaranteed, but if it happens, don't hesitate to pull the trigger) A new ATH is coming anyway…$SUI 1M update We got the pullback that I was talking about, the monthly candle closed right at my $0.9 horizontal level I believe the current month will also close…
💊 Why I'm bullish on $PYTH for this bull cycleAnother month of domination for $PYTH It priced $734B (88.5%) of the rwa perp volume in October. Way ahead of the rest
💊 The main reason why I'm not going to buy $MON for the 2027-2029 Bull RunThis month $MON has ~17B new tokens unlocking in one hit Supply will more than double in one day!The price is already losing its vital Support
Showing the 12 most recent of 56 posts we hold for @cryptomadnessofficially. 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.
Posts recorded as deleted after publishing
We recorded 1 post on @cryptomadnessofficially as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
- First seen missing
- 21 October 2026
- Most recent seen missing
- 21 October 2026
- Median time before seen missing
- 20 hours
- Seen missing in the last 30 days
- 1
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 18 November 2026 — this entry's latest reading, not the date you are reading this.
“Cryptomadness 📉” (@cryptomadnessofficially), 261,536 subscribers as measured 18 November 2026. Telegram Register, tgregister.com/channel/cryptomadnessofficially.
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.