Telegram RegisterThe public register of Telegram
Telegram profile photo for CryptoKILS🥷🏻

Channel

CryptoKILS🥷🏻

@CryptoKILS

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

38subscribers

+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-1002389008576
TypeChannel
Username@CryptoKILS
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live22 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/CryptoKILS

Growth

373837.57 August 2026 — 37 subscribers10 August 2026 — 37 subscribers22 August 2026 — 38 subscribers7 August 202622 August 2026
3 measurements spanning 14 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 37–38 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 02:0738+1
10 Aug 2026, 21:3137no change
7 Aug 2026, 15:2237first reading

Engagement

20 posts held, back to 9 September 2025the 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 20 posts for this entry, the most recent from 18 October 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

18 Oct 2025, 15:06 UTC53 viewsread 10 August 2026

CPLTbYbtDMKZtHBaPqdDmHjxNwESCEB14gm6VuoDpump

Signed Arpkils♱

3 Oct 2025, 16:25 UTC71 viewsread 10 August 2026

0xD19Cc8A170dAA38cB5093B9Bb3Ac82aBea1b6b52

Signed Arpkils♱

19 Sept 2025, 08:30 UTC66 viewsread 10 August 2026

And guys its only available on aster dex most of people dont even know bridging we are early as fuck

Signed Arpkils♱

19 Sept 2025, 07:51 UTC62 viewsread 10 August 2026

if u were in the trenches since year and seen all the launchpad wars BONK vs PUMP vs HEAVEN vs BAGS vs BELIEVE they all actually captured almost 50% of launchpad volume on their peak so im full in $ASTER my entry price was 0.189$

Signed Arpkils♱

19 Sept 2025, 07:49 UTC59 viewsread 10 August 2026

My thesis :- its $HYPE substitute backed by binance and hype is at 56-57$ per coin and i think even if its share 10-20% marketshare of $HYPE which is billions then $ASTER will be at 5-6$ easy and also HYPE is independent DEX with its low liquidity BNB u all know 1000$ just ath...

Signed Arpkils♱

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

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

“CryptoKILS🥷🏻” (@CryptoKILS), 38 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/CryptoKILS.

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.