Telegram RegisterThe public register of Telegram
Telegram profile photo for 3RbGh - HaCkEr

Channel

3RbGh - HaCkEr

@outyur

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

339subscribers

-35 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-1002515860318
TypeChannel
Username@outyur
Created13 June 2025 — measured — dated from the channel’s first post
First recorded8 August 2026
Last confirmed live5 November 2026
Measurements held12
Confirmed unchanged1 time, most recently 5 November 2026
On Telegramt.me/outyur

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

339374356.57 August 2026 — 374 subscribers8 August 2026 — 374 subscribers14 August 2026 — 370 subscribers20 August 2026 — 363 subscribers27 August 2026 — 361 subscribers5 September 2026 — 359 subscribers13 September 2026 — 355 subscribers26 September 2026 — 354 subscribers7 October 2026 — 349 subscribers14 October 2026 — 346 subscribers21 October 2026 — 341 subscribers5 November 2026 — 339 subscribers7 August 20265 November 2026
12 measurements spanning 90 days, net -35. 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 334–379 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Nov 2026, 13:09339-2
21 Oct 2026, 18:27341-5
14 Oct 2026, 15:16346-3
7 Oct 2026, 16:00349-5
26 Sept 2026, 08:57354-1
13 Sept 2026, 06:59355-4
5 Sept 2026, 02:38359-2
27 Aug 2026, 20:47361-2
20 Aug 2026, 14:22363-7
14 Aug 2026, 06:37370-4
8 Aug 2026, 06:18374no change
7 Aug 2026, 16:22374first reading

Engagement

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

Recent posts

4 Aug 2026, 01:12 UTC42 viewsread 8 August 2026

يلي يعرف للكرت الفضي الوهمي خاص @MJA7m

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

“3RbGh - HaCkEr” (@outyur), 339 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/outyur.

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.