Channel
@killazDev
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
187subscribers
+4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002033608746 |
|---|---|
| Type | Channel |
| Username | @killazDev |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/killazDev |
Education — 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 24 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 12:18 | 187 | +2 |
| 8 Sept 2026, 13:00 | 185 | +3 |
| 23 Aug 2026, 02:16 | 182 | -1 |
| 8 Aug 2026, 12:32 | 183 | no change |
| 7 Aug 2026, 18:12 | 183 | first reading |
19 posts held, back to 5 June 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 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 19 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
125 reactions across 15 posts, in 7 distinct kinds. The most used accounts for 59.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5294107689847119376 | 74 | 59.2% | |
| custom 5242356464961478778 | 23 | 18.4% | |
| custom 5465405283557733520 | 16 | 12.8% | |
| custom 5465602315182437524 | 4 | 3.20% | |
| custom 5242344653801415939 | 3 | 2.40% | |
| custom 5382319858476146053 | 3 | 2.40% | |
| custom 5280813894187639638 | 2 | 1.60% |
Custom emoji. Every 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 counts beside them are Telegram’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 15 of the 19 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 125 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 5 June 2026 to 6 August 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.
4-ех месячный курс для QA от Авито, кому актуально - welcome. регистрация до 16 августа https://start.avito.ru/course-qa https://start.avito.ru/course-qa https://start.avito.ru/course-qa
custom 52941076898471193762
🇷🇺
custom 529410768984711937614
"работай без ошибок, сделай все хорошо"
custom 52941076898471193762custom 54656023151824375242custom 53823198584761460531
завтра буду смотреть, Боря раскидал по фактам https://youtu.be/jsoKH4Pvld0?si=h_xX0BzFQ-J62nPw
custom 54656023151824375241
прикольно? или нет? https://yandex.ru/company/news/29-07-2026-01
➕
custom 529410768984711937620
🐴
норм у меня паблик новостей про авито и рандомных картинок? работаю, стараюсь
custom 52423564649614787788custom 52423446538014159392custom 54656023151824375241
Пользователи "Авито" старше 14 лет теперь смогут подтверждать подлинность своего профиля через "Госуслуги" — раньше это можно было делать только с 18 лет, пишут РИА Новости. Расширение возрастных рамок реализовано в партнерстве с Минцифры. А если система в целях безопасности ограничила доступ к аккаунту, например, при признаках взлома, подростки смогут использовать новый механизм "Позвать взрослого", где родитель ил…
custom 52423564649614787783
Photo, posted without a caption
custom 529410768984711937611
Кто помнит Go&Grill в Москве? Так вот — собираемся в СПб, потому что 22 июля проведём Go&Grill там! План простой: 1⃣22 июля идём в бар «Юнион» 2⃣там в командах играем в Fast food System Design — прикидываем архитектуру для мемных проектов (ну, например, для системы охлаждения пива в офисе 😂) 3⃣не забываем наслаждаться ништяками с гриля и разнообразными напитками 4⃣ чиллим и болтаем со всеми в лаундж-зоне Ну не пла…
custom 52423564649614787782custom 52423446538014159391
отказался от rtk в пользу второго аккаунта с подпиской 20 долларов оставил только системный промпт на go test, там сильно экономит, в остальном не очень и иногда руинит поиск по файлам
custom 53823198584761460531
Showing the 12 most recent of 19 posts we hold for @killazDev. 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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“killaz.dev/blog” (@killazDev), 187 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/killazDev.
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.