Telegram RegisterThe public register of Telegram
Telegram profile photo for NEKRIMINAL

Channel

NEKRIMINAL

@nekrimlnal

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

522subscribers

-31 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-1001661613284
TypeChannel
Username@nekrimlnal
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live4 November 2026
Measurements held12
Confirmed unchanged1 time, most recently 4 November 2026
On Telegramt.me/nekrimlnal

Topic

Hacking & security — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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 the other topics.

Growth

522553537.57 August 2026 — 553 subscribers7 August 2026 — 553 subscribers15 August 2026 — 550 subscribers23 August 2026 — 548 subscribers31 August 2026 — 545 subscribers9 September 2026 — 541 subscribers17 September 2026 — 540 subscribers3 October 2026 — 535 subscribers13 October 2026 — 532 subscribers21 October 2026 — 528 subscribers29 October 2026 — 526 subscribers4 November 2026 — 522 subscribers7 August 20264 November 2026
12 measurements spanning 89 days, net -31. 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 517–558 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Nov 2026, 11:34522-4
29 Oct 2026, 09:20526-2
21 Oct 2026, 08:11528-4
13 Oct 2026, 22:29532-3
3 Oct 2026, 15:38535-5
17 Sept 2026, 20:37540-1
9 Sept 2026, 23:19541-4
31 Aug 2026, 20:13545-3
23 Aug 2026, 20:46548-2
15 Aug 2026, 20:24550-3
7 Aug 2026, 16:51553no change
7 Aug 2026, 07:31553first reading

Engagement

20 posts held, back to 8 April 2025 — 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 9 April 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

9 Apr 2025, 03:40 UTC88 viewsread 7 August 2026
Photo

Новый профит! Абсолютно новая схема,с отменой транзакций BTC. Ты обязан на ней заработать! 🔽🔽🔽 Инструкция 🔽🔽🔽

9 Apr 2025, 03:27 UTC69 viewsread 7 August 2026
Photo

Новый профит! Абсолютно новая схема,с отменой транзакций BTC. Ты обязан на ней заработать! 🔽🔽🔽 Инструкция 🔽🔽🔽

9 Apr 2025, 03:14 UTC48 viewsread 7 August 2026
Photo

Новый профит! Абсолютно новая схема,с отменой транзакций BTC. Ты обязан на ней заработать! 🔽🔽🔽 Инструкция 🔽🔽🔽

9 Apr 2025, 03:01 UTC36 viewsread 7 August 2026
Photo

Новый профит! Абсолютно новая схема,с отменой транзакций BTC. Ты обязан на ней заработать! 🔽🔽🔽 Инструкция 🔽🔽🔽

9 Apr 2025, 02:48 UTC30 viewsread 7 August 2026
Photo

Новый профит! Абсолютно новая схема,с отменой транзакций BTC. Ты обязан на ней заработать! 🔽🔽🔽 Инструкция 🔽🔽🔽

9 Apr 2025, 02:35 UTC27 viewsread 7 August 2026
Photo

Новый профит! Абсолютно новая схема,с отменой транзакций BTC. Ты обязан на ней заработать! 🔽🔽🔽 Инструкция 🔽🔽🔽

9 Apr 2025, 02:22 UTC21 viewsread 7 August 2026
Photo

Новый профит! Абсолютно новая схема,с отменой транзакций BTC. Ты обязан на ней заработать! 🔽🔽🔽 Инструкция 🔽🔽🔽

9 Apr 2025, 02:09 UTC19 viewsread 7 August 2026
Photo

Новый профит! Абсолютно новая схема,с отменой транзакций BTC. Ты обязан на ней заработать! 🔽🔽🔽 Инструкция 🔽🔽🔽

9 Apr 2025, 01:56 UTC19 viewsread 7 August 2026
Photo

Новый профит! Абсолютно новая схема,с отменой транзакций BTC. Ты обязан на ней заработать! 🔽🔽🔽 Инструкция 🔽🔽🔽

9 Apr 2025, 01:43 UTC19 viewsread 7 August 2026
Photo

Новый профит! Абсолютно новая схема,с отменой транзакций BTC. Ты обязан на ней заработать! 🔽🔽🔽 Инструкция 🔽🔽🔽

9 Apr 2025, 01:29 UTC19 viewsread 7 August 2026
Photo

Новый профит! Абсолютно новая схема,с отменой транзакций BTC. Ты обязан на ней заработать! 🔽🔽🔽 Инструкция 🔽🔽🔽

9 Apr 2025, 01:16 UTC17 viewsread 7 August 2026
Photo

Новый профит! Абсолютно новая схема,с отменой транзакций BTC. Ты обязан на ней заработать! 🔽🔽🔽 Инструкция 🔽🔽🔽

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

“NEKRIMINAL” (@nekrimlnal), 522 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/nekrimlnal.

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.