Channel
@HackNU
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
1,366subscribers
-3 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001248128854 |
|---|---|
| Type | Channel |
| Username | @HackNU |
| Created | Between 1 March 2018 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 13 August 2026 |
| On Telegram | t.me/HackNU |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 14:25 | 1,366 | -2 |
| 7 Aug 2026, 15:27 | 1,368 | -1 |
| 6 Aug 2026, 20:33 | 1,369 | first reading |
15 posts held, back to 5 April 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 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 15 posts for this entry, the most recent from 28 April 2026. An engagement rate over an empty window would be a number about nothing.
132 reactions across 14 posts, in 4 distinct kinds. The most used accounts for 78.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 103 | 78.0% | |
| 🔥 | 18 | 13.6% | |
| 🎉 | 6 | 4.55% | |
| 👍 | 5 | 3.79% |
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 14 of the 15 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 132reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 5 April 2026 to 28 April 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.
👀We’ve wrapped up HackNU 2026, and we hope you enjoyed it. Here’s a quick recap. 9th annual hackathon 1000+ registered 700+ participants 2,800,000 ₸ prize pool Two days of building, no sleep, real ideas turned into real projects. Big thanks to everyone who made it happen. See you next year 🥴
❤7
Всем привет! 👋 Ловите ваши долгожданные сертификаты и фото с HackNU/26! 🚀 Еще раз спасибо всем за нереальный вайб и крутые проекты. 🔥 Фотографии: album1 by @S3R0T0N1N & album2 Сертификаты
❤1
🔤🔤🔤🔤 🔤🔤🔤 🔤🔤🔤🔤🔤🔤2️⃣5️⃣
❤6
🏆 Vote for ACM@NU at the NU Awards 🏆 This year, ACM@NU has been nominated in two categories: ✨ Academic Club of the Year - ACM ✨ Academic Event of the Year - HackNU/25 Over 2025-2026 academic year, we set record-breaking results and organized 7 major events: 🟡HackNU/25 - 24-hour hackathon, 800+ registered, 5 800 000 KZT prize pool 🟡HackNU/26 - 24-hour hackathon, 1 092 registered, 2 800 000 KZT prize pool 🟡NUOPEN 2…
❤5🔥1
HackNU 2026 by ACM@NU SC | 04-05.04.2026 by @S3R0T0N1N https://photos.app.goo.gl/6mmekUzVbTsSdX2F6
🔥4
Всем привет! Хотели сообщить, что призовые по кейсам Higgsfield уже отправлены. Призовые от КТЖ пока ещё ожидаем постараемся ускорить процесс. Спасибо за понимание!
🎉6
A huge thank you to the partners of HackNU26! 💚 Thanks to your support, we’ve built a platform where hundreds of talents turned their ideas into real projects in just 24 hours 🤝 Огромное спасибо партнерам HackNU26! 💚 Благодаря вашей поддержке мы создали площадку, где сотни талантов всего за 24 часа превратили смелые идеи в реальные проекты 🤝 HackNU26 серіктестеріне үлкен алғыс білдіреміз! 💚 Сіздердің қолдауларың…
❤5
Hi everyone! We’d really appreciate it if you could take a few minutes to fill out this feedback form about HackNU 🙌 Your responses help us improve future events and make them even better for you. https://docs.google.com/forms/d/e/1FAIpQLSe_m0vg-vnDsd_VE2oV6MRCx4AYRCAE_xXdbcln0hxymsSWsw/viewform Thank you for your time 💙
👍5
Дорогие участники HackNU 2026, Спасибо каждому из вас за участие, энергию и те идеи, которые вы привнесли в этот хакатон. Эти 24 часа - это не только про код и решения, но и про людей, атмосферу, новые знакомства и опыт, который остаётся с вами надолго ❤️🔥 Отдельно хотим поблагодарить наших спонсоров за поддержку - благодаря вам это событие стало возможным! Наша команда ACM действительно старалась сделать HackNU …
❤31🔥4
Вот и закончился HackNU/26, всем спасибо за участие, а также поздравляем всех наших победителей! Скоро мы выложим форму где победителям нужно будет заполнить чтобы получить денежные призовые💰
❤41
Церемония закрытия начнется в 1️⃣8️⃣:3️⃣0️⃣ Orange Hall👀, там же где было открытие! Всех ждём😎!
🧩 Топ-15 команд по кейсу Higgsfield DS/ML будут выступать в следующем порядке: 1. opik 2. BoltWW 3. 2seq 4. SE-2307 5. PullRequest 6. wins 7. Three_musketeers 8. AI_development_jiggas_department 9. digital_yakuza 10. Arcana 11. codeakbas 12. vibecoders 13. SUvIT 14. akeshbetti 15. fairies Ждём всех в Blue Hall скоро начинаем, приходите поддержать команды
🔥9❤2
Showing the 12 most recent of 15 posts we hold for @HackNU. 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 — 101,427 of 1,350,102entries 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.
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.
Named by 2 registered channels — 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.
@HackNU named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“HackNU” (@HackNU), 1,366 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/HackNU.
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.