На дорогу смотри, дура!
😁1

Channel
@gorodovye
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
67subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001294574110 |
|---|---|
| Type | Channel |
| Username | @gorodovye |
| Description | Посмотрим на себя со стороны. Почта: [email protected] |
| Created | 9 October 2019 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/gorodovye |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 01:16 | 67 | no change |
| 7 Aug 2026, 05:40 | 67 | first reading |
9 posts held, back to 8 August 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 pageof 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 9 posts for this entry, the most recent from 5 June 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 10 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
5 reactions across 3 posts, in 3 distinct kinds. The most used accounts for 40.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 40.0% | |
| 👍 | 2 | 40.0% | |
| 😁 | 1 | 20.0% |
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 4 of the 9 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 5reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 8 August 2024 to 5 June 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
Ну и денек...
"Выручка фуникулера в Нижегородском кремле за месяц достигла 9,6 млн рублей. Воссозданный элеватор был запущен 15 сентября. К 14 октября на нем прокатились 48,9 тысячи пассажиров." / Гипер-НН Даже если предположить, что поток пассажиров сохранится: 1,8 млрд / 9,6 млн / 12 месяцев = 15,6 лет + налоги, ЗП, электроэнергия, ремонт и прочее.
Городовые - новые. Порядки - старые. Теперь вопросы нужно задавать не ряженным в папахах или перепуганному бухгалтеру, а в мэрии Нижнего Новгорода.
В микрорайоне Мещерское озеро разрушили скульптуру «Прорыв». NN.RU со ссылкой на администрацию торгового центра «Небо» сообщает, что решение приняло руководство. Источник: kommersant.ru
❤1
Это тот самый? https://www.kommersant.ru/doc/7182392
Граффити по заказу, на мой взгляд, редко получаются хорошими. Но это прям удачное. Фото: Юрий Шалабаев
👍2❤1
Автомобильный проезд планируется открыть под Триумфальной аркой, которая будет воссоздана в Канавинском районе. С одной стороны интересная, с другой странная идея. Если раньше с арки открывался вид на собор и ярмарку, то теперь дорога ведет в "яму".
Петиция за сохранение книжного магазина "кНижный Новгород" по адресу ул. Алексеевская 2 https://chng.it/qQkVpXW9zN
Showing the 9 most recent of 9 posts we hold for @gorodovye. 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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“Городовые” (@gorodovye), 67 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/gorodovye.
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.