Telegram RegisterThe public register of Telegram
Telegram profile photo for Регион-52 | Нижний Новгород 📢

Channel

Регион-52 | Нижний Новгород 📢

@novgorod_52

On this record: Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry

635subscribers

+4 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001406223606
TypeChannel
Username@novgorod_52
Created16 August 2019measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded8 August 2026
Last confirmed live29 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 29 August 2026
On Telegramt.me/novgorod_52

Growth

630635632.57 August 2026 — 631 subscribers7 August 2026 — 630 subscribers8 August 2026 — 630 subscribers22 August 2026 — 632 subscribers29 August 2026 — 635 subscribers7 August 202629 August 2026
5 measurements spanning 22 days, net +4. 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 629–636 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 03:36635+3
22 Aug 2026, 18:38632+2
8 Aug 2026, 02:50630no change
7 Aug 2026, 23:14630-1
7 Aug 2026, 12:14631first reading

Engagement

20 posts held, back to 6 August 2026the 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.

ERR · 30 days
3.65%
avg views ÷ 635 subscribers
Avg views / post
23.1
20 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
20
of 20 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held20 (6 August 20267 August 2026)
Views total463
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 02:50 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.

Recent posts

7 Aug 2026, 20:14 UTC10 viewsread 8 August 2026
Photo

🎈 Нижний Новгород снова готовится к одному из самых красивых событий лета. С 13 по 17 августа здесь пройдет «Приволжская фиеста». Десятки ярких аэростатов поднимутся в небо, а город на несколько дней станет настоящей столицей воздушных шаров. Если давно хотели увидеть это своими глазами — не откладывайте. Такие моменты бывают всего раз в году. 📸 Никита Духник

7 Aug 2026, 18:48 UTC19 viewsread 8 August 2026
Photo

🚛 На трассе М-12 перевернулся и вспыхнул большегруз. Авария произошла на 569-м километре трассы. После опрокидывания фура загорелась. Информация о пострадавших и причинах ДТП уточняется.

7 Aug 2026, 17:30 UTC24 viewsread 8 August 2026
Photo

🚤 Пьяная прогулка на лодке закончилась судом. Выксунский суд вынес приговор мужчине, который летом прошлого года катал подростков по реке в нетрезвом виде. На носу моторной лодки находились трое детей, из-за чего водитель практически не видел, что происходит впереди. Во время движения лодка врезалась в бакен. Подростки оказались в воде, а один из них получил тяжелую травму головы. Мужчина полностью признал вину. С

7 Aug 2026, 14:50 UTC22 viewsread 8 August 2026
Photo

Пассажирка «Оки», в которую на Заревской объездной дороге в Дзержинске врезался грузовик, погибла. Водитель легковушки выжил — его с травмами доставили в больницу. После смертельного ДТП возбудили уголовное дело по статье о нарушении ПДД, повлекшем по неосторожности смерть человека. По данным ГУ МВД по Нижегородской области, молодой водитель большегруза признал свою вину.

7 Aug 2026, 13:48 UTC22 viewsread 8 August 2026
Photo

🚗 В Воскресенском районе Нижегородской области смертельное ДТП: погиб 39-летний мужчина. Авария произошла утром 7 августа на дороге Калиниха — Елдеж — Орехи. По предварительным данным ГАИ, 31-летний водитель автомобиля Kaiyi не выбрал безопасную скорость, не справился с управлением, съехал в кювет и врезался в дерево. 39-летний пассажир получил смертельные травмы и погиб на месте. Обстоятельства аварии выясняются.

7 Aug 2026, 12:57 UTC21 viewsread 8 August 2026
Photo

👀 Появились кадры со второго яруса «Volga Арены» в Нижнем Новгороде. С этой точки открывается отличный вид на всю площадку — можно оценить масштаб нового пространства практически целиком.

7 Aug 2026, 11:39 UTC24 viewsread 8 August 2026
Photo

🦓 Малышке-зебре, которая не так давно появилась на свет в «Лимпопо», выбрали имя. Знакомьтесь, ее зовут Мира!

7 Aug 2026, 10:46 UTC28 viewsread 8 August 2026
Photo

🛌 Нижегородские врачи спасли мужчину, который получил тяжёлую травму после… падения с кровати. Пациент просто рухнул ночью с кровати на пол. После случившегося он прошёл лечение, но позже заметил болезненное образование на животе. Обследование показало разрыв диафрагмы и грыжу, из-за которой часть кишечника сместилась в грудную полость. Торакальные хирурги ГКБ № 5 провели сложную операцию, вернули кишечник на место

7 Aug 2026, 08:10 UTC26 viewsread 8 August 2026
Photo

Крупный пожар на деревообрабатывающем предприятии в Воротынском округе. На площади 1000 квадратов горели отходы производства. Была угроза распространения огня на соседние здания, но пламя удалось вовремя потушить. К счастью, погибших и пострадавших нет. По данным МЧС, предварительная причина пожара — поджог.

7 Aug 2026, 08:10 UTC26 viewsread 8 August 2026
Photo

Ждём Вас в «Управдом» по адресу: ул. Коминтерна, д. 127 пл. Советская, д. 5, МП-18 Загляните на наш сайт: https://vk.cc/d0fAPV

Showing the 12 most recent of 20 posts we hold for @novgorod_52. 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.

Citation-graph rank

Citation-graph rank — 633,043 of 1,624,174entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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.

Mentions

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.

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.

Appears in Telegram’s recommendations for other channels

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.

Подслушано Нижний Новгород
@novgorod_nizhniy · 104,587
Telegram ranks this channel #64 of 85 here — alongside 84 others — read 20 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Регион-52 | Нижний Новгород 📢” (@novgorod_52), 635 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/novgorod_52.

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.