Telegram RegisterThe public register of Telegram
Telegram profile photo for cryptyk

Channel

cryptyk

@cryptyk

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

218subscribers

-8 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-1001088782009
TypeChannel
Username@cryptyk
CreatedBetween 1 September 2016 and 30 September 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 October 2026
Measurements held5
Confirmed unchanged1 time, most recently 8 October 2026
On Telegramt.me/cryptyk

Topic

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 8 October 2026 and assigned it the closest of 31 fixed categories, at 58% 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.

Growth

2182262227 August 2026 — 226 subscribers8 August 2026 — 226 subscribers15 August 2026 — 223 subscribers21 August 2026 — 219 subscribers8 October 2026 — 218 subscribers7 August 20268 October 2026
5 measurements spanning 62 days, net -8. 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 217–227 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Oct 2026, 15:39218-1
21 Aug 2026, 05:42219-4
15 Aug 2026, 04:04223-3
8 Aug 2026, 10:19226no change
7 Aug 2026, 20:41226first reading

Engagement

20 posts held, back to 15 January 2019 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page 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 20 posts for this entry, the most recent from 30 March 2022. An engagement rate over an empty window would be a number about nothing.

Recent posts

30 Mar 2022, 11:47 UTCviews —

The account of the user that owns this channel has been inactive for the last 5 months. If it remains inactive in the next 30 days, that account will self-destruct and this channel may no longer have an owner.

27 Aug 2021, 17:39 UTC≈1,060 viewsread 8 August 2026

Hi CTK Community, I have some frustrating news that the ProBit listing has been delayed again by 6 days. We have been having some problems on Cointiger with dumper bots for the last few weeks and have only just got rid of them (I hope). This was messing with the market makers who have to manage arbitrage between Cointiger and ProBit. And it has taken a week to get rid of 4 different trader bots. We now list 8am GMT …

25 Jun 2021, 20:23 UTCviews —

cryptyk pinned «For all the latest Cryptyk info please go to the Cryptyk Chat channel at https://t.me/cryptykChat»

25 Jun 2021, 20:23 UTC871 viewsread 8 August 2026

For all the latest Cryptyk info please go to the Cryptyk Chat channel at https://t.me/cryptykChat

25 Sept 2019, 20:51 UTC≈2,000 viewsread 8 August 2026

To all CTK investors - We are a long term investment with a token that will not acquire true utility until we launch our Cloud product range to enterprises in 2020. Until then we are like 99% of tokens with no utility and completely subject to investor speculation / manipulation and market sentiment. As detailed in our token web site at cryptyk.io and our annual report we expect our price trading regime during this p…

14 Apr 2019, 16:04 UTC≈1,790 viewsread 8 August 2026
Photo

Cryptyk announces a 3 way partnership with BitcoinBing and Project Initiators for penetration into the Indian market. This involved a US$2M token swap and includes listing of the CTK token on the BitcoinBing crypto-exchange https://www.cryptyk.io/bingpartners/ #cryptyk #cryptocurrency #cryptotrading #cryptoexchange #CTK

18 Feb 2019, 05:32 UTC≈1,590 viewsread 8 August 2026
Photo

Crypto a Complement to Fiat, Not a Competitor http://cryptyk.press/CryptoFiat

18 Feb 2019, 04:14 UTC≈1,240 viewsread 8 August 2026
Photo

CTK investment and customer adoption http://cryptyk.news/tokenEconomics

15 Feb 2019, 04:10 UTC≈1,140 viewsread 8 August 2026

Cryptyk featured in top startups tackling security in 2019 http://cryptyk.press/11_Startups

10 Feb 2019, 09:19 UTC999 viewsread 8 August 2026
Photo

Cryptyk Public Sale Officially Closed. Updates about token release coming soon. http://cryptyk.news/PublicSaleClose

Showing the 12 most recent of 20 posts we hold for @cryptyk. 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 8 October 2026 — this entry's latest reading, not the date you are reading this.

“cryptyk” (@cryptyk), 218 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/cryptyk.

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.