$BTC just cleaned out $72K Massive cluster sitting at $82K above Price doesn't leave liquidity on the table @Nakamoto_Signals
🐳24👍8💯5⚡4🔥4👀3❤2

Channel
@Nakamoto_Signals
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
74,287subscribers
+9,747 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001454159481 |
|---|---|
| Type | Channel |
| Username | @Nakamoto_Signals |
| Description | Precision over prediction. Structure over emotion. We analyze liquidity, momentum shifts and market structure to build high-probability trade scenarios. Admin: @AlanSignalDirector / @web3John https://www.bitunix.com/register?vipCode=NakamotoSignals |
| Created | Between 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 November 2026 |
| Measurements held | 64 |
| Confirmed unchanged | 1 time, most recently 12 November 2026 |
| On Telegram | t.me/Nakamoto_Signals |
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 10 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.
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 2 other registered channels. 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 |
|---|---|---|---|
| @Nakamoto_Signals/11806 · this entry11 Aug 2026, 10:21 UTC | @Bitunix_Trades/357111 Aug 2026, 10:21 UTC | 0.95 | under a minute |
| @Nakamoto_Signals/11821 · this entry17 Aug 2026, 06:49 UTC | @Bitunix_Trades/358517 Aug 2026, 06:50 UTC | 0.95 | under a minute |
| @Nakamoto_Signals/11844 · this entry24 Aug 2026, 08:05 UTC | @Bitunix_Trades/360624 Aug 2026, 08:05 UTC | 0.95 | under a minute |
| @Bitunix_Trades/359921 Aug 2026, 13:40 UTC | @Nakamoto_Signals/11836 · this entry21 Aug 2026, 13:40 UTC | 0.93 | under a minute |
| @Nakamoto_Signals/11848 · this entry25 Aug 2026, 13:20 UTC | @Bitunix_Trades/361025 Aug 2026, 13:20 UTC | 0.93 | under a minute |
| @Nakamoto_Signals/11897 · this entry7 Sept 2026, 17:10 UTC | @Bitunix_Trades/36817 Sept 2026, 18:20 UTC | 0.93 | 70 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @Bitunix_Trades | 23 (8/8 hand-verifiable sample passed) | 0.93 | under a minute | @Bitunix_Trades (13–10) |
| @ChartsSignalsTrading | 10 (8/8 hand-verifiable sample passed) | 0.93 | 72 seconds | @ChartsSignalsTrading (8–2) |
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. 17 of the 21 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 205 comparable posts for this entry, running 30 July 2026 to 11 November 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.
Recorded under the keys clone_copy · clone_mutual, last confirmed 12 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Nov 2026, 06:09 | 74,287 | +778 |
| 10 Nov 2026, 01:29 | 73,509 | +893 |
| 8 Nov 2026, 12:58 | 72,616 | +160 |
| 7 Nov 2026, 08:01 | 72,456 | -759 |
| 6 Nov 2026, 06:49 | 73,215 | -501 |
| 5 Nov 2026, 07:26 | 73,716 | +1,374 |
| 4 Nov 2026, 05:38 | 72,342 | -411 |
| 3 Nov 2026, 03:51 | 72,753 | -101 |
| 2 Nov 2026, 02:28 | 72,854 | -799 |
| 1 Nov 2026, 04:27 | 73,653 | -871 |
| 31 Oct 2026, 07:21 | 74,524 | +596 |
| 30 Oct 2026, 09:56 | 73,928 | +882 |
| 29 Oct 2026, 10:36 | 73,046 | +844 |
| 28 Oct 2026, 07:51 | 72,202 | -674 |
| 27 Oct 2026, 08:44 | 72,876 | -182 |
| 26 Oct 2026, 09:49 | 73,058 | +3,805 |
| 25 Oct 2026, 06:39 | 69,253 | +1,504 |
| 24 Oct 2026, 08:44 | 67,749 | +797 |
| 23 Oct 2026, 06:29 | 66,952 | -1,208 |
| 22 Oct 2026, 04:11 | 68,160 | first reading |
267 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 196 pages of 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 12 November 2026 |
|---|---|
| Posts held | 267 (30 July 2026 – 12 November 2026) |
| Views total | 438,218 |
| Reactions total | 2,241 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Nov 2026, 19:59 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 12 November 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.
Measured directly from 56 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
9,276 reactions across 155 posts, in 11 distinct kinds. The most used accounts for 13.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1,223 | 13.2% | |
| 👍 | 1,223 | 13.2% | |
| 🔥 | 1,199 | 12.9% | |
| 💯 | 1,192 | 12.9% | |
| 🏆 | 1,023 | 11.0% | |
| ⚡ | 1,006 | 10.8% | |
| 🐳 | 874 | 9.42% | |
| 👀 | 747 | 8.05% | |
| 😱 | 306 | 3.30% | |
| 😍 | 256 | 2.76% | |
| 👏 | 227 | 2.45% |
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 155 of the 267 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 9,276 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 267 most recent posts we hold, published 30 July 2026 to 12 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.
Telegram’s own ‘edited’ marker: 1 of 45 posts held from the last 30 days (2.22%) 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).
$BTC just cleaned out $72K Massive cluster sitting at $82K above Price doesn't leave liquidity on the table @Nakamoto_Signals
🐳24👍8💯5⚡4🔥4👀3❤2
BREAKING: 🇺🇸 $5 TRILLION JPMORGAN JUST REVEALED A $47,000,000 PURCHASE OF #BITCOIN THEY NOW HOLD OVER $539,000,000 WORTH OF BTC JAMIE DIMON FINALLY SURRENDERED TO BITCOIN 🔥 @Nakamoto_Signals
👍14💯9❤8🐳7👀5🔥3⚡2🏆2
$BTC Final flush done What comes next is going to hurt the people who sold Get ready for HUGE PUMP @Nakamoto_Signals
❤22🐳16👍5👀3💯3🏆2
The same dip you fear today could be the one you wish you had bought. @Nakamoto_Signals
👀13🏆9💯9⚡7🐳5👍3❤2🔥2
One day, the world will realize Bitcoin was inevitable. Most will pretend nobody warned them. The writing was on the wall—they just looked away. @Nakamoto_Signals
🔥24👍7🏆6👀5🐳3💯3❤2
This cluster so FUCKING BIG If you think $BTC will ignore it, you're wrong @Nakamoto_Signals
👀14🏆11👍9🔥6❤5⚡4🐳1
Final Flush finally DONE Get ready for this HUGE $BTC MOVE This will trigger the biggest bull run ever @Nakamoto_Signals
🏆14💯8⚡7🐳6👍6🔥6❤2👀1
THE COVID CRASH TRIGGERED THE GREATEST CRYPTO BULL RUN EVER. AND AFTER 12 MONTHS OF PURE FUCKING PAIN, I’M MORE BULLISH THAN I’VE EVER BEEN. I’M PREDICTING A REVERSAL THAT WILL CATCH THE ENTIRE MARKET OFF GUARD. BITCOIN IS ABOUT TO BREAK ABOVE ITS PREVIOUS ALL-TIME HIGHS. @Nakamoto_Signals
❤19🐳8👍8⚡6🔥6👀2💯1
YOUR NEXT TRADING MOVE STARTS HERE. Still trading without exploring all your options? Meet Bitunix, a global cryptocurrency exchange built for traders who want access to the crypto markets without unnecessary complications. Whether you’re trading Bitcoin, hunting for altcoin opportunities or exploring futures markets, Bitunix gives you a platform to put your trading strategy into action. https://www.bitunix.com/r…
💯12🏆11👀10⚡5👍5🐳3🔥3❤1
$1.3B in short liquidations at $79,000. $400M in long risk down to $72,000. The risk is heavily stacked against the bears. @Nakamoto_Signals
❤12🏆12🔥11👀7⚡4🐳2👍2
MASSIVE: 🇺🇸 $2.1 TRILLION added to US stocks today. Everyone made money except the guy who got caught. @Nakamoto_Signals
🔥20💯12👀8🏆7❤2⚡1
$500B banking giant Barclays bought Bitcoin ETFs in Q3, bringing its holdings to $190M. Also increased Strategy $MSTR position to $120M. @Nakamoto_Signals
🏆23🐳7🔥5❤4👍4💯4⚡3
Showing the 12 most recent of 267 posts we hold for @Nakamoto_Signals. 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.
Named by 6 registered channels — 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
@Nakamoto_Signals named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 12 November 2026 — this entry's latest reading, not the date you are reading this.
“Nakamoto Signals” (@Nakamoto_Signals), 74,287 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/Nakamoto_Signals.
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.