Telegram RegisterThe public register of Telegram
Telegram profile photo for ⋆ M ⋆

Channel

⋆ M ⋆

@idkhiwsp

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

16subscribers

+5 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-1004314252502
TypeChannel
Username@idkhiwsp
Created20 June 2026 — measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live30 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 23 August 2026
On Telegramt.me/idkhiwsp

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

111613.57 August 2026 — 11 subscribers12 August 2026 — 11 subscribers16 August 2026 — 14 subscribers23 August 2026 — 16 subscribers7 August 202623 August 2026
4 measurements spanning 16 days, net +5. 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 10–17 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 11:2616+2
16 Aug 2026, 15:4814+3
12 Aug 2026, 06:3011no change
7 Aug 2026, 19:3311first reading

Engagement

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

Recent posts

20 Jun 2026, 22:07 UTC73 viewsread 12 August 2026

You may also report a paste to me if it meets any of the following conditions: ———————————————— -Lack of effort -Lack of info -Contains info on person 14 or younger -Irrelevant/Spam -Encourages Violence/Harassment ————————————————

20 Jun 2026, 22:06 UTC73 viewsread 12 August 2026

Paid Support —————————————- removals: $150 blacklists: $700 HOAs: $5000 Discounted Ranks: ? pins: $85 per day —————————————-

Showing the 5 most recent of 5 posts we hold for @idkhiwsp. 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 23 August 2026 — this entry's latest reading, not the date you are reading this.

“⋆ M ⋆” (@idkhiwsp), 16 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/idkhiwsp.

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.