Channel
@cryptochiefss
On this record: Growth · Engagement · What this channel posts · Posts · Telegram's recommendations · Cite this entry
28,034subscribers
-419 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001184413120 |
|---|---|
| Type | Channel |
| Username | @cryptochiefss |
| Description | The #1 Crypto Trading Community ✅ Free Daily Market Update No financial advice is given in this group. |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 29 August 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 29 August 2026 |
| On Telegram | t.me/cryptochiefss |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Aug 2026, 19:57 | 28,034 | -17 |
| 28 Aug 2026, 19:07 | 28,051 | -20 |
| 27 Aug 2026, 18:48 | 28,071 | -20 |
| 26 Aug 2026, 18:04 | 28,091 | -19 |
| 25 Aug 2026, 18:36 | 28,110 | -26 |
| 24 Aug 2026, 17:53 | 28,136 | -30 |
| 23 Aug 2026, 00:44 | 28,166 | -36 |
| 21 Aug 2026, 10:29 | 28,202 | -18 |
| 20 Aug 2026, 09:47 | 28,220 | -17 |
| 19 Aug 2026, 07:36 | 28,237 | -13 |
| 18 Aug 2026, 10:06 | 28,250 | -14 |
| 17 Aug 2026, 12:45 | 28,264 | -27 |
| 16 Aug 2026, 05:24 | 28,291 | -29 |
| 14 Aug 2026, 18:48 | 28,320 | -19 |
| 13 Aug 2026, 08:25 | 28,339 | -19 |
| 12 Aug 2026, 04:53 | 28,358 | -24 |
| 11 Aug 2026, 07:01 | 28,382 | -14 |
| 10 Aug 2026, 07:42 | 28,396 | -15 |
| 9 Aug 2026, 08:51 | 28,411 | -12 |
| 8 Aug 2026, 11:56 | 28,423 | first reading |
23 posts held, back to 18 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 50 pagesof 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 11 August 2026 |
|---|---|
| Posts held | 23 (18 July 2026 – 11 August 2026) |
| Views total | 19,880 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 30 Aug 2026, 07:51 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.
Lifetime counters from Telegram’s own channel header, read 30 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.
Market update- Bitcoin is continuing to look weak, and for this reason I prefer to play safe and have patience. It is clear that $65k+ is a huge barrier for BTC, after another rejection from here yesterday. For now $62.8k (Monday Low) is holding as support, but no strong reaction yet. If this is lost, I expect mid $62k area at least. The Monday Range this week is $65.4k - $63.8k
Market update- Bitcoin continues to have support at the $64.8k area, which is the new weekly open. The price action remains choppy, and $65k is proving to be a strong level of 4hr resistance. For now I am watching the Monday Range play out, but a 4hr close above $65.5k and the uptrend could resume with a push towards $66.9k (Prev Month High.) $64.3k area is my first level of interest for a lower retest, but just obs…
Market update- It has been another few boring days for Bitcoin, with the $65k resistance level continuing to be a barrier to further upside. At the time of writing, BTC is a few minutes from breaking this level, and if we get a good retest at $65.8k to confirm support, $65.8k will likely be next.
Market update- Bitcoin hit $65k yesterday as I expected, but there is clear 4hr resistance here just as there was this time last week. $64.3k is now a potential 4hr level that I am looking at on a retest before another attempt to break $65k. If $65k is broken on the 4hr timeframe, then we will probably see $65.8k soon after.
Market update- Bitcoin has broken out from the 2 week long 4hr downtrend and also has 4hr acceptance above $64k (Monday High). So far there has been no strong follow through from this level, but equally every 4hr close has maintained $64k as new 4hr support. There is an opportunity to try a long from this level, because as long as the Monday High is held as support then we could see BTC push towards $65k and $65.8k.…
Market update- Bitcoin has continued with strength since sweeping $62.3k (Prev Week Low Area) yesterday. This is now looking like a potential double bottom; however we can see that BTC is under a big resistance level on the 4hr timeframe. There has been no acceptance above $64k (Monday High) yet, and we are seeing a number of rejections of the 4hr downtrend which BTC has been in for a full two weeks. Watch for a 4hr…
Market update- Bitcoin continues to respect my levels- $63.5k is still strong 4hr resistance, as we expected, and this is now our weekly open level. BTC has given another retest of my long area this morning, around $63.3k, with a positive reaction so far. However, we cannot rule out a move below $62k in the short term until the resistance at $63.5k is broken. Patience for now as we watch how the Monday Range develop…
Market update- Bitcoin finally reached my Long idea at 62.3k last night, which was the level I had been waiting for since the start of the week. This has given a good reaction so far of 2%, especially considering it is the weekend. As expected, $63.5k is the 4hr resistance now so I will be watching to see if further strength enters the market around the weekly close for a potential push back towards $65k.
Market update- Not much for me to do here other than continue being patient. Frustrating that my BTC long idea missed by less than $100 yesterday, before giving a reaction, but in the process the Monday Range has been lost. My idea remain valid, but I do expect $63.5k (Monday Low) to be resistance if it is retested today, particularly because of the lower weekend volume.
Market update- After Bitcoin broke out from the 4hr downtrend (orange trendline), we can see that it rejected exactly from $65.4k (Weekly Open). Since this, the price has retraced back inside the previous downtrend, confirming deviation, and back to $65.3k (Monday Low). At the time of writing, $63.5k is holding as support. We could look to take an entry here in anticipation of the Monday Low holding and look for a …
Market update- Bitcoin is currently pushing into the 4hr downtrend resistance as shown by the orange trendline. This downtrend has been in place since early last week, so I am watching for a breakout. Confirmation of a breakout could see the price push back towards $65.7k (Monday High) once again. Another rejection from the downtrend and we could be looking to $63.5k (Monday Low) again which has been solid over the …
Market update- We have seen the Monday Low reclaim scenario play out for Bitcoin, as highlighted in yesterday's update- Once $63.5k was reclaimed on the 4hr time frame, this has been back tested to confirm new support before pushing towards the supply starting at $64.5k. We can expect BTC to continue to face resistance in this area, up towards $65k. Later today we have the FOMC interest rate decision, and the press…
Showing the 12 most recent of 23 posts we hold for @cryptochiefss. 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.
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.
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 29 August 2026 — this entry's latest reading, not the date you are reading this.
“Crypto Chiefs - @chiefrafba” (@cryptochiefss), 28,034 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/cryptochiefss.
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.