Telegram RegisterThe public register of Telegram
Telegram profile photo for ☀️🌞Красная яруга NEW🌞

Channel

☀️🌞Красная яруга NEW🌞

@Yaruga_new

On this record: Topic · Growth · Engagement · Reactions · Posts · Telegram's recommendations · Cite this entry

1,737subscribers

-13 since we began measuring on 21 August 2026

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

Register entry

Telegram ID-1001836015563
TypeChannel
Username@Yaruga_new
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded21 August 2026
Last confirmed live15 September 2026
Measurements held9
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/Yaruga_new

Topic

National news — 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 17 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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.

Growth

1,7371,7501,743.521 August 2026 — 1,750 subscribers21 August 2026 — 1,750 subscribers25 August 2026 — 1,749 subscribers28 August 2026 — 1,748 subscribers30 August 2026 — 1,746 subscribers2 September 2026 — 1,743 subscribers7 September 2026 — 1,741 subscribers11 September 2026 — 1,740 subscribers15 September 2026 — 1,737 subscribers21 August 202615 September 2026
9 measurements spanning 25 days, net -13. 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,735–1,752 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 10:591,737-3
11 Sept 2026, 12:011,740-1
7 Sept 2026, 00:581,741-2
2 Sept 2026, 11:131,743-3
30 Aug 2026, 21:451,746-2
28 Aug 2026, 01:341,748-1
25 Aug 2026, 00:491,749-1
21 Aug 2026, 17:081,750no change
21 Aug 2026, 08:301,750first reading

Engagement

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

Reaction mix

20 reactions across 17 posts, in 4 distinct kinds. The most used accounts for 80.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤬1680.0%
🙏210.0%
👎15.00%
🕊15.00%

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

Measured over the 20 most recent posts we hold, published 19 August 2026 to 21 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.

Recent posts

21 Aug 2026, 06:51 UTC34 viewsread 21 August 2026

❗В Ракитянском округе в хуторе Семейный FPV-дрон атаковал ГАЗель — повреждена кабина. ❗В селе Илек-Кошары дрон сдетонировал на предприятии — пробита кровля гаража.

21 Aug 2026, 05:53 UTC49 views1 reactionsread 21 August 2026

‼️Сводка последствий ударов ВСУ по нашему Краснояружскому МО и Ракитянскому МО за 20 августа ❗В Краснояружском округе по посёлкам Задорожный, Красная Яруга, Прилесье, Степное, сёлам Вязовое, Графовка, Колотиловка, Надежевка, Поповка, Сергиевка, Староселье, Теребрено, хуторам Первомайский и Фищево 3 раза сброшены 4 взрывных устройства с БПЛА и совершены удары 48 беспилотников, 16 из которых подавлены и сбиты. В посёл

🤬1

21 Aug 2026, 05:51 UTC37 views1 reactionsread 21 August 2026

‼️Информация о нанесённых ВСУ ударах по нашему региону за прошедшие сутки (часть 2): ◻️ В Ивнянском округе село Новенькое подверглось атакам двух беспилотников — повреждён инфраструктурный объект. Также над округом сбиты 3 БПЛА. ◻️ Над Красногвардейским округом сбиты 2 беспилотника. Без повреждений. ◻️ В Краснояружском округе по посёлкам Задорожный, Красная Яруга, Прилесье, Степное, сёлам Вязовое, Графовка, Колоти

🤬1

21 Aug 2026, 05:51 UTC35 views1 reactionsread 21 August 2026

‼️Информация о нанесённых ВСУ ударах по нашему региону за прошедшие сутки (часть 1): ◻️ Над Алексеевским округом сбиты 9 беспилотников. Пострадавших нет. ◻️ Белгород атакован один беспилотником. Без последствий. ◻️ В Белгородском округе по посёлкам Малиновка, Октябрьский, сёлам Бессоновка, Болдыревка, Долбино, Нечаевка, Никольское, Отрадное, Салтыково, Устинка и Ясные Зори выпущен один боеприпас в ходе одного обст

🤬1

21 Aug 2026, 05:12 UTC54 views1 reactionsread 21 August 2026

‼️Два рейсовых автобуса в Шебекино атаковали беспилотники. По данным местного блогера «Просто Михаила», есть пострадавшие.

🤬1

20 Aug 2026, 18:08 UTC119 views1 reactionsread 21 August 2026

‼️Громко в Красной Яруге. Будьте в укрытиях!

🙏1

20 Aug 2026, 17:57 UTC122 viewsread 21 August 2026

‼️Внимание, Красная Яруга фиксируется множество фпв Врага быть в укрытиях. Работаем.

20 Aug 2026, 17:21 UTC131 views1 reactionsread 21 August 2026

❗В посёлке Пролетарский Ракитянского округа при детонации FPV-дрона посечён кузов автомобиля. Второй дрон сдетонировал на парковке многоквартирного дома — повреждены остекление и машина. ❗В районе села Дмитриевка дрон ударил по грузовому автомобилю — транспорт повреждён. ❗В селе Бобрава вследствие атаки FPV-дрона разбиты стёкла трактора.

🤬1

20 Aug 2026, 17:20 UTC121 views1 reactionsread 21 August 2026

❗В Краснояружском округе село Сергиевка атаковано двумя беспилотниками — пробиты крыши, посечены фасады двух частных домов. ❗В посёлке Красная Яруга при детонации дрона посечены два автомобиля.

🤬1

20 Aug 2026, 17:20 UTC104 views1 reactionsread 21 August 2026

‼️В Ракитянском округе в посёлке Пролетарский FPV-дрон атаковал грузовой автомобиль. Мужчине со слепыми осколочными ранениями тела оказывают помощь в Ракитянской ЦРБ. Для продолжения лечения он будет направлен в городскую больницу №2 г. Белгорода. Транспорт получил повреждения. При атаке второго беспилотника повреждён объект инфраструктуры.

🤬1

20 Aug 2026, 17:19 UTC95 views1 reactionsread 21 August 2026

‼️В посёлке Красная Яруга в результате атак дронов выбиты окна коммерческого объекта и повреждены две машины.

🤬1

20 Aug 2026, 17:18 UTC95 views1 reactionsread 21 August 2026

‼️В Ракитянском округе в селе Криничное от удара беспилотника повреждено лобовое стекло автомобиля.

🤬1

Showing the 12 most recent of 20 posts we hold for @Yaruga_new. 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.

Appears in Telegram’s recommendations for other channels

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.

Доброволец | Военное дело
@Dobrovoleec · 55,695
Telegram ranks this channel #12 of 59 here — alongside 58 others — read 21 August 2026
Красная Яруга🇷🇺Ракитное Приграничье
@yaruga31 · 35,979
Telegram ranks this channel #19 of 32 here — alongside 31 others — read 2 September 2026
Красная Яруга🇷🇺
@krasnaya_yaruga31 · 29,942
Telegram ranks this channel #43 of 59 here — alongside 58 others — read 7 September 2026

This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“☀️🌞Красная яруга NEW🌞” (@Yaruga_new), 1,737 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/Yaruga_new.

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.