Channel
@golikov_v_g
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
2,760subscribers
-26 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003277375916 |
|---|---|
| Type | Channel |
| Username | @golikov_v_g |
| Created | Between 1 October 2025 and 28 February 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/golikov_v_g |
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 15 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 06:00 | 2,760 | -5 |
| 13 Sept 2026, 15:20 | 2,765 | -1 |
| 9 Sept 2026, 22:15 | 2,766 | -4 |
| 31 Aug 2026, 17:04 | 2,770 | -2 |
| 28 Aug 2026, 09:03 | 2,772 | -6 |
| 24 Aug 2026, 23:54 | 2,778 | -1 |
| 21 Aug 2026, 01:32 | 2,779 | -3 |
| 18 Aug 2026, 07:22 | 2,782 | -1 |
| 15 Aug 2026, 02:13 | 2,783 | -3 |
| 8 Aug 2026, 03:20 | 2,786 | no change |
| 8 Aug 2026, 03:19 | 2,786 | first reading |
3 posts held, back to 7 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 3 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
На этой неделе провели расширенное оперативное совещание, на котором рассмотрели итоги работы за истекший период и обозначили приоритеты на предстоящий этап. ✅Безопасность. - В жаркие дни усилен контроль за местами купания для предотвращения несчастных случаев. Особое внимание уделяем профилактике детского травматизма. В связи с подготовкой к осенне-зимнему периоду активизируем работу, направленную на недопущение во…
Провел очередной личный прием граждан. Обсуждали вопросы ЖКХ, соцподдержки, дорог и благоустройства. Остановлюсь на некоторых подробнее. ✅ Память и забота. Ко мне обратилась мать погибшего участника СВО из села Заломного. Ее волнует состояние дорог — подъезда к дому и к местному кладбищу, а также обустройство площадки для прощаний с твердым покрытием и лавочками. Дал поручение профильным службам проработать все эти …
На прошлой неделе на территории нашей будущей художественной школы провели очередную рабочую встречу. Собрались с заместителями и руководителями подрядных организаций, чтобы лично оценить ситуацию на объекте. Работы идут строго по утверждённому графику, что не может не радовать. Специалисты уже ведут закупку необходимого оборудования и инвентаря — к открытию всё будет на своих местах. Вместе с подрядчиком проверили …
Showing the 3 most recent of 3 posts we hold for @golikov_v_g. 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 2 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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“Василий Голиков” (@golikov_v_g), 2,760 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/golikov_v_g.
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.