Channel
@CryptoChiefsFree
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Posts · Telegram's recommendations · Cite this entry
915subscribers
-109 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001842939201 |
|---|---|
| Type | Channel |
| Username | @CryptoChiefsFree |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 10 November 2026 |
| On Telegram | t.me/CryptoChiefsFree |
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 19 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 the other topics.
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 in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. 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 |
|---|---|---|---|
| @cryptochiefss/963223 Jul 2026, 12:01 UTC | @CryptoChiefsFree/4666 · this entry23 Jul 2026, 12:01 UTC | 1.00 | under a minute |
| @cryptochiefss/963425 Jul 2026, 09:47 UTC | @CryptoChiefsFree/4668 · this entry25 Jul 2026, 10:02 UTC | 1.00 | 15 minutes |
| @cryptochiefss/964031 Jul 2026, 10:22 UTC | @CryptoChiefsFree/4674 · this entry31 Jul 2026, 10:37 UTC | 1.00 | 15 minutes |
| @cryptochiefss/96411 Aug 2026, 08:35 UTC | @CryptoChiefsFree/4675 · this entry1 Aug 2026, 08:37 UTC | 1.00 | 2 minutes |
| @cryptochiefss/96422 Aug 2026, 09:51 UTC | @CryptoChiefsFree/4676 · this entry2 Aug 2026, 09:52 UTC | 1.00 | under a minute |
| @cryptochiefss/96433 Aug 2026, 11:05 UTC | @CryptoChiefsFree/4677 · this entry3 Aug 2026, 11:07 UTC | 1.00 | 2 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @cryptochiefss | 20 (8/8 hand-verifiable sample passed) | 1.00 | 6 minutes | @cryptochiefss (20–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. 4 of the 20 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 20 comparable posts for this entry, running 21 July 2026 to 11 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.
Of the group of 2 channels, the one whose matching posts we hold earliest is @cryptochiefss. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, last confirmed 11 November 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 is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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 |
|---|---|---|
| 10 Nov 2026, 09:45 | 915 | -12 |
| 2 Nov 2026, 14:07 | 927 | -7 |
| 26 Oct 2026, 02:08 | 934 | -4 |
| 20 Oct 2026, 01:40 | 938 | -9 |
| 13 Oct 2026, 21:10 | 947 | -6 |
| 3 Oct 2026, 23:40 | 953 | -14 |
| 19 Sept 2026, 15:39 | 967 | -9 |
| 11 Sept 2026, 20:22 | 976 | -11 |
| 2 Sept 2026, 15:03 | 987 | -12 |
| 25 Aug 2026, 21:34 | 999 | -6 |
| 23 Aug 2026, 03:42 | 1,005 | -5 |
| 19 Aug 2026, 10:19 | 1,010 | -3 |
| 16 Aug 2026, 18:03 | 1,013 | -9 |
| 12 Aug 2026, 18:43 | 1,022 | -2 |
| 12 Aug 2026, 10:46 | 1,024 | first reading |
20 posts held, back to 21 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 1 page of 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 11 August 2026. An engagement rate over an empty window would be a number about nothing.
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 20 posts we hold for @CryptoChiefsFree. 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 2 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 10 November 2026 — this entry's latest reading, not the date you are reading this.
“Crypto Chiefs Updates” (@CryptoChiefsFree), 915 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/CryptoChiefsFree.
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.