Telegram RegisterThe public register of Telegram

Channel

HSE CTF

@hse_ctf

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

344subscribers

-3 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-1003508302773
TypeChannel
Username@hse_ctf
CreatedBetween 1 December 2025 and 30 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/hse_ctf

Growth

344347345.56 August 2026 — 347 subscribers6 August 2026 — 347 subscribers13 August 2026 — 344 subscribers6 August 202613 August 2026
3 measurements spanning 6 days, net -3. 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 344–347 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 03:54344-3
6 Aug 2026, 21:31347no change
6 Aug 2026, 18:03347first reading

Engagement

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

Reaction mix

152 reactions across 18 posts, in 11 distinct kinds. The most used accounts for 57.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
8857.9%
🐳2717.8%
🤪138.55%
👍95.92%
🫡63.95%
21.32%
❤‍🔥21.32%
🔥21.32%
👏10.658%
😱10.658%
🙏10.658%

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 18 of the 18 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 152reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 30 May 2026 to 12 June 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.

Recent posts

12 Jun 2026, 15:51 UTC425 views20 reactionsread 6 August 2026

Сертификаты участников и победителей были отправлены на указанные при регистрации почты. Перед тем как писать, что сертификат не пришел, пожалуйста, проверьте спам🙏! В случае, если сертификат действительно не пришел/иных ошибок - пишите @Dimitry121. Спасибо за участие в HSE CTF❤️

20

8 Jun 2026, 09:49 UTC585 views22 reactionsread 6 August 2026
Forwarded from @bizone_bugbountyPhoto

🪲 Заглянули на HSE CTF В этом году стали партнерами HSE CTF — соревнования по практической кибербезопасности от МИЭМ НИУ ВШЭ для студентов и школьников. Привезли фирменный мерч для победителей, пообщались с участниками, а Андрей Лёвкин, руководитель продукта BI.ZONE Bug Bounty, рассказал про багбаунти и то, чем поиск уязвимостей в реальных продуктах отличается от CTF. Было много интересных вопросов, крутых решений

13🐳72

30 May 2026, 14:18 UTC≈1,570 views36 reactionsread 6 August 2026

Поздравляем победителей! Школьный зачет: 1. Слопопотамы 2. pwn3dByKid$ 3. pwnedworld Студенческий зачет: 1. Glavnoye Zdaniye 2. Beavers0 3. The power of Elijah

21👍8🫡6😱1

30 May 2026, 12:37 UTC681 views4 reactionsread 6 August 2026

ХИНТ НА "Into the looking glass" Арена лежит рядом с кучей

4

30 May 2026, 12:27 UTC694 views2 reactionsread 6 August 2026

ХИНТ НА "МГУ DPI" 1. В дампе можно заметить правильные, и неправильные запросы, которые отличаются в разные дни. 2. Успешные пакеты зависят от фиксированных параметров, один из которых явно указан на сайте, второй и третий можно понять по предыдущей логики. Один из этих параметров может меняться в зависимости от успешного запроса в дампе 3. Фиксированные параметры составляют хеш.

2

30 May 2026, 12:22 UTC608 views2 reactionsread 6 August 2026

ХИНТ НА elbabuinbox Дайте своему агенту всё необходимое отсюда https://dev.mcst.ru/download/

1🐳1

30 May 2026, 12:10 UTC565 views1 reactionsread 6 August 2026

ХИНТ НА "WikiDocs Revenge" Некий сервис скрыт внутри, сможешь ли ты его найти?

1

30 May 2026, 12:08 UTC578 views2 reactionsread 6 August 2026

ХИНТ НА "Raven Poster Workshop" В истории репозитория на гитлабе миэма был обнаружен следующий json-файл: {"style":"miem colors raven","caption_path":"","transform":"t e x t s t y l e"} Есть подозрение, что это артефакт тестировщиков AI-генератора картинок

2

30 May 2026, 12:00 UTC559 views5 reactionsread 6 August 2026

Закрытие борды в 16:30 Все остальное будет согласно расписанию

5

30 May 2026, 11:59 UTC522 views4 reactionsread 6 August 2026

На борде появились новые таски Dopamine Checkpoint Карр-PAdES elbabuinbox

3🙏1

30 May 2026, 11:38 UTC525 views8 reactionsread 6 August 2026
Photo

Сегодня в рамках HSE CTF пройдет доклад на тему «Как работает багбаунти?». Его проведет наш гость - Андрей Владимирович Левкин, руководитель продукта BI.ZONE Bug Bounty. Поговорим о том, как устроен баг-хантинг, чем он отличается от CTF и почему может стать следующим шагом для тех, кто хочет развиваться в практической кибербезопасности. Не пропустите - будет полезно всем, кто хочет применить свои навыки в деле!

4🐳4

Showing the 12 most recent of 18 posts we hold for @hse_ctf. 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 — 636,130 of 1,345,403entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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

“HSE CTF” (@hse_ctf), 344 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/hse_ctf.

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.