Telegram RegisterThe public register of Telegram
Telegram profile photo for Blog CryptoJuke

Channel

Blog CryptoJuke

@CryptoJuketrade

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

5,750subscribers

+27 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001867981813
TypeChannel
Username@CryptoJuketrade
CreatedBetween 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/CryptoJuketrade

Growth

5,7235,7505,736.57 August 2026 — 5,723 subscribers7 August 2026 — 5,723 subscribers10 August 2026 — 5,729 subscribers14 August 2026 — 5,750 subscribers7 August 202614 August 2026
4 measurements spanning 7 days, net +27. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 5,719–5,754 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 00:295,750+21
10 Aug 2026, 23:445,729+6
7 Aug 2026, 14:555,723no change
7 Aug 2026, 06:165,723first reading

Engagement

23 posts held, back to 24 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 8 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
8.26%
avg views ÷ 5,750 subscribers
Avg views / post
475
23 posts measured
Reaction rate
4.00%
reactions ÷ views · ER floor
Posts in window
23
of 23 held

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 21 of 23 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 11 August 2026
Posts held23 (24 July 202611 August 2026)
Views total10,918
Reactions total398
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 03:56 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.

Reaction mix

398 reactions across 21 posts, in 6 distinct kinds. The most used accounts for 44.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍17644.2%
🔥15739.4%
custom 54475769688013263184812.1%
👎92.26%
😁61.51%
💋20.503%

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 isTelegram’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 21 of the 23 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 398reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 23 most recent posts we hold, published 24 July 2026 to 11 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.

Recent posts

11 Aug 2026, 10:25 UTC246 views18 reactionsread 12 August 2026
Photo

❤️НЕДЕЛЮ ЖДАЛ — И НАКОНЕЦ-ТО! 🔥 🐤Всю неделю #BTC топтался в восходящем канале, постепенно подходя ко второму тесту Supply. 👔И вот на выходных наконец сформировалась стадия распределения — 🍮боковик, выход из которого в итоге произошел вниз. ➡️После этого началась проработка накопленной ликвидности снизу, которая уже привела к: 🌟SMS, а после и ☕️BOS на M30; формированию медвежьего OB от 64.545$ — правда, блок получ

🔥9👍6custom 54475769688013263182💋1

10 Aug 2026, 11:24 UTC336 views20 reactionsread 12 August 2026
Photo

Так, привет, друзьяшки! 👋 🐤Вчера я сообщил вам, что переводим шорт по #BTC в БУ — и, как итог, конец выходных закрыл позицию. 💻И вот тут, скорее всего, дело было не в муве Крупного Игрока, а в моей ошибке при построении боковика. Точнее — не учел младший TF. ✨Я взял первую коррекцию на 1H TF. Логика для выходных в этом была — всего 48 свечей, но я упустил один момент: за такое количество свечей боковик нормально н

🔥11👍6custom 54475769688013263183

9 Aug 2026, 09:48 UTC346 views20 reactionsread 12 August 2026
Photo

Утречка всем добрейшего! ☀️ ✨Вот и создана ПЕРВАЯ ДЕВИАЦИЯ СВЕРХУ — ну и стандартная реакция после формирования девиации, конечно же, ВНИЗ. 🐤На данный момент цена тестирует 0.5 текущего рэнджа, о котором писал вчера. 🤔В связи с этим позицию уже можно обезопасить, переведя стоп в БУ. 🙂

🔥12👍6custom 54475769688013263182

8 Aug 2026, 10:02 UTC417 views14 reactionsread 12 August 2026
Photo

🤔Добрый день! 👋 Кратко затрону #BTC и #HYPE. 🐤По #BTC я уже почти всю неделю ждал у моря погоды ✨ — хотелось увидеть либо выход из восходящего канала, либо свип ликвидности снизу с формированием Wick, либо возврат в нисходящую структуру, ну или хотя бы полноценный импульс вверх. 😂Но… ничего из этого не произошло. 🙂🙂Единственное, что отработало — вчерашний локальный лонговый импульс на снятие ликвидности. Да, ликви

👍7🔥5custom 54475769688013263182

7 Aug 2026, 11:04 UTC407 views14 reactionsread 12 August 2026
Photo

🙂🙂Восходящий канал продолжается… уже четвертый день. 😂 ❤️Цена доставлена к STB и получена реакция, после чего рынок снова вернул ее в восходящий канал, прямо в зону Premium. При этом IMB снизу до сих пор остается неперекрытым. ✨Но локально сейчас, на мой взгляд, с высокой вероятностью увидим снятие точек High в зоне Premium. 💻Причина проста — выше сформировалась плавная аккумуляция ликвидности. По сути, это скопле

👍6🔥6💋1😁1

6 Aug 2026, 10:56 UTC439 views15 reactionsread 12 August 2026
Photo

Добрый денек! 👋 💻Восходящий канал продолжает свое движение, при этом цена уже находится в зоне Premium. ✨Интересно, что по пути был сформирован 🐤STB, который до сих пор не протестирован. Его уровень находится на 64.145$. 🐤Но, если честно, работать от него мне не хочется. Причина все та же — 😓IMB снизу до сих пор остается неперекрытым. На мой взгляд, сейчас лишь вопрос времени, когда этот «сквозняк» дойдет до 63.22

🔥11👍2custom 54475769688013263182

5 Aug 2026, 10:21 UTC459 views29 reactionsread 12 August 2026
Photo

❤️Так после дня рождения в итоге пропал на два дня. 😄 😴На самом деле только сегодня вернулся домой за компьютер. Давайте посмотрим, что нового произошло по #BTC. 🙂После отработки боковика, как я и вижу по графику, 3 августа цена вышла из диапазона вверх, при этом не свипнув LL. Самое главное — возврата обратно в рэндж так и не произошло. 🙂🙂Из интересного: снизу сформировался IMB, который до сих пор остается непере

🔥17👍9custom 54475769688013263183

3 Aug 2026, 10:09 UTC522 views26 reactionsread 12 August 2026
Photo

❤️Добрый денек! 😴Сегодня разборов не будет — у жены День рождения. ❤️ Поэтому сегодня уделю время семье. Но пару слов по #BTC все же скажу. 🙂После формирования нижней девиации цена создала обратную девиацию сверху и взяла обозначенную цель — именно об этом был вчерашний пост. 🙂При этом я также писал, что после формирования второй девиации (первой сверху, которая не протестировала OB) шорт открывать не стану. В ит

🔥11👍10custom 54475769688013263183👎1😁1

2 Aug 2026, 09:28 UTC499 views32 reactionsread 12 August 2026
Photo

❤️Добрый день! 👋 Можно сказать, что нижняя девиация полностью себя отработала. 🙂🙂Единственное, от девиации сверху я работать не буду. Еще вчера писал, что если рынок снимет 62.846$, то в шорт входить не стану. Именно этот сценарий мы и увидели — после снятия ликвидности произошел полноценный возврат цены. 🙂Кстати, OB в зоне Discount до сих пор не свипнут, несмотря уже на третий тест. При этом девиация сверху сформи

🔥21👍7custom 54475769688013263184

1 Aug 2026, 11:53 UTC557 views22 reactionsread 12 August 2026
Photo

❤️Большинство проголосовало за шорт, но есть важный нюанс. 👍👎Пока идут выходные, разбирать #BTC выше M5 я не вижу смысла. Все-таки большинству интересны именно внутридневные движения. 🙂🙂Если смотреть на стандартное формирование боковика после IMB-импульса, то сейчас у нас есть четкие границы диапазона: 🙂 63.300$ — верхняя граница. 🙂 62.461$ — нижняя граница. Дальнейшее движение будет зависеть от того, какую сторо

👍14🔥5custom 54475769688013263182👎1

Showing the 12 most recent of 23 posts we hold for @CryptoJuketrade. 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.

Citation-graph rank

Citation-graph rank — 1,310,801 of 1,481,243entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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.

Mentions

Named by 2 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.

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.

Cite this entry

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 14 August 2026 — this entry's latest reading, not the date you are reading this.

“Blog CryptoJuke” (@CryptoJuketrade), 5,750 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/CryptoJuketrade.

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.