Telegram RegisterThe public register of Telegram

Channel

NS Tech Talks

@nstechtalks

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

1,107subscribers

+9 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002055823461
TypeChannel
Username@nstechtalks
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/nstechtalks

Growth

1,0981,1071,102.56 August 2026 — 1,098 subscribers6 August 2026 — 1,099 subscribers6 August 2026 — 1,099 subscribers9 August 2026 — 1,105 subscribers12 August 2026 — 1,107 subscribers6 August 202612 August 2026
5 measurements spanning 6 days, net +9. 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 1,097–1,108 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 15:251,107+2
9 Aug 2026, 06:411,105+6
6 Aug 2026, 12:191,099no change
6 Aug 2026, 10:211,099+1
6 Aug 2026, 05:471,098first reading

Engagement

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

Reaction mix

209 reactions across 9 posts, in 11 distinct kinds. The most used accounts for 58.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥12258.4%
4320.6%
👍3014.4%
😁31.44%
😱31.44%
custom 524913866929341394020.957%
👎20.957%
❤‍🔥10.478%
👏10.478%
💅10.478%
💯10.478%

Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it isTelegram’s.

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

Measured over the 9 most recent posts we hold, published 20 April 2026 to 2 July 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

2 Jul 2026, 09:22 UTC784 views28 reactionsread 6 August 2026
Photo

NS Tech Talks #19: tell me wAI — случился 🤖 Говорили про AI три часа — и ни разу не сказали «ChatGPT изменит всё». Кажется, это и было главное. Записи уже на YouTube 👇 🧠 Саша Дёмин — «Искусственность Интеллекта, или Требуется Подкрепление» 🏗 Юрий Бацюро — «Влияние ИИ на архитектуру систем и предприятий» 🔮 Иван Немытченко — «Чё там уже после AI?» 📸 Фото с митапа — спасибо Александру за атмосферу в кадре: [ссылк

18🔥9👍1

30 Jun 2026, 18:36 UTC≈1,050 views22 reactionsread 6 August 2026

NS TT Workshop #1: Keep calm and Vibe code! Или "Как я перестала бояться и полюбила вайбкодинг" 💻 🙂 Мы пробуем новый формат! 4 июля Дарья Касаткина (Senior Product Manager, Tabby, ex-Avito) расскажет про свой опыт вайбкодинга без большого технического бэкграунда. Не просто доклад, а именно воркшоп: сядешь, попробуешь, уйдёшь с результатом. Для тех, кто давно смотрит на вайбкодинг с интересом, но так и не нашёл по

🔥13😱32👍2custom 52491386692934139402

17 Jun 2026, 14:47 UTC≈2,360 views24 reactionsread 6 August 2026

NS Tech Talks #19: tell me wAI 🤖 Если честно, мы немного устали от разговоров про AI. Не от темы, а от того, как о ней говорят: одни и те же слова, одни и те же прогнозы, одни и те же примеры. В этот раз по-другому. 🧠 Саша Дёмин — «Искусственность Интеллекта, или Требуется Подкрепление: Как мы учимся и учим в агентскую эру?» [10 лет в машинном обучении, разработке и прикладной статистике — в России, США и Сербии] Ч

🔥193💅1💯1

27 May 2026, 14:05 UTC≈1,270 views43 reactionsread 6 August 2026

Нас стало 1000 🎉 Сегодня @demin_developer стал нашим тысячным участником. Мы не знаем как ты нас нашёл, но знаем одно — ты попал в хорошую компанию. Здесь собрались те, кто приходит на митапы в субботу днём, спорит со спикерами, остаётся после докладов и искренне кайфует от того, что делает. @demin_developer — добро пожаловать! И сразу подарок: мы дарим тебе пригласительный на наш следующий митап 🎟 Пиши @AKitovsk

🔥374😁2

27 May 2026, 11:01 UTC≈1,060 views24 reactionsread 6 August 2026
Photo

NS Tech Talks #18: Quality Intelligence - случился 🎉 Три доклада и много разговоров про то, куда QA вообще движется. Кажется, вышло хорошо. Записи уже на YouTube - смотрите, пересматривайте, пересылайте коллегам, которые всё ещё думают что QA это только кликать по кнопкам 🙂 🤖 Фёдор Звалинский - QAI: следите за руками 🎭 Сергей Эльфимов - Ролевые E2E-тесты и Browser Contexts в Playwright 🔧 Дмитрий Новосёлов - QA,

🔥13👍64😁1

15 May 2026, 15:29 UTC≈1,380 views14 reactionsread 6 August 2026

NS Tech Talks #18: Quality Intelligence 🧪 Тестирование меняется быстрее, чем мы успеваем переписывать тест-планы. AI лезет в QA, автотесты обрастают архитектурой, а сами QA-инженеры всё глубже уходят в инфраструктуру. 23 мая поговорим об этом честно - с кодом, цифрами и живыми кейсами. Митап будет полезен QA-инженерам, тест-лидам и разработчикам, которым не всё равно, что происходит с качеством на проде. 🎤 Темы и с

👍11👎21

4 May 2026, 11:21 UTC≈1,320 views16 reactionsread 6 August 2026

Выложили записи докладов с NS Tech Talks #17: Между кодом и продом 🎬 Смотрите, пересматривайте, делитесь с теми, кто не успел прийти 👇 🚀 Слава Олейник — DevOps: риски, деньги, два ямла 🤖 Руслан Садретдинов — DevOps Unchained: реальные истории про то, как мы начали строить то, за что раньше бы не взялись 🐾 Павел Катуров — DevOps для пет-проектов: как не превратить хобби в кладбище кода 🔔 Артём Соколов — От белого

7🔥5👍4

28 Apr 2026, 11:02 UTC≈1,470 views27 reactionsread 6 August 2026
Photo

NS Tech Talks #17: Между кодом и продом — делимся итогами! ⚙️ Поговорили про инженерный менеджмент, AI-инструменты в руках DevOps-инженера, пет-проекты в стабильном проде и фальшивые алерты, которые достают всех. Кажется, у многих что-то щёлкнуло 🙂 Спасибо нашим спикерам. И спасибо всем, кто пришёл, задавал вопросы и оставался до конца 💚 Записи докладов скоро будут на YouTube — следите за каналом. Фотографии: [ссы

🔥19👍43❤‍🔥1

20 Apr 2026, 17:24 UTC≈1,490 views11 reactionsread 6 August 2026

Открываем регистрацию на NS Tech Talks #17: Между кодом и продом 🚀 25 апреля в баре Арена — про прод, деплой, алерты и AI. Подробности уже знаете, осталось только зарегистрироваться 👇 👉 Регистрация: бот 📅 25 апреля (суббота) 📍 Бар Арена, Нови Сад 🚪 Двери в 14:00, доклады с 14:30 окончание 17:00 💸 Вход: 1500 RSD

🔥7👍21👏1

Showing the 9 most recent of 9 posts we hold for @nstechtalks. 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 — 743,509 of 1,160,990entries 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.

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 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.

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

“NS Tech Talks” (@nstechtalks), 1,107 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/nstechtalks.

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.