Channel
@bykaranteli_com
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Telegram's recommendations · Cite this entry
121,189subscribers
-6,077 since we began measuring on 16 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
| Telegram ID | -1002076688575 |
|---|---|
| Type | Channel |
| Username | @bykaranteli_com |
| Description | The crypto futures terminal trained to be honest. Every signal is rule-bound. Every outcome is logged. Every metric is post-fee. ByKaranteli publishes its live track record, not a backtest, not marketing copy. https://bykaranteli.com |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 16 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 19 |
| Confirmed unchanged | 1 time, most recently 9 September 2026 |
| On Telegram | t.me/bykaranteli_com |
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 16 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 13:35 | 121,189 | -947 |
| 6 Sept 2026, 04:38 | 122,136 | -491 |
| 4 Sept 2026, 01:01 | 122,627 | -298 |
| 2 Sept 2026, 18:05 | 122,925 | -298 |
| 1 Sept 2026, 16:04 | 123,223 | -386 |
| 31 Aug 2026, 14:53 | 123,609 | -262 |
| 30 Aug 2026, 12:43 | 123,871 | -296 |
| 29 Aug 2026, 09:54 | 124,167 | -251 |
| 28 Aug 2026, 08:04 | 124,418 | -265 |
| 27 Aug 2026, 04:38 | 124,683 | -245 |
| 26 Aug 2026, 02:16 | 124,928 | -244 |
| 25 Aug 2026, 03:24 | 125,172 | -346 |
| 23 Aug 2026, 16:49 | 125,518 | -455 |
| 22 Aug 2026, 01:34 | 125,973 | -368 |
| 20 Aug 2026, 17:48 | 126,341 | -175 |
| 19 Aug 2026, 16:45 | 126,516 | -241 |
| 18 Aug 2026, 17:03 | 126,757 | -257 |
| 17 Aug 2026, 18:35 | 127,014 | -252 |
| 16 Aug 2026, 19:45 | 127,266 | first reading |
700 posts held, back to 15 August 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 49 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 28 of 699 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 9 September 2026 |
|---|---|
| Posts held | 700 (15 August 2026 – 9 September 2026) |
| Views total | 33,888 |
| Reactions total | 27 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Sept 2026, 04:55 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 10 September 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.
27 reactions across 27 posts, in 4 distinct kinds. The most used accounts for 88.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 24 | 88.9% | |
| ⚡ | 1 | 3.70% | |
| 👎 | 1 | 3.70% | |
| 🤝 | 1 | 3.70% |
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 28 of the 700 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 27 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 700 most recent posts we hold, published 15 August 2026 to 9 September 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.
Across $SOL, $ETH and $BTC, total long open interest was $67.5M and total short open interest was $20.2M, with the JLP pool at $851.8M. The most utilised market was $SOL short at 57.8% utilisation with a 0.0006% hourly borrow rate.
Data wrap 2026-09-09. Liquidations recorded in 24h: $203.6M (longs $123.8M, shorts $79.8M, 76,759 events, most in $BTC at $46.5M; largest single print $4.0M on $BTC). Perp open interest across 25 venues: $72.84B (-1.06% vs 24h earlier), DEX share 14.1%. US spot BTC ETFs, settled 2026-09-08: -$46.6M net; ETH ETFs -$24.3M. Hyperliquid top-300 whales: 38% of notional long across 82 accounts. Largest $BTC resting wal…
Layer 1 led the last 24 hours at +1.92% and DePIN lagged at -2.33%. Over 30 days, DeFi beat $BTC by 36.4 percentage points, Layer 2 by 11.6, Meme by 11.5, RWA by 9.4, AI by 6.3, DePIN by 2.6, Quantum by 1.2, and Layer 1 by 1.2.
BTC dominance is 58.39%, so capital is still concentrated in $BTC as risk off consolidation and the tape is waiting. Without a 24h delta, rotation cannot be confirmed; a sustained move lower in BTC dominance alongside a firm rise in $ETH dominance from 11.21% would be the condition that would confirm capital rotating toward alts.
Fear and Greed sits at 66, down 3 in 24h, so greed is easing. Stablecoin cap is up 0.13% while BTC dominance is 58.37%, which reads as rotation back to $BTC.
The Altcoin Season Index is 60, a no clear season regime, with 29 of 48 sampled alts beating $BTC over 90 days. The 7 day change is 9, led by $AKE at 5492.3% and lagged by $KAT at -15.3% over 90 days.
VPIN on $BTC is 0.1516, at the 84th percentile. This means order flow imbalance is running above most recent readings, but VPIN is not directional.
Binance global long short account ratio for $BTC was 1.16, and the top trader position ratio was 2.12. The 24 hour cumulative taker delta for $BTC was -1,873 BTC, measured as buy minus sell volume, and $DOGE had the most stretched ratio at 2.73.
$AVAX on dYdX long versus Aster short shows the widest spread on the board at 0.037% with a net APR of 31.14% after fees. That is the kind of dislocation desks farm while others argue direction, and it points to where leverage is sitting rather than where price is headed.
DAI is trading above its dollar peg on our 10 minute public endpoint snapshot, with a high of 1.0078, a low of 0.9998, and a median of 1.0026 across 3 venues. Historically, readings like this have often reflected short lived venue level dislocations rather than a firm conclusion about redemption conditions, but this snapshot alone does not show the cause.
Mixed pressure is the cluster pattern, with $ARB standing out at 47 score, -5.49% OI, and -0.0183% funding. OI build with one sided funding measures crowding, OI drop with flat funding measures deleveraging, and funding without OI build measures positioning without new money.
On $BTC, a $1M market order costs 0.8 bps on the deepest book, while on $LINK it costs 28.1 bps on the thinnest book. Thin books leave less depth to absorb a large order, so cascade risk rises when liquidity is sparse across levels.
Showing the 12 most recent of 700 posts we hold for @bykaranteli_com. 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.
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 16 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 5 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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“📊 Bykaranteli.Com” (@bykaranteli_com), 121,189 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/bykaranteli_com.
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.