Other / unclassifiable — 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 14 September 2026 and assigned it the closest of 31 fixed categories, at 91% 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
14 measurements spanning 42 days, net +48. 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 3,142–3,204 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
17 Sept 2026, 07:40
3,197
+2
13 Sept 2026, 01:38
3,195
+4
8 Sept 2026, 16:01
3,191
+4
3 Sept 2026, 08:56
3,187
+1
31 Aug 2026, 10:06
3,186
+6
28 Aug 2026, 14:45
3,180
+3
25 Aug 2026, 17:56
3,177
+2
22 Aug 2026, 17:45
3,175
+1
19 Aug 2026, 04:36
3,174
+7
15 Aug 2026, 19:07
3,167
+4
12 Aug 2026, 12:23
3,163
+6
9 Aug 2026, 16:22
3,157
+7
6 Aug 2026, 14:20
3,150
+1
6 Aug 2026, 08:48
3,149
first reading
Engagement
6 posts held, back to 17 May 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 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 6 posts for this entry, the most recent from 18 May 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Video runtime
1m 58s
Average length
1m 58s
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
196 reactions across 6 posts, in 5 distinct kinds. The most used accounts for 36.7% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
72
36.7%
❤
67
34.2%
👍
49
25.0%
🎉
5
2.55%
😍
3
1.53%
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 6 of the 6 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 196 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 17 May 2026 to 18 May 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
In the posts I made earlier, I showed you the scams that Mike's very own alt accounts, SlaserX and Apocalypse, have done (with definite proof that they are all the same person).
Here is proof of a scam Mike did using his old "Mike" account. This was posted on his old server, but was deleted right away by him, and this member was banned, never to be seen again.😞
PS: It's funny how Mike keeps making up all these imag…
Some might say the only missing puzzle piece here was direct evidence linking Mike to Apocalypse.
You can see the direct proof of Mike being SlaserX above. How cool would it be if there was a piece of evidence linking Mike directly to Apocalypse as well?🙈
You don't have to look too far, because that's exactly what I have attached below!
Here is the full paste itself: https://pastebin.com/BHGgsaR1
Hint: Same as th…
Here is more proof of what should be obvious by now: Mike, SlaserX, and Apocalypse are the same person, and each one of these accounts has been used to scam people repeatedly in different ways.
In the 1st screenshot, you can see that Mike himself literally confirms he is SlaserX. (Hint: check the name on Mike's output message.)
Now, some of you might not know who SlaserX is. For that, check the 2nd screenshot. In i…
This is not the next post I was going to make. I am posting this because some people are asking for proof of the allegations I have made about Mike above. I mean, those are not allegations and the proof itself is in the screenshots, but if you want more proof, fine, here you go;
What I have attached is a screenshot of a chat that happened between me and a user who got scammed by the fake Freddy. To summarize what ha…
Many screenshots here. Let's unpack them one by one.
In the 1st, 2nd, and 3rd screenshots, Mike is trying to say something like I use Sp4rky (the developer behind unshackle) for reversing the ChromeCDM. Needless to say, this is even more ridiculous than Mike's "Zane hooks the browser" claim. Sp4rky himself is literally a user of mine and has been using my API for a long time. 😵💫 Anyone can ask Sp4rky directly, and …
❤24🔥10👍7
Showing the 6 most recent of 6 posts we hold for @DecryptLabs. 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
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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 17 September 2026 — this
entry's latest reading, not the date you are reading this.
“Decrypt Labs” (@DecryptLabs), 3,197 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/DecryptLabs.
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.