liquidations galore holy moly
🥰5🤯3🫡3😱1

Channel
@kirbycrypto
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Stars · Posts · Citations · Telegram's recommendations · Cite this entry
37,961subscribers
-3,557 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001831680966 |
|---|---|
| Type | Channel |
| Username | @kirbycrypto |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 63 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/kirbycrypto |
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 92% 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 word for word on 1 other registered channel. They sit inside a group of 3 channels that share the same post bodies with each other. 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 |
|---|---|---|---|
| @kirbycrypto/2015 · this entry30 Jul 2026, 13:40 UTC | @moecrypto/3100130 Jul 2026, 14:00 UTC | 1.00 | 20 minutes |
| @kirbycrypto/2017 · this entry31 Jul 2026, 15:38 UTC | @moecrypto/3100431 Jul 2026, 15:55 UTC | 1.00 | 18 minutes |
| @kirbycrypto/2024 · this entry3 Aug 2026, 13:02 UTC | @moecrypto/310073 Aug 2026, 13:16 UTC | 1.00 | 14 minutes |
| @kirbycrypto/2027 · this entry4 Aug 2026, 14:21 UTC | @moecrypto/310124 Aug 2026, 14:36 UTC | 1.00 | 15 minutes |
| @kirbycrypto/2028 · this entry5 Aug 2026, 02:42 UTC | @moecrypto/310155 Aug 2026, 02:57 UTC | 1.00 | 14 minutes |
| @kirbycrypto/2029 · this entry5 Aug 2026, 15:48 UTC | @moecrypto/310175 Aug 2026, 15:58 UTC | 1.00 | 11 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @moecrypto | 10 (8/8 hand-verifiable sample passed) | 1.00 | 15 minutes | this entry (10–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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 17 comparable posts for this entry, running 27 July 2026 to 6 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.
Across the whole group of 3, the earliest publisher we hold is @kirbycrypto — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 7 August 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’s posts match, word for word or near enough, posts on 2 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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 |
|---|---|---|
| 6 Nov 2026, 06:59 | 37,961 | -11 |
| 5 Nov 2026, 06:00 | 37,972 | -15 |
| 4 Nov 2026, 05:56 | 37,987 | -20 |
| 3 Nov 2026, 08:30 | 38,007 | -10 |
| 2 Nov 2026, 07:27 | 38,017 | -28 |
| 1 Nov 2026, 06:36 | 38,045 | -20 |
| 31 Oct 2026, 10:08 | 38,065 | -19 |
| 30 Oct 2026, 13:37 | 38,084 | -29 |
| 29 Oct 2026, 10:56 | 38,113 | -25 |
| 28 Oct 2026, 10:49 | 38,138 | -81 |
| 27 Oct 2026, 13:10 | 38,219 | -12 |
| 26 Oct 2026, 16:40 | 38,231 | -17 |
| 25 Oct 2026, 16:09 | 38,248 | -729 |
| 24 Oct 2026, 16:40 | 38,977 | -26 |
| 23 Oct 2026, 19:37 | 39,003 | -18 |
| 22 Oct 2026, 21:00 | 39,021 | -20 |
| 21 Oct 2026, 16:10 | 39,041 | -18 |
| 20 Oct 2026, 12:59 | 39,059 | -6 |
| 19 Oct 2026, 14:54 | 39,065 | -48 |
| 18 Oct 2026, 13:56 | 39,113 | first reading |
147 posts held, back to 27 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 174 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. It is computed over the 42 of 43 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 5 November 2026 |
|---|---|
| Posts held | 147 (27 July 2026 – 5 November 2026) |
| Views total | 84,865 |
| Reactions total | 484 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 5 Nov 2026, 22:50 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.
1,959 reactions across 125 posts, in 21 distinct kinds. The most used accounts for 49.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 964 | 49.2% | |
| 🔥 | 579 | 29.6% | |
| 😁 | 128 | 6.53% | |
| 🥰 | 45 | 2.30% | |
| 👌 | 38 | 1.94% | |
| 🤯 | 26 | 1.33% | |
| 🫡 | 26 | 1.33% | |
| 💯 | 24 | 1.23% | |
| 😱 | 20 | 1.02% | |
| 🎉 | 18 | 0.919% | |
| 🙏 | 17 | 0.868% | |
| 🤪 | 17 | 0.868% | |
| 👀 | 16 | 0.817% | |
| 👏 | 11 | 0.562% | |
| 🌚 | 8 | 0.408% | |
| custom 5972187557352443077 | 7 | 0.357% | |
| 🤔 | 5 | 0.255% | |
| 🤝 | 4 | 0.204% | |
| ✍ | 3 | 0.153% | |
| ❤🔥 | 2 | 0.102% | |
| 1 further kind | 1 | 0.051% |
Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it is Telegram’s.
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 131 of the 147 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 1,963 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 147 most recent posts we hold, published 27 July 2026 to 5 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @kirbycrypto. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 147 most recent posts we hold for this entry, published 27 July 2026 to 5 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Telegram’s own ‘edited’ marker: 11 of 43 posts held from the last 30 days (25.6%) 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).
liquidations galore holy moly
🥰5🤯3🫡3😱1
Posted without readable text
❤3
Signed Kirby Crypto Grok
Posted without readable text
❤4
Signed Kirby Crypto Grok
November 3, 2026 📰 Headlines • Hyperliquid co-founder Jeff Yan told Bloomberg he wants to break into the US market and sees high-quality tokenized stocks and RWAs as the next frontier. • Trade.xyz restored its GitBook docs after unauthorized changes and warns users not to click any links in them while it investigates. • Banana Gun is coming to Kinetiq's Elysium L2 and has committed 40% of net trading revenue to KNTQ…
❤4
APEX second vault deposits are open INFINIT is building the platform and standards for institutional-grade trading vaults, and APEX is its first vault, run by the APEX team. APEX 1 track record: 41% annualized return 3.7% max drawdown INFINIT trades Hyperliquid perps, so if you're on Hyperliquid and want exposure to a managed strategy instead of trading yourself, this one's worth a look. Link to vault Deposits c…
🔥2
November 2, 2026 📰 Headlines • Entropy's HIP-3 perp markets on Hyperliquid passed $100M in open interest. • Elliptic says 44% of the $6.4B stolen from Binance, about $2.85B, is now frozen or seized, while the hacker has started using CoinJoin. • THORChain halted swaps on 10 chains after an Ethereum reorg made a vault pay out 10 ETH it never received, which the user has since returned. • BTCPay Server told users to s…
❤6
October 31, 2026 📰 Headlines • Grayscale says Hyperliquid made about $105M in September revenue, with non-core income like third-party markets and USDC yield doubling year over year to $38M. • ICE reposted its trade[XYZ] announcement with softer wording, now saying it plans to bring Hyperliquid perps to the US subject to regulatory approvals. • Binance found a wider breach behind its $6.3B hack and is targeting a Su…
❤4✍1
October 30, 2026 📰 Headlines • Stan Druckenmiller used his first-ever X post to say he invested in trade[XYZ], backing its ICE deal to bring Hyperliquid perps to the US. • Trade[XYZ] listed a 24/7 ICE stock perp on Hyperliquid with up to 10x leverage. • Binance says a roughly $6.3B hack, likely starting from a compromised DevOps engineer's laptop (do you even believe this nonsense lol) • Aave froze its V3 and V4 mar…
❤2
$5.8B. Let that sink in. That's roughly 4x the Bybit hack, which was the largest crypto hack ever until now. Heart goes out to those who watched the hardware wallet exploits, moved their funds to a CEX to feel safe, and then got caught in a CEX hack anyway. Hopefully binance covers user losses Trust in this industry is chipping away a little every day and that's really sad to see. I don't really have any hope in t…
❤32🙏1
What in the world did we (Asia) just wake up to Thank God I have exactly ($0) in binance
😁12🔥4
newly revamped website for hypurrco check it out - hypurr.co https://x.com/hypurr_co/status/2115851316971061329
🔥16❤3
1) what
❤22🔥6
Showing the 12 most recent of 147 posts we hold for @kirbycrypto. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 30 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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 27 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“Kirby Crypto” (@kirbycrypto), 37,961 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/kirbycrypto.
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.