Channel
@redlineua
On this record: Topic · Growth · Engagement · Posts · Cite this entry
13,827subscribers
-8,679 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001420082130 |
|---|---|
| Type | Channel |
| Username | @redlineua |
| Created | 28 July 2020 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 29 October 2026 |
| Measurements held | 52 |
| Confirmed unchanged | 1 time, most recently 29 October 2026 |
| On Telegram | t.me/redlineua |
Politics & activism — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 49% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Oct 2026, 11:00 | 13,827 | -35 |
| 28 Oct 2026, 12:18 | 13,862 | -87 |
| 27 Oct 2026, 09:59 | 13,949 | -47 |
| 26 Oct 2026, 08:40 | 13,996 | -81 |
| 25 Oct 2026, 09:41 | 14,077 | -48 |
| 24 Oct 2026, 12:05 | 14,125 | -83 |
| 23 Oct 2026, 15:25 | 14,208 | -127 |
| 22 Oct 2026, 12:28 | 14,335 | -141 |
| 21 Oct 2026, 09:09 | 14,476 | -113 |
| 20 Oct 2026, 03:50 | 14,589 | -90 |
| 19 Oct 2026, 04:57 | 14,679 | -59 |
| 18 Oct 2026, 04:37 | 14,738 | -108 |
| 17 Oct 2026, 04:38 | 14,846 | -99 |
| 16 Oct 2026, 07:18 | 14,945 | -242 |
| 15 Oct 2026, 04:20 | 15,187 | -184 |
| 14 Oct 2026, 00:18 | 15,371 | -596 |
| 10 Oct 2026, 23:40 | 15,967 | -768 |
| 6 Oct 2026, 16:22 | 16,735 | -785 |
| 1 Oct 2026, 14:35 | 17,520 | -1,273 |
| 18 Sept 2026, 10:56 | 18,793 | first reading |
2 posts held, back to 28 July 2020 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 55 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 2 posts for this entry, the most recent from 16 July 2026. An engagement rate over an empty window would be a number about nothing.
Почему Зеленский сделал Хмару и.о. министра обороны? Этим решение Зеленский, вероятно, планирует убить сразу двух зайцев. Во-первых, Хмара в СБУ отвечал за дальние удары по РФ (дипстрайки), а потому имеет хороший имидж в обществе, что, как предполагают на Банковой, может сбить акции протеста в поддержку Федорова. Одно дело протестовать против назначения министром обороны мало кому известного бывшего главы МВД Климе…
Channel created
Showing the 2 most recent of 2 posts we hold for @redlineua. 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.
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 29 October 2026 — this entry's latest reading, not the date you are reading this.
“Червона Лінія” (@redlineua), 13,827 subscribers as measured 29 October 2026. Telegram Register, tgregister.com/channel/redlineua.
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.