Other / unclassifiable — 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 27 September 2026 and assigned it the closest of 31 fixed categories, at 50% 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.
Growth
8 measurements spanning 80 days, net -21. 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 79–106 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
28 Oct 2026, 19:19
82
-1
13 Oct 2026, 18:40
83
-5
3 Oct 2026, 20:18
88
-4
10 Sept 2026, 23:02
92
-2
1 Sept 2026, 08:36
94
-6
24 Aug 2026, 18:07
100
-3
10 Aug 2026, 15:51
103
no change
9 Aug 2026, 19:17
103
first reading
Engagement
17 posts held, back to 24 July 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 17 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
50 reactions across 16 posts, in 8 distinct kinds. The most used accounts for 50.0% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
custom 5429277624981538430
25
50.0%
custom 5429226690964374907
8
16.0%
custom 5429164809075574615
5
10.0%
custom 5429311254575465998
5
10.0%
custom 5416076321442777828
3
6.00%
custom 5411197345968701560
2
4.00%
custom 5363978187753670318
1
2.00%
custom 5435857540648813250
1
2.00%
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 16 of the 17 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 50 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 24 July 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.
📰 СВОДКА НОВОСТЕЙ ЗА 5–6 АВГУСТА
━━━━━━━━━━━━━━━━━
Привет, Горизонт!
Прошу прощения, что долго не было новостей — небольшая пауза, но я вернулся. Наверстываю упущенное.
RP по Фандомам 🎭
Владелец проекта вышел из тени и сразу обозначил позицию. Три новых правила:
запрет на использование нейросетей для анкет
запрет на ИИ в постах
запрет на созывы без веской причины
Теперь только живое творчество, без автоматизации…
📰 Скромная сводка новостей за последние 2 дня (31 июля - 1 августа 2026
━━━━━━━━━━━━━━━━━━━
В этот раз ещё меньше. Прошу простить. Новостей не так много.
Rise of World II 🏛️
Владелец проекта Кофе опубликовал завещание на случай своего неактива. Все полномочия переходят к заместителю Кхаву. В завещании прописаны права на назначение админов, изменение настроек и баны.
Говорят, что Кофе возвращается к работе — обещае…
📰 Сводка новостей за последние 2 дня (29-30 июля 2026)
━━━━━━━━━━━━━━━━━━━
Новостей в этот раз не так много, прошу простить, но я собрал всё, что смог.
Яблочное РП 🍏
Не так много новостей. Глава объявил снижение лимита неактива до 10 дней. Более новостей не было найдено.
Lord Roleplay ⚔️
В проекте готовятся изменения.
Администрация вынесла на голосование вопрос: снятие одного из старших администраторов. Итоги пок…
⚡️📰 Эксклюзив: угрозы владельцу канала Феникз
━━━━━━━━━━━━━━━━━━━
Сегодня в ВПИ-сообществе произошёл инцидент, который может иметь последствия.
В чате НИВА появилось сообщение от неизвестного пользователя, содержавшее угрозы в адрес владельца ролевого канала Феникз — utimij'а. Сообщение было тут же удалено самим utimij'ем, но осадок остался.
━━━━━━━━━━━━━━━━━━━
Кто такой utimij?
Для тех, кто в бункере — utimij изв…
⚔️ Ржев: цена забытой победы
1942 год. Ржевско-Вяземский выступ.
Немцы называют его «оружием возмездия» — плацдармом для нового удара по Москвы. Отсюда до столицы всего 200 километров.
Здесь сосредоточено 2/3 всех сил группы армий «Центр». Гитлер приказал стоять насмерть. Ржев — «ворота на Берлин».
А по ту сторону окопов — Красная армия. И приказ тот же.
━━━━━━━━━━━━━━━━━━━━
Тактика
Почему же Ржев стал «мясору…
📰 Сводка новостей за последние 2 дня (27-28.07.2026)
━━━━━━━━━━━━━━━━━━━━━
Helios Roleplay ⚡
Вчера на проекте стартовала полноценная весьма активная игра после вайпа на 2026 год. Участники уже осваиваются — страны распределены, пошли первые новости и заявления от игроков. Жизнь на сервере набирает обороты.
Rise of World 🏛️
Голосование позади — вайп будет. Вчера игроки выбрали 1980 год и почти сразу проголосовали за…
📰 Сводка новостей за 27.07.2026
━━━━━━━━━━━━━━━━━━━
Helios Roleplay ⚡
В проекте прошли голосования за год вайпа.
По их итогам выбран 2026 год.
Сейчас идёт вайп. Игроки уже могут бронировать страны и заполнять анкеты. Проект оживает, участники выбирают свои государства и готовятся к старту.
Rise of World 🏛️
Голосование за вайп в проекте обернулось настоящей драмой.
Сначала неактивные игроки потребовали вайп на 193…
POVA Sphere - это ваше место, где вы можете прорекламировать свой проект
Мы рекламируем каналы, РП и чаты
Вся реклама в канале бесплатная
Если вы хотите прорекламировать свой проект, то пишите: @privet_moy_pups / @Nol1xx
Showing the 12 most recent of 17 posts we hold for @orizzonte_news. 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.
Polls
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Новостник, в котором есть другие рубрики, но новостных постов большинство43%
Новостник, в котором рубрик больше, чем новостных постов37%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 17 most recent posts we hold, published 24 July 2026 to 7 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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 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.
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.
Handles this channel named that no longer answer
Dead references
1
handles named in this channel’s posts, vacant today
Evidenced gone
1
we ourselves saw one of these resolve, at some point
Never seen alive
0
vacant every time we have ever looked
@orizzonte_news named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
@titan_news_roleplay named in 3 posts, 10 August 2026 – 10 August 2026 · confirmed gone 15 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
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 28 October 2026 — this
entry's latest reading, not the date you are reading this.
“Горизонт” (@orizzonte_news), 82 subscribers as measured 28 October 2026. Telegram Register, tgregister.com/channel/orizzonte_news.
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.