Channel
@igor_arsentyev
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Referenced elsewhere · Cite this entry
1,180subscribers
-14 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001347239243 |
|---|---|
| Type | Channel |
| Username | @igor_arsentyev |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 28 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 28 September 2026 |
| On Telegram | t.me/igor_arsentyev |
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 89% 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 |
|---|---|---|
| 28 Sept 2026, 01:41 | 1,180 | -9 |
| 18 Sept 2026, 05:39 | 1,189 | -3 |
| 14 Sept 2026, 06:38 | 1,192 | +4 |
| 10 Sept 2026, 15:59 | 1,188 | +2 |
| 5 Sept 2026, 15:39 | 1,186 | +1 |
| 30 Aug 2026, 11:35 | 1,185 | +1 |
| 27 Aug 2026, 05:05 | 1,184 | +1 |
| 24 Aug 2026, 15:05 | 1,183 | -4 |
| 17 Aug 2026, 10:06 | 1,187 | -3 |
| 13 Aug 2026, 17:54 | 1,190 | -2 |
| 11 Aug 2026, 00:54 | 1,192 | -1 |
| 7 Aug 2026, 18:11 | 1,193 | -1 |
| 6 Aug 2026, 19:31 | 1,194 | first reading |
6 posts held, back to 5 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 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 6 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
26 reactions across 6 posts, in 6 distinct kinds. The most used accounts for 38.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 10 | 38.5% | |
| 🔥 | 7 | 26.9% | |
| ⚡ | 3 | 11.5% | |
| 🤝 | 3 | 11.5% | |
| 🙏 | 2 | 7.69% | |
| ❤ | 1 | 3.85% |
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 6 of the 6 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 26 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 5 August 2026 to 6 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.
Со вчерашнего дня поступают сообщения от жителей о серьезных пробках на въезде в город. Понимаю, как это всех злит, отнимает время и мешает планировать день. Сегодня связался с подрядчиком и заказчиком работ: по информации от дорожников, сегодня ночью они завершают укладку асфальта на текущем участке на въезде в Северодвинск и переходят на следующий — с 1 по 13 километр в районе посёлка Пирсы. Там из-за колецности пр…
👍2🤝1🙏1
Муниципальные округа Архангельской области за последние пять лет состоялись, как новый уровень публичной власти. Но сегодня важно не останавливаться на достигнутом, а вместе с правительством региона и главами муниципалитетов определять новые точки роста, чтобы каждый житель видел реальные изменения на своей территории. Именно этому посвящена серия форумов «Сильные муниципалитеты – сильный регион». Сегодня мероприятие…
👍1🔥1🤝1
Продолжил встречи в Котласском округе с трудовыми коллективами – сегодня с котласским подразделением «Россетей». Разговор с энергетиками получился честным: обсудили как существующие проблемы, так и перспективы развития отрасли. Коллеги подняли важный вопрос – необходимость сделать профессию энергетика более привлекательной и востребованной для молодого поколения. Это напрямую связано с уровнем заработной платы, социа…
👍2🔥1🙏1
В Северодвинске продолжается ремонт дворовых территорий. Сегодня дорожные работы идут во дворе домов № 37 и 39 на проспекте Ленина. Внутриквартальный проезд ведёт к Совету ветеранов войны и труда Севмаша, который посещают многие жители старшего поколения, поэтому этот объект был для нас в приоритете. Жители давно просили привести территорию в порядок. От старого асфальта здесь практически ничего не осталось, поэтому …
👍1🔥1🤝1
Во время рабочей поездки в Котлас не мог не заглянуть в дом на улице Луговой, где почётно висит табличка: «Они защищали Родину». Николай Васильевич Белоруков – участник Великой Отечественной войны, человек, чья юность началась в нашем городе, Молотовске. В 15 лет он пришёл работать на завод №402 (ныне «Севмаш») в инструментальный цех. Позже Николай Васильевич ушёл на фронт в 17 лет, приписав себе год. Командовал взв…
👍2🔥2⚡1❤1
Сегодня работаю в Котласе на форуме «Сильные муниципалитеты – сильный регион». Мы собрались, чтобы подтвердить главное: когда муниципалитет способен принимать решения, реализовывать проекты и нести ответственность – меняется жизнь людей. Выступил на форуме от имени Ассоциации «Совет муниципальных образований Архангельской области». Сегодня мы видим беспрецедентное внимание федерального центра и лично Президента РФ В…
⚡2👍2🔥2
Showing the 6 most recent of 6 posts we hold for @igor_arsentyev. 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.
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.
Named by 4 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.
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.
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 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
This handle named by sources this register does not control and did not measure — each shown exactly as found, attributed by name, dated to when it was read.
Wikipedia
One Wikipedia article names this handle in its article text, found by searching for a t.me link inside the article source. A citation is a notability signal, not a verification: nobody here confirmed the cited post is genuine or still says what the article quotes. Article text is CC BY-SA 4.0, Wikipedia contributors; snippets below are short excerpts.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“АРСЕНТЬЕВ LIVE” (@igor_arsentyev), 1,180 subscribers as measured 28 September 2026. Telegram Register, tgregister.com/channel/igor_arsentyev.
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.