Telegram RegisterThe public register of Telegram
Telegram profile photo for Убежище Хакера {зеркало}

Channel

Убежище Хакера {зеркало}

@hacker_sanctuary0

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

335subscribers

-5 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001609581506
TypeChannel
Username@hacker_sanctuary0
CreatedBetween 1 December 2021 and 2 September 2022— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live27 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 27 August 2026
On Telegramt.me/hacker_sanctuary0

Growth

335340337.56 August 2026 — 340 subscribers6 August 2026 — 340 subscribers14 August 2026 — 338 subscribers20 August 2026 — 336 subscribers27 August 2026 — 335 subscribers6 August 202627 August 2026
5 measurements spanning 21 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 334–341 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Aug 2026, 07:08335-1
20 Aug 2026, 13:55336-2
14 Aug 2026, 01:07338-2
6 Aug 2026, 21:33340no change
6 Aug 2026, 17:17340first reading

Engagement

20 posts held, back to 2 September 2022the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 2 September 2022. An engagement rate over an empty window would be a number about nothing.

Recent posts

2 Sept 2022, 13:36 UTC≈5,470 viewsread 6 August 2026

Решение задания "Root Power" с Google CTF 2020. Реверс изменённой авторизации в Linux, анализ ACPI-модуля Читать #CTF #Практика #Решения #Ревёрс

2 Sept 2022, 13:36 UTC≈4,790 viewsread 6 August 2026

Решение задания "soda pop bop" с rgbCTF 2020. Атака на кучу House of Force и особенности выделения крупных чанков Читать Читать, если нет доступа к telegra.ph #CTF #Практика #Решения #PWN

2 Sept 2022, 13:36 UTC≈3,950 viewsread 6 August 2026

Решение задания "Reverse-ing" с TSG CTF 2020. Ревёрс самомодифицирующегося кода Читать Читать, если нет доступа к telegra.ph #CTF #Практика #Решения #Ревёрс

2 Sept 2022, 13:36 UTC≈2,660 viewsread 6 August 2026

Решение задания "sshâteau" с ASIS CTF Quals 2020. Ревёрс SSH-сервера с модифицированной авторизацией Читать Читать, если нет доступа к telegra.ph #CTF #Практика #Решения #Ревёрс

2 Sept 2022, 13:36 UTC≈3,310 viewsread 6 August 2026

Решение задания "Invisible" с ASIS CTF Quals 2020. Подробный разбор атаки на кучу - fastbin-dup. Читать Читать, если нет доступа к telegra.ph #CTF #Практика #Решения #PWN

2 Sept 2022, 13:36 UTC≈2,200 viewsread 6 August 2026

Решение задания "tthttpd" с ASIS CTF Quals 2020. Взлом простого HTTP-сервера. Чтение любого файла с помощью переполнения буфера на стеке Читать Читать, если нет доступа к telegra.ph #CTF #Практика #Решения #PWN

2 Sept 2022, 13:36 UTC≈1,890 viewsread 6 August 2026

Решение задания "Baby note" с ASIS CTF Quals 2020. type conversion loss -> alloca(-n) -> AR -> libc leak-> rewrite saved rbp -> pivot stack on heap -> one_gadget Читать Читать, если нет доступа к telegra.ph #CTF #Практика #Решения #PWN

2 Sept 2022, 13:36 UTC≈1,510 viewsread 6 August 2026

picoCTF 2019 Решение всех заданий категории "Binary Exploitation" Часть 3, оставшиеся 2 задания на эксплуатацию кучи Читать Читать, если нет доступа к telegra.ph #CTF #PWN #Практика #Решения #picoCTF

2 Sept 2022, 13:36 UTC≈1,700 viewsread 6 August 2026

Ровно 2 года назад вышел первый пост на данном канале. В этом посте мы собрали ссылки на самые интересные публикации на канале Читать Читать, если нет доступа к telegra.ph #Ссылки

2 Sept 2022, 13:36 UTC≈1,290 viewsread 6 August 2026

picoCTF 2019 Решение всех заданий категории "Binary Exploitation" Часть 2, следующие 7 задач Читать Читать, если нет доступа к telegra.ph #CTF #PWN #Практика #Решения #picoCTF

2 Sept 2022, 13:36 UTC≈1,070 viewsread 6 August 2026

picoCTF 2019 Решение всех заданий категории "Cryptography" Все 15 задания с разбором Читать Читать, если нет доступа к telegra.ph #CTF #Криптография #Практика #Решения #picoCTF

2 Sept 2022, 13:36 UTC≈1,160 viewsread 6 August 2026

picoCTF 2019 Решение всех заданий категории "Binary Exploitation" Часть 1, первые 15 задач Читать Читать, если нет доступа к telegra.ph #CTF #PWN #Практика #Решения #picoCTF

Showing the 12 most recent of 20 posts we hold for @hacker_sanctuary0. 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.

Citation-graph rank

Citation-graph rank — 1,563,984 of 1,624,904entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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 27 August 2026 — this entry's latest reading, not the date you are reading this.

“Убежище Хакера {зеркало}” (@hacker_sanctuary0), 335 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/hacker_sanctuary0.

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.