Telegram RegisterThe public register of Telegram
Telegram profile photo for CryptoWhale Chart

Channel

CryptoWhale Chart

@cryptowhalechart

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

2,063subscribers

-11 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001999638460
TypeChannel
Username@cryptowhalechart
CreatedBetween 1 October 2023 and 30 April 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live15 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/cryptowhalechart

Growth

2,0632,0742,068.56 August 2026 — 2,074 subscribers6 August 2026 — 2,074 subscribers9 August 2026 — 2,072 subscribers12 August 2026 — 2,066 subscribers15 August 2026 — 2,063 subscribers6 August 202615 August 2026
5 measurements spanning 9 days, net -11. 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 2,061–2,076 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 05:232,063-3
12 Aug 2026, 06:182,066-6
9 Aug 2026, 05:532,072-2
6 Aug 2026, 06:192,074no change
6 Aug 2026, 04:172,074first reading

Engagement

19 posts held, back to 17 November 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof 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 19 posts for this entry, the most recent from 6 June 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

192 reactions across 18 posts, in 19 distinct kinds. The most used accounts for 32.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
6332.8%
custom 54654653830350837684624.0%
157.81%
👀94.69%
🔥94.69%
👍84.17%
🤔63.13%
🎄52.60%
custom 521314363071741369642.08%
😁42.08%
🙏42.08%
🤝42.08%
🤣42.08%
🐳31.56%
🕊31.56%
👎21.04%
custom 546554660086665200810.521%
🤨10.521%
🤷‍♂10.521%

Custom emoji. 3 of the rows above are 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 counts beside them areTelegram’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 18 of the 19 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 192reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 17 November 2025 to 6 June 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

6 Jun 2026, 10:30 UTC≈5,250 views7 reactionsread 7 August 2026
Photo

💰 Bitcoin (CME) 1D Actualización Tras cerrar el gap del CME en torno a los $84.000, el precio ha corregido tal y como anticipábamos. En el proceso se ha generado un nuevo gap en la zona de los $79.000. El escenario que manejo es el siguiente: una vez completada la corrección actual y recogida la liquidez situada entre los $48.000 y los $52.000, el precio debería tener vía libre para volver a buscar y cerrar ese ga

3custom 546546538303508376821🤝1

9 May 2026, 11:37 UTC≈8,390 views7 reactionsread 7 August 2026
Photo

⚠️ MAPA DE LIQUIDACIONES 📉 Si el precio cae hasta los $65.520 → se liquidarían casi $14.000 millones en posiciones largas. 📈 Si el precio sube hasta los $92.140 → se liquidarían casi $9.000 millones en posiciones cortas. Mucho ojo con estos niveles 👀 💰 BTC1! 1D Bitcoin ha cerrado el GAP del CME. Toca estar atentos: es posible una corrección antes de seguir subiendo. Yo sigo optimista y no vendo. Mantengo liquid

2🐳2👍2custom 54654653830350837681

14 Apr 2026, 09:28 UTC≈10,700 views10 reactionsread 7 August 2026
Photo

💰 BTC/USD 1D - CME Bitcoin acaba de superar al alza la línea de tendencia bajista que arrastraba desde el ATH de principios de octubre. El siguiente movimiento lógico sería ir a cubrir la zona del GAP del CME situada en torno a los 85.000$. ✅ https://t.me/cryptowhalechart/

4custom 54654653830350837684🤝2

25 Feb 2026, 11:48 UTC≈13,400 views23 reactionsread 7 August 2026
Photo

💰 BTC/USD 1M Se habla mucho del “ciclo de 4 años”. Bitcoin ha marcado su suelo aproximadamente 23 meses después de su ATH previo. En 2015 ocurrió. En 2018 ocurrió. En 2022 ocurrió. Estamos nuevamente en el mes 23. ✅ https://t.me/cryptowhalechart/

12custom 54654653830350837686🔥3😁2

21 Feb 2026, 12:15 UTC≈11,800 views14 reactionsread 7 August 2026
Photo

BTC/XAU 1M En 2014, el BTC/XAU tocó fondo después de 14 meses. En 2018, el BTC/XAU tocó fondo después de 14 meses. En 2022, el BTC/XAU tocó fondo después de 14 meses. En este ciclo, el mercado bajista de BTC/XAU lleva 14 meses en curso. ¿Estaremos presenciando el inicio de una reversión? ✅ https://t.me/cryptowhalechart/

10custom 54654653830350837684

15 Feb 2026, 19:45 UTC≈1,480 views3 reactionsread 7 August 2026
Forwarded from @SignalswinsPhoto

Estamos regalando nuestro libro, La Biblia del Análisis Técnico, solo por suscribirte a nuestra Newsletter. En la newsletter, compartiremos contenido exclusivo cada mes, incluyendo análisis de mercado a fondo, secretos, narrativas y mucho más. Sigue el enlace a continuación para suscribirte con tu correo electrónico. https://scryptowhale.substack.com ✅ https://t.me/Signalswins

21

4 Feb 2026, 09:15 UTC≈10,600 views10 reactionsread 7 August 2026
Photo

💰 BTC/USDT 1M - Bitcoin ha bajado un 42% desde que alcanzó los $126,200 el 6 de octubre. - 4 meses rojos consecutivos, es la racha bajista más larga desde 2018. - En 2018 la racha bajista mas larga fue de 6 meses y fue de casi el 60%. El suelo podría estar cerca ✅ https://t.me/cryptowhalechart/

custom 546546538303508376864

2 Feb 2026, 11:55 UTC≈8,770 views3 reactionsread 7 August 2026
Photo

BTC1! 4H GAP formado en el mercado de futuros del CME durante este fin de semana ✅ https://t.me/cryptowhalechart/

21

2 Feb 2026, 10:14 UTC≈7,820 views6 reactionsread 7 August 2026
Photo

💰 BTC/USDT 1D Elimina todo el FUD y el ruido alrededor de bitcoin. Confía en el proceso Bitcoin se encuentra en rango y seguirá en esta zona durante varios meses. Muchos esperan bitcoin en 60.000 o en 50.000 $... y muchos otros creen que alcanzaremos un nuevo ATH en 2026. Seamos realistas, la probabilidad más alta es que el precio simplemente se mantenga lateral durante gran parte del 2026. ✅ https://t.me/crypto

🔥3👍21

25 Dec 2025, 13:34 UTC≈10,800 views18 reactionsread 7 August 2026
Photo

💰 BTC/USDT 1D Bitcoin está repitiendo exactamente la misma estructura correctiva de 5 ondas Dos máximos crecientes > tramo correctivo > doble suelo > rally En ambas ocasiones, esta estructura condujo a una fuerte expansión alcista. El tiempo se esta acabando y bitcoin no espera La paciencia paga! ✅ https://t.me/cryptowhalechart/

custom 54654653830350837687🎄53🙏2👀1

22 Dec 2025, 12:13 UTC≈10,500 views17 reactionsread 7 August 2026
Photo

💰 BTC/USDT 1D Estamos a punto de producir el breakout de la línea de tendencia descendente. ¿Próximo objetivo? Nuevo ATH!!! 👀👀👀 ✅ https://t.me/cryptowhalechart/

6custom 52131436307174136964🔥3custom 54654653830350837683🤝1

Showing the 12 most recent of 19 posts we hold for @cryptowhalechart. 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 — 15,348 of 1,481,217entries 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.

Republishes

Channels on the register whose posts this channel has forwarded.

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 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.

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

“CryptoWhale Chart” (@cryptowhalechart), 2,063 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/cryptowhalechart.

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.