Telegram RegisterThe public register of Telegram
Telegram profile photo for John Bio

Channel

John Bio

@johnsstock

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

5subscribers

+2 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-1004366525840
TypeChannel
Username@johnsstock
Created22 July 2026 — measured — dated from the channel’s first post
First recorded13 August 2026
Last confirmed live16 November 2026
Measurements held5
Confirmed unchanged6 times, most recently 16 November 2026
On Telegramt.me/johnsstock

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

364.57 August 2026 — 3 subscribers13 August 2026 — 3 subscribers14 August 2026 — 5 subscribers19 September 2026 — 6 subscribers4 October 2026 — 5 subscribers57 August 20264 October 2026
5 measurements spanning 57 days, net +2. 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–6 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Oct 2026, 04:595-1
19 Sept 2026, 10:006+1
14 Aug 2026, 20:355+2
13 Aug 2026, 16:313no change
7 Aug 2026, 19:423first reading

Engagement

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

Recent posts

13 Aug 2026, 13:36 UTC1 viewsread 13 August 2026

#WTS 🐛 WISE, POCKIT, STRIPE CRYPTO EXCHANGE: BINGX, BYBIT, @WALLET, MOONPAY, MEXC, BITGET AND ALL COUNTRY KYC AVAILABLE 🇵🇱! KYC CUSTOM NAME // KYC BY LINK 👤 ALL ACCOUNT DM ME 🛡 ✅@johndagt

26 Jul 2026, 13:30 UTC32 viewsread 13 August 2026

We’re available 24/7, Monday to Sunday. ⏱ Our experienced team handles tasks of any complexity with speed, quality, and professionalism. 🚀 Don’t miss your chance to work with us — we’re always ready to help! 🛡 The only contact @johndagt

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

“John Bio” (@johnsstock), 5 subscribers as measured 4 October 2026. Telegram Register, tgregister.com/channel/johnsstock.

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.