Channel
@behdark_EN
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
7,636subscribers
+294 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001736040703 |
|---|---|
| Type | Channel |
| Username | @behdark_EN |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 8 October 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 8 October 2026 |
| On Telegram | t.me/behdark_EN |
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 12 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Oct 2026, 16:19 | 7,636 | +359 |
| 2 Oct 2026, 09:38 | 7,277 | +13 |
| 16 Sept 2026, 11:57 | 7,264 | -21 |
| 12 Sept 2026, 12:22 | 7,285 | -3 |
| 8 Sept 2026, 05:01 | 7,288 | +5 |
| 3 Sept 2026, 05:55 | 7,283 | -18 |
| 31 Aug 2026, 00:34 | 7,301 | -13 |
| 25 Aug 2026, 07:12 | 7,314 | -2 |
| 22 Aug 2026, 00:38 | 7,316 | -5 |
| 18 Aug 2026, 23:26 | 7,321 | -11 |
| 16 Aug 2026, 07:58 | 7,332 | -1 |
| 12 Aug 2026, 20:07 | 7,333 | -3 |
| 10 Aug 2026, 01:31 | 7,336 | -8 |
| 7 Aug 2026, 11:42 | 7,344 | +2 |
| 7 Aug 2026, 09:30 | 7,342 | no change |
| 7 Aug 2026, 09:28 | 7,342 | first reading |
56 posts held, back to 2 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 16 pages 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 56 posts for this entry, the most recent from 20 August 2026. An engagement rate over an empty window would be a number about nothing.
657 reactions across 56 posts, in 12 distinct kinds. The most used accounts for 67.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 443 | 67.4% | |
| 👍 | 126 | 19.2% | |
| 🔥 | 22 | 3.35% | |
| 😁 | 18 | 2.74% | |
| 💯 | 12 | 1.83% | |
| 🤝 | 10 | 1.52% | |
| 😎 | 8 | 1.22% | |
| 🤯 | 8 | 1.22% | |
| 🏆 | 6 | 0.913% | |
| 🐳 | 2 | 0.304% | |
| 👏 | 1 | 0.152% | |
| 💋 | 1 | 0.152% |
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 56 of the 56 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 657 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 56 most recent posts we hold, published 2 August 2026 to 20 August 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.
🔥 KCEX × BehDark | 72H Exclusive Trading Challenge The market is moving again |don’t let fees eat into your trades. Low fees don’t mean a small platform. KCEX is currently listed among CoinMarketCap’s Top 25 global derivatives exchanges. ⚡️ 0% spot trading fees ⚡️ 0% futures Maker fees ⚡️ Only 0.01% futures Taker fees ⚡️ 0 withdrawal fees Eligible new users can also unlock the KCEX New User Welcome Package and qu…
❤5💯2🤝2👍1
#TWTUSDT analysis (1D) The Trust Wallet Token appears to be forming a Diametric pattern. It is currently moving upward along with the market and seems to be forming Wave F of this Diametric, which is a bullish wave. We expect the price to move down from the supply box and make its drop to form Wave G. The targets are marked on the chart. A daily candle close above the invalidation level will invalidate this analy…
❤7
✅ #ZECUSDT analysis (4H) Update By holding the green zone, the price pumped more than 11% and reached the first target. 🔗 @Behdark_EN
❤7
🔆 When the market had low volume and little movement, many people left our community. 🔆 They thought our analysis was wrong, or that it was somehow our fault that the market wasn’t moving. 🔆 As Warren Buffett says, the market takes money from the impatient and gives it to the patient. 🔆 Sometimes, you simply have to be patient. You can’t control the market.
❤6👍4
✅ This signal was forwarded live from our VIP channel to the public channel. 🚀 After a 13% pump, the first target was reached. 💭 To join the VIP channel, message @S_Behdark
❤4🔥2😁1
✅ #QTUMUSDT analysis (8H) Update After hitting the demand zone, the price pumped more than 7%, and the first target was reached. 🔗 @Behdark_EN
❤7
✅ #BTCUSDT analysis (1D) Update We previously shared a higher timeframe analysis for Bitcoin. We expect the price to rise toward the supply zone identified in that analysis and then drop back toward the low. 🔗 @Behdark_EN
❤14😁6🤯1
✅ #BTCUSDT analysis (4H) Update If you’ve been following us, you know that we’ve had a bullish view on Bitcoin from the very beginning. In our previous post, we were expecting a mild correction, but the scenario we shared in this POST turned out to be correct. Price reached the supply zone from our previous analysis. However, we’ll update our Bitcoin analysis on the higher time frame in the next post. 👇🏻 🔗 @Behda…
👍9❤3😁2
✅ #NEARUSDT analysis (12H) Update After hitting the green zone, the price pumped more than 12% and reached the first target. 🔗 @Behdark_EN
❤4😁2👍1
❤️User feedback! Nearly 2,000% profit!🫶🏻
❤7😁1
✅ #AAVEUSDT analysis (12H) Update After hitting the green zone, the price pumped more than 10%. We should consider the first target as hit, so take some profit. 🔗 @Behdark_EN
❤9😁2👍1
✅ #DOGEUSDT analysis (4H) Update Despite the low trading volume in the market during this period, the green zone held, and the price pumped more than 4% from the upper edge of the zone, hitting the first target. 🔗 @Behdark_EN
❤9👍1😁1
Showing the 12 most recent of 56 posts we hold for @behdark_EN. 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.
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 1 registered channel — 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.
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 10 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 8 October 2026 — this entry's latest reading, not the date you are reading this.
“BehDark (Crypto)” (@behdark_EN), 7,636 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/behdark_EN.
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.