Telegram RegisterThe public register of Telegram
Telegram profile photo for 🚧ДТП АРХАНГЕЛЬСКА🚧

Channel

🚧ДТП АРХАНГЕЛЬСКА🚧

@arhangelsklive

On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry

14subscribers

+1 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002308142275
TypeChannel
Username@arhangelsklive
Created16 December 2024 — measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live4 November 2026
Measurements held5
Confirmed unchanged7 times, most recently 4 November 2026
On Telegramt.me/arhangelsklive

Topic

Local community — 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 1 October 2026 and assigned it the closest of 31 fixed categories, at 81% 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

131413.56 August 2026 — 13 subscribers12 August 2026 — 13 subscribers21 August 2026 — 14 subscribers4 September 2026 — 13 subscribers12 September 2026 — 14 subscribers6 August 202612 September 2026
5 measurements spanning 37 days, net +1. 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 13–14 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Sept 2026, 15:3714+1
4 Sept 2026, 02:2013-1
21 Aug 2026, 08:4814+1
12 Aug 2026, 02:3113no change
6 Aug 2026, 10:0713first reading

Engagement

1 post held, back to 16 December 2024 — 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 1 post for this entry, the most recent from 16 December 2024. An engagement rate over an empty window would be a number about nothing.

Recent posts

Showing the 1 most recent of 1 post we hold for @arhangelsklive. 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.

Mentions

Named by 288 registered channels — 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

Named by

Channels on the register whose posts name this channel's handle.

Петербургский Радар
@piterpyrg_radar · 35,868
15 posts
Новости Брянска
@barakholka32 · 63,833
12 posts
Громко, курское приграничье!
@gromkokursk · 36,936
12 posts
Цифровая Сатира
@dfhumor · 35,731
10 posts
🚨 ЧП, Курское приграничье
@incidentkursk · 37,505
10 posts
Позже всех. Уже точно
@livefrom2007 · 72,604
10 posts
Подслушано село Пездово
@pezdovo_podslushano · 40,570
10 posts
Позже всех. Ну прости
@latenewz · 59,737
9 posts
птенец
@ptenetstg · 68,445
9 posts
Радар Саратов
@rada_saratov · 253,142
9 posts
Радар Брянск
@radar_bryanskk · 41,093
9 posts
Радар Чувашия
@radar_chuvashiya · 87,592
9 posts
Радар Краснодар
@radar_kras · 59,959
9 posts
Радар Москва
@radar_moscoww · 532,720
9 posts
Радар Питер и Ленинградская область
@radar_peterburg · 221,700
9 posts
Радар ПЛЮС • БПЛА • Мониторинг обстановки 24/7
@radar_plus_bpla · 228,197
9 posts
Радар Самара
@radar_samaraa · 84,148
9 posts
Радар Сочи(Адлер, Лазаревское, Сириус)
@radar_sochiii · 64,411
9 posts
Радар Татарстан
@radar_tatarstann · 50,112
9 posts
Радар Тверь
@radar_tver · 41,812
9 posts
Радар Волгоград
@radar_volgograd · 95,697
9 posts
Радар Воронеж
@radar_voronezh · 60,409
9 posts
Радар по всей России | Новости
@radarrussiia_novosti · 88,825
9 posts
Твич
@twitch_news_fan · 42,795
9 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.

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

“🚧ДТП АРХАНГЕЛЬСКА🚧” (@arhangelsklive), 14 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/arhangelsklive.

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.