NEAR Long Setup I’m looking for NEAR longs if price pulls back into the $1.75–$1.78 zone. This area acted as previous resistance and has now been reclaimed, so I’m watching for it to hold as support on the 4H. If we get a clean reaction from this zone, I’ll be looking for continuation back towards $1.95–$2.00, with $2.10–$2.15 as the main upside target.

Channel
CRYPTOMOJO_TA
@CRYPTOMOJO_TA
On this record: Topic · Growth · Engagement · Posts · Telegram's recommendations · Cite this entry
8,628subscribers
+1,255 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001667921924 |
|---|---|
| Type | Channel |
| Username | @CRYPTOMOJO_TA |
| 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 | 16 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/CRYPTOMOJO_TA |
Topic
Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 11 September 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 20:37 | 8,628 | -66 |
| 12 Sept 2026, 15:57 | 8,694 | -84 |
| 8 Sept 2026, 14:58 | 8,778 | -107 |
| 3 Sept 2026, 13:19 | 8,885 | -54 |
| 31 Aug 2026, 11:53 | 8,939 | -123 |
| 28 Aug 2026, 02:33 | 9,062 | -26 |
| 25 Aug 2026, 12:11 | 9,088 | -59 |
| 22 Aug 2026, 11:27 | 9,147 | -112 |
| 18 Aug 2026, 21:55 | 9,259 | +2,808 |
| 16 Aug 2026, 02:18 | 6,451 | -659 |
| 12 Aug 2026, 20:56 | 7,110 | -66 |
| 10 Aug 2026, 07:28 | 7,176 | -182 |
| 7 Aug 2026, 13:13 | 7,358 | -15 |
| 7 Aug 2026, 04:30 | 7,373 | first reading |
Engagement
62 posts held, back to 30 July 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 24 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 3.05%
- avg views ÷ 8,628 subscribers
- Avg views / post
- 263
- 5 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 5
- of 62 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 26 August 2026 |
|---|---|
| Posts held | 62 (30 July 2026 – 26 August 2026) |
| Views total | 1,314 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Aug 2026, 15:29 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.
Recent posts
https://x.com/CRYPTOMOJO_TA/status/2092559935150469550?s=20
SUSHI Update SUSHI has broken out of its long-term descending channel and reclaimed the 200 EMA, signaling improving bullish momentum. Now, I'd like to see a successful retest of the breakout zone. If it holds, the rally could continue toward the next major resistance. Patience is key, and the breakout confirm before chasing the move.
GOLD LONG SETUP I’m looking for longs on Gold here around $4,640–$4,642. Price has started breaking the short-term structure to the upside, and I’m looking for this area to hold as support before continuation higher. Entry: $4,640–$4,642 Stop Loss: $4,616.59 TP1: $4,650 TP2: $4,675 TP3: $4,696–$4,697 Main target is the previous high around $4,696. As long as this breakout area holds, I’m expecting Gold to continu…
Resistance is holding very well. Volume is also decreasing as BTC approaches this zone. Looks like a rejection could be on the cards. Let’s see. https://www.tradingview.com/chart/BTCUSDT/NDR33XAA-BTC-Faces-a-Make-or-Break-Zone-at-77-8K/
BTC is currently trading around $77.8K and has reached a major resistance zone that also lines up with the long-term descending trendline. This is a very strong resistance area and won't be easy to break. On top of that, the RSI is already in the overbought zone, suggesting that buying momentum may be getting exhausted. For now, I'd rather wait for confirmation than chase the move. A strong daily close above this res…
https://x.com/CRYPTOMOJO_TA/status/2091800042403209358?s=20
#update OIL Short Watch Looking for a short on OIL here on the 4H timeframe. Price is testing this bullish FVG around the $85 area, so I’m waiting for confirmation before entering. If we get a 4H close below the FVG, I think we have a pretty clean short setup back down towards the $78 area. For now, just waiting for that 4H confirmation before taking the trade.
#Ethereum Update Ethereum has rallied straight into a major resistance zone around $2,400–2,450, an area that has repeatedly rejected price in the past and won't be easy to break. The rally has been strong, but price is now testing one of the most important resistance levels on the chart while RSI is entering overbought territory, increasing the chances of a short-term pullback. For now, I wouldn't chase longs at t…
$FARTCOIN Profit Update 🚀 As expected, $FARTCOIN broke out of the descending trendline and hit the $0.17 area. That’s around 45%+ profit from our setup. https://x.com/CRYPTOMOJO_TA/status/2090797125693215022?s=20
$ENA Update 🚀 As expected, $ENA broke the long-term trendline and delivered 70%+ profit from our setup. Still holding. Let’s see how far it goes! https://x.com/CRYPTOMOJO_TA/status/2090795779036483803?s=20
USDT.D Update USDT Dominance is coming into a key support zone around the 7% area after a pretty aggressive move lower. This is an important area to watch because if USDT.D starts finding support and reversing from here, we could see some weakness or a short-term reversal across the altcoin market. Alts have benefited from this drop in dominance, but with USDT.D now reaching support, I’d be a little more cautious …
Showing the 12 most recent of 62 posts we hold for @CRYPTOMOJO_TA. 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.
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.
@hexatrades · 22,355
Telegram ranks this channel #17 of 90 here — alongside 89 others — read 21 September 2026
@gurumengajar · 134,410
Telegram ranks this channel #33 of 53 here — alongside 52 others — read 27 August 2026
@RLindaTrade · 27,097
Telegram ranks this channel #54 of 77 here — alongside 76 others — read 11 September 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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“CRYPTOMOJO_TA” (@CRYPTOMOJO_TA), 8,628 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/CRYPTOMOJO_TA.
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.