Channel
@vereshchaginkolomna
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
124subscribers
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004441515814 |
|---|---|
| Type | Channel |
| Username | @vereshchaginkolomna |
| Description | Официальный канал временно исполняющего обязанности главы Городского округа Коломна |
| Created | 23 September 2026 — measured — dated from the channel’s first post |
| First recorded | 26 September 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 1 |
| On Telegram | t.me/vereshchaginkolomna |
Growth history is still building. We hold one measurement for this entry. A trend needs at least two, taken days apart — so this will fill in on its own rather than being estimated. We do not publish numbers we have not measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Sept 2026, 21:22 | 124 | first reading |
7 posts held, back to 23 September 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.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 26 September 2026 |
|---|---|
| Posts held | 7 (23 September 2026 – 26 September 2026) |
| Views total | 887 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 26 Sept 2026, 21:22 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 26 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Работали с командой в обновленном парке 50-летия Октября. Обсудили безопасность отдыхающих. Новая лыжероллерная трасса загружена постоянно: здесь идут тренировки, спортсмены развивают высокую скорость. При этом по соседним аллеям гуляют семьи с колясками, пожилые люди, бегают малыши. Чтобы исключить риски, одну сторону трассы уже оборудовали защитным ограждением. Поручил поставить предупреждающие знаки о скоростном …
Принял участие в заседании областного штаба по теплу в режиме ВКС. С руководителями ресурсоснабжающих организаций рассмотрели важные вопросы вхождения в отопительный сезон. К пробным топкам в округе приступили с 24 сентября. Тепло подаем поэтапно, в первую очередь - в социальные учреждения, далее – в жилой сектор.
70 лип и кленов посадили сегодня на берегу реки Оки на улице Малое Колычево. Благодарю всех, кто не испугался непогоды и присоединился к доброму делу. Около 100 человек приняли участие в экологической акции «Сохраним лес». Пример всем подала наша молодежь: активисты «Волонтеров Подмосковья» и «Молодой гвардии». Сажать деревья именно на этом участке начали еще в 2024 году про просьбам жителей. Вместе с депутатом Мосо…
Вместе с командой проведем выездную администрацию в деревне Зарудня 30 сентября. Встреча тематическая, обсудим вопросы дорожного хозяйства и транспорта. Приглашаю присоединиться всех, кому есть что спросить и что сказать. Место встречи – Маливская школа, начало в 17:00.
Рабочий день начал с утреннего обхода территории. На повестке дня – темы дорог, капремонта и благоустройства. Вместе с командой и представителями МБУ «САХ» уже составили план ближайших объездов. Программу капремонта, о которой говорил на совещании губернатор Андрей Юрьевич Воробьев, берем на особый контроль. Сейчас ремонтируем 20 жилых домов.
Друзья! Земляки! Мне выпала большая честь возглавить Городской округ Коломна. С 22 сентября я приступил к обязанностям в должности временно исполняющего полномочия главы. Я вырос в Коломне, она всегда была для меня родной, здесь моя семья и близкие мне люди. Благодарю нашего губернатора Андрея Юрьевича Воробьева за оказанное доверие. На первом месте для меня всегда стоят интересы жителей — их комфорт и благополуч…
Channel created
Showing the 7 most recent of 7 posts we hold for @vereshchaginkolomna. 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.
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.
Names
Channels on the register whose handles appear in this channel's 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.
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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“Виктор Верещагин, врип главы Г.о. Коломна” (@vereshchaginkolomna), 124 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/vereshchaginkolomna.
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.