Telegram RegisterThe public register of Telegram
Telegram profile photo for CryptoDave - Free Signals

Channel

CryptoDave - Free Signals

@CryptoDavess

On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

245subscribers

-1 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001359680865
TypeChannel
Username@CryptoDavess
CreatedBetween 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live24 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 24 August 2026
On Telegramt.me/CryptoDavess

Growth

245246245.57 August 2026 — 246 subscribers7 August 2026 — 246 subscribers24 August 2026 — 245 subscribers7 August 202624 August 2026
3 measurements spanning 18 days, net -1. 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 245–246 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Aug 2026, 19:54245-1
7 Aug 2026, 02:31246no change
7 Aug 2026, 00:16246first reading

Engagement

19 posts held, back to 11 September 2021the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 13 October 2021. An engagement rate over an empty window would be a number about nothing.

Recent posts

13 Oct 2021, 12:57 UTC720 viewsread 7 August 2026
Photo

Hai Guys, Hari ini saya mau menyampaikan berita yang sangat baik. Jadi eShark Token (ESHK) mengadakan Final Call dengan sisa supply dari stage pertama hingga stage keempat. Final call ini hanya akan ada sampai 14 Oktober! Dalam 12 jam pertama saja, sudah terjual lebih dari 25% dari supply yg ada. Inilah kesempatan terakhir bagi kalian semua agar bisa membeli ESHK sebelum listing nanti. Kedua, eShark Token juga sudah

30 Sept 2021, 13:23 UTC676 viewsread 7 August 2026

Masih ingat dengan eShark Token (ESHK) yang pernah saya kenalkan? Yang bisa cuan besar-besaran karena masih dalam masa ICO. Hari ini akan saya jelaskan beberapa poin mengenai ESHK dan keunggulannya sehingga menjelaskan kenapa ini bukan koin micin eShark Token adalah kripto untuk komunitas eSports karya anak bangsa untuk dunia. Sering kali karya seperti ini dipandang rendah dan tidak dipercaya apalagi karena banyakn

29 Sept 2021, 13:07 UTC479 viewsread 7 August 2026
Photo

ESHK adalah token karya anak bangsa untuk dunia yang memiliki potensi kenaikan yang sangat besar. eShark sekarang ada dalam tahap ICO ke 4 sampai 30 Septemberdengan harga Rp.14.25 per token (potensinya sangat besar apalagi dengan fundamental yang ada) Apa itu eShark? eShark token memiliki utilitas untuk transaksi dalam bidang eSports selain fungsi lain seperti smart contract, transaksi aman dan cepat dan sebagainy

28 Sept 2021, 14:06 UTC431 viewsread 7 August 2026

Hai guys! Udah pada tau belum kalau eShark lagi ngadain Airdrop? Bisa dapat Iphone 12 promax dan 31 Juta Token eShark loh! Pada penasaran gak gimana caranya? Pertama-tama buka situs resmi dari eShark Token ( www.esharktoken.com ) untuk mendapatkan akses ke Airdrop nya, lalu pastikan kamu login menggunakan akun eShark yang sudah kamu daftarkan agar bisa melihat misi dan hadiah yang sudah tersedia. Setelah login berh

16 Sept 2021, 16:53 UTC414 viewsread 7 August 2026

BTCUSDT LONG 43,990 - 45,050/NOW TARGETS 45400 ✅ 46000 ✅ 47000✅ 48000✅ SL 42,148

16 Sept 2021, 16:53 UTC429 viewsread 7 August 2026

#20 CAKEUSDT SPOT Entry Zone: 20-21.2 TP 22.50✅-23.50-25.00-27.00-29.00-31.00-34.00-38.00-43.50 SL 17.80

16 Sept 2021, 16:53 UTC500 viewsread 7 August 2026

XTZUSDT SHORT 6.78 - 7.02 🔘Target 1 - 6.70✅ 🔘Target 2 - 6.60✅ 🔘Target 3 - 6.45 🔘Target 4 - 6.30 🔘Target 5 - 6.20 🔘Target 6 - 6.00 🔘Target 7 - 5.80 🔘Target 8 - 5.57 🚫STOP LOSS: 7.31

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

Mentions

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

“CryptoDave - Free Signals” (@CryptoDavess), 245 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/CryptoDavess.

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.