Telegram RegisterThe public register of Telegram
Telegram profile photo for Crypto Lab 🧪

Channel

Crypto Lab 🧪

@CryptoZMan

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

2,430subscribers

-54 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001409557641
TypeChannel
Username@CryptoZMan
CreatedBetween 1 April 2019 and 30 November 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/CryptoZMan

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 15 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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

2,4302,4842,4577 August 2026 — 2,484 subscribers7 August 2026 — 2,484 subscribers10 August 2026 — 2,481 subscribers14 August 2026 — 2,478 subscribers17 August 2026 — 2,472 subscribers20 August 2026 — 2,469 subscribers23 August 2026 — 2,464 subscribers25 August 2026 — 2,459 subscribers28 August 2026 — 2,451 subscribers31 August 2026 — 2,443 subscribers4 September 2026 — 2,438 subscribers9 September 2026 — 2,434 subscribers13 September 2026 — 2,431 subscribers17 September 2026 — 2,430 subscribers7 August 202617 September 2026
14 measurements spanning 41 days, net -54. 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,422–2,492 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 13:382,430-1
13 Sept 2026, 02:402,431-3
9 Sept 2026, 02:182,434-4
4 Sept 2026, 00:192,438-5
31 Aug 2026, 09:172,443-8
28 Aug 2026, 15:362,451-8
25 Aug 2026, 23:032,459-5
23 Aug 2026, 06:382,464-5
20 Aug 2026, 02:462,469-3
17 Aug 2026, 13:042,472-6
14 Aug 2026, 12:592,478-3
10 Aug 2026, 18:182,481-3
7 Aug 2026, 22:162,484no change
7 Aug 2026, 04:152,484first reading

Engagement

20 posts held, back to 15 December 2021the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages 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 12 January 2022. An engagement rate over an empty window would be a number about nothing.

Recent posts

12 Jan 2022, 07:46 UTC≈2,200 viewsread 7 August 2026
Forwarded from @TheBullvsTheBearPhoto

Read it 👆and stay safe

10 Jan 2022, 15:25 UTC≈2,180 viewsread 7 August 2026
Forwarded from @TheBullvsTheBearPhoto

$BTC dipped below $40K and just look at that monster buy back hourly candle 👀 Huge buyer stepped in

7 Jan 2022, 15:07 UTC≈1,560 viewsread 7 August 2026
Forwarded from @TheBullvsTheBearPhoto

Market still in fear but there seems to be a pattern 👀 Definitely not the right time to SHORT

6 Jan 2022, 09:22 UTC≈1,340 viewsread 7 August 2026
Forwarded from @TheBullvsTheBear

I will update BTC soon. Stay tuned

4 Jan 2022, 08:47 UTC966 viewsread 7 August 2026
Forwarded from @TheBullvsTheBear

Mistype 👆 BTC Long around 46k BTC Short around 49k This BTC’s range can take more than 10-15 days. You can open Long/Short when BTC touch resistance/support. BTC need a breakout candle of BTC to confirm BTC go to the moon or the held #Tradesafe

1 Jan 2022, 09:28 UTC983 viewsread 7 August 2026
Photo

BTC Long 49k. Targets: 48k-47k-46k BTC Short 46k. Targets: 47k-48k-49k BTC moving in this range , we can do trade like this 👆for shortterm

31 Dec 2021, 15:55 UTC846 viewsread 7 August 2026
Forwarded from @TheBullvsTheBearVideo

Video, posted without a caption

31 Dec 2021, 02:18 UTC764 viewsread 7 August 2026
Forwarded from @TheBullvsTheBear

Today is the end of year. So be careful with market guys✊ Let’s enjoy holidays🎏🎉🧨

29 Dec 2021, 13:42 UTC750 viewsread 7 August 2026
Forwarded from @TheBullvsTheBearPhoto

$436 billions liquidated Today. So far.......‼️

29 Dec 2021, 13:35 UTC700 viewsread 7 August 2026
Forwarded from @TheBullvsTheBearPhoto

$BTC update If we lose this horizontal support, I think we’ll break the 45.3K low and go to 43K-41K to grab liquidity

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

“Crypto Lab 🧪” (@CryptoZMan), 2,430 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/CryptoZMan.

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.