Channel
@valuyki_incident
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
2,730subscribers
+40 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002071283049 |
|---|---|
| Type | Channel |
| Username | @valuyki_incident |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/valuyki_incident |
Gambling & betting — 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 15 September 2026 and assigned it the closest of 31 fixed categories, at 53% 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 |
|---|---|---|
| 19 Sept 2026, 07:56 | 2,730 | +8 |
| 14 Sept 2026, 23:17 | 2,722 | +3 |
| 11 Sept 2026, 14:38 | 2,719 | -4 |
| 6 Sept 2026, 14:19 | 2,723 | +9 |
| 2 Sept 2026, 08:37 | 2,714 | +3 |
| 30 Aug 2026, 04:13 | 2,711 | +4 |
| 27 Aug 2026, 12:56 | 2,707 | +6 |
| 20 Aug 2026, 04:22 | 2,701 | +7 |
| 13 Aug 2026, 18:07 | 2,694 | +4 |
| 10 Aug 2026, 19:41 | 2,690 | -2 |
| 8 Aug 2026, 03:52 | 2,692 | +2 |
| 7 Aug 2026, 12:18 | 2,690 | first reading |
22 posts held, back to 6 August 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 2 pages 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 22 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 5 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
5 reactions across 4 posts, in 2 distinct kinds. The most used accounts for 80.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 4 | 80.0% | |
| 😢 | 1 | 20.0% |
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 5 of the 22 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 5 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 22 most recent posts we hold, published 6 August 2026 to 7 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.
🚗 17-летний водитель без прав врезался в дерево в Волоконовском округе Авария произошла в минувшую среду. По предварительным данным, юноша за рулём «Лады-2114» не выбрал безопасную скорость, потерял управление и съехал с дороги, после чего машина врезалась в дерево. В результате ДТП несовершеннолетний водитель получил травмы. Валуйки | Подписаться
В Telegram появилось лицензионное казино Пробуйте: @TonPlay
🚛 В районе хутора Жданов загорелась фура Сегодня в Яковлевском округе, у хутора Жданов, произошло возгорание грузового автомобиля. Что именно случилось — пока неизвестно. Подробности уточняются. Валуйки | Подписаться
⚠️ Дерево упало на проезжую часть на улице Волчанской Инцидент произошёл сегодня — дерево полностью перекрыло все полосы движения. По словам очевидцев, объехать препятствие можно только через велодорожку с заездом через бордюр. Будьте осторожны при движении на этом участке! Валуйки | Подписаться
❗️Уничтоженные склады Wildberries, дефицит топлива, блокировки интернета — это только цветочки. Настоящая кульминация начнётся уже в сентябре. Но официальные СМИ об этом молчат. В Telegram стремительно набирает популярность канал «Закрытая повестка», где публикуют то, что остаётся за рамками официальной пропаганды: — Почему нужно снять вклады до выборов в сентябре? Какие банки могут первыми их заморозить? — Почем…
❤1
🎾 Жители дома на Белгородского полка, 50, жалуются на теннис под окнами Тренировки у стены на стадионе начинаются в 5–6 утра — стук мяча не даёт спать. «Стук мяча и удары ракетки эхом разносятся по всей округе, спать с открытыми окнами просто невозможно! Напоминаю, что это прямое нарушение Закона Белгородской области №489 "Об обеспечении покоя граждан и тишины". Шуметь на придомовой территории запрещено до 8:00 в б…
Удаляю через 5 минут все зашли? ☝️❗️
⚡️ Владимир Путин подписал указ о единовременной выплате для всех граждан РФ в связи с ростом цен на бензин! 🇷🇺 📌Для оформления выплаты нужно подать заявку в течение 48 часов! Выберите свой возраст, чтобы узнать, какую сумму вы можете получить: 🔸 18–24 года 🔸 24–35 лет 🔸 35–45 лет 🔸 45–55 лет 🔸 55–75 лет 🔸 от 75 лет и старше
🚓 Ночью на Есенина, 15 выбили стекло ударом ноги Неизвестный решил не пользоваться дверью и просто вынес стекло. Зачем понадобился такой перформанс — остаётся загадкой. Валуйки | Подписаться
🌦 Утро в Валуйках: ясно и жарко — до +35° Сегодня без осадков, слабый ветер 2–3 м/с, порывы до 13 м/с. Температура воздуха: +28…+35°. Валуйки | Подписаться
⚡️ 5 000 ₽ — столько приносит одна сделка В день доступно 3-5 готовых сделок. Их находит ИИ и проверяют аналитики. От тебя — только повторить под сопровождением трейдеров. ❗️Можно без опыта и анализа графика, нужен телефон, обучение и час времени. Мы живём в эпоху, когда искусственный интеллект делает большую часть работы за нас, НО НЕ ВСЮ! И чтобы понять, как это работает — заходи в канал к Евгению. Все инструкц…
🌦 Последний жаркий день — до 35°С Сегодня в Валуйках ещё будет жарко, но это финальный всплеск: уже в ближайшие дни столбики термометров начнут опускаться. Можно выдохнуть и спланировать выходные с комфортной погодой. Хорошего дня! Валуйки | Подписаться
Showing the 12 most recent of 22 posts we hold for @valuyki_incident. 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.
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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“Валуйки Инцидент🔞 Новости г. Валуйки” (@valuyki_incident), 2,730 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/valuyki_incident.
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.