Telegram RegisterThe public register of Telegram

Channel

Зеленоград - происшествия, розыск и находки

@zelenograd_chp

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

11,666subscribers

+143 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001562405642
TypeChannel
Username@zelenograd_chp
DescriptionВсе происшествия Зеленограда и окрестностей. Розыск и находки. Новости, вопросы, объявления, предложения: @zelenogradru_contact Реклама: @zelenogradru_reklama Правила комментариев t.me/zelenogradru_chat/163333 6125235760 18+
CreatedBetween 1 August 2021 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live12 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/zelenograd_chp

Topic

Local community — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 78% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (1 of the pairs behind the counts below)
Posted firstThenOverlapGap
@zelenograd_andreevka/35863 Aug 2026, 11:02 UTC@zelenograd_chp/5499 · this entry3 Aug 2026, 11:03 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@zelenograd_andreevka5 (5/5 hand-verifiable sample passed)1.00under a minute@zelenograd_andreevka (50)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 1 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 22 comparable posts for this entry, running 30 July 2026 to 7 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 2, the earliest publisher we hold is @zelenograd_andreevka. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

11,52311,66811,595.57 August 2026 — 11,523 subscribers7 August 2026 — 11,563 subscribers8 August 2026 — 11,578 subscribers9 August 2026 — 11,579 subscribers10 August 2026 — 11,660 subscribers11 August 2026 — 11,668 subscribers12 August 2026 — 11,666 subscribers11,6667 August 202612 August 2026
7 measurements spanning 5 days, net +143. 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 11,501–11,690 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 06:3711,666-2
11 Aug 2026, 08:1411,668+8
10 Aug 2026, 07:1011,660+81
9 Aug 2026, 07:1211,579+1
8 Aug 2026, 08:0411,578+15
7 Aug 2026, 10:3211,563+40
7 Aug 2026, 01:0211,523first reading

Engagement

29 posts held, back to 30 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 15 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
50.4%
avg views ÷ 11,666 subscribers
Avg views / post
5,880
29 posts measured
Reaction rate
0.518%
reactions ÷ views · ER floor
Posts in window
29
of 29 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. It is computed over the 26 of 29 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 12 August 2026
Posts held29 (30 July 202612 August 2026)
Views total170,540
Reactions total811
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 13:02 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.

What this channel posts

Photos
4,120
Videos
553
Links
1,990

Lifetime counters from Telegram’s own channel header, read 12 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.

Video runtime
2m 27s
Average length
37s

Measured directly from 4 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

811 reactions across 26 posts, in 26 distinct kinds. The most used accounts for 10.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤬8710.7%
😢8610.6%
😱8510.5%
🤯799.74%
749.12%
🙏718.75%
💔647.89%
😁526.41%
👍425.18%
😭404.93%
😡303.70%
👎263.21%
😨222.71%
🤣121.48%
👀111.36%
🙉101.23%
🔥50.617%
😍40.493%
🕊20.247%
🤔20.247%
6 further kinds70.863%

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 26 of the 29 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 811reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 29 most recent posts we hold, published 30 July 2026 to 12 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.

Recent posts

12 Aug 2026, 07:49 UTC≈1,480 views3 reactionsread 12 August 2026
Forwarded from @zelenograd_3mkrPhoto

Большая ветка упала на машину во дворе 3-го микрорайона. Что делать в такой ситуации Пострадал припаркованный Ford Explorer ветка лежит на лобовом стекле и крыше автомобиля. Есть ли повреждения, пока неизвестно. Если дерево или ветка упали на вашу машину, главное — не убирать их и не передвигать автомобиль до фиксации происшествия полицией и, при необходимости, страховой компанией. Что делать по шагам👇 ✹ Сначала

2🤯1

11 Aug 2026, 10:27 UTC≈2,730 views8 reactionsread 12 August 2026
Forwarded from @zelenograd_20mkrVideo

Гости полезли в квартиру с козырька подъезда после конфликта с хозяином в 20-м микрорайоне Компания распивала спиртное в квартире 40-летнего мужчины. Во время застолья между хозяином и одним из гостей произошел конфликт. Гость нанес мужчине несколько ударов по лицу и туловищу. Позднее гости покинули квартиру, а затем попытались вернуться. Хозяин отказался их впускать. После этого в полицию сообщили, что неизвестные

🤬42🕊2

10 Aug 2026, 17:38 UTC≈3,460 views2 reactionsread 12 August 2026

Разыскиваются свидетели ДТП 10 августа около 12:30 был повреждён автомобиль Haval F7x белого цвета. Он был припаркован возле корпуса 807, напротив стоянки детской поликлиники №105. Автомобиль получил царапины и вмятины. Соответствующие службы зарегистрировали данный факт и принимают все необходимые меры по выяснению обстоятельств. Если вы обладаете какой-либо информацией или были свидетелем происшествия, просьба на

🙏2

10 Aug 2026, 15:54 UTC≈3,030 views21 reactionsread 12 August 2026
Forwarded from @voditeli_zelenogradVideo

Водителя без номеров преследовали от 8-го микрорайона и задержали за границами Зеленограда Автоинспекторы заметили в 8-м микрорайоне иномарку без государственных номеров и потребовали от водителя остановиться. Тот не подчинился и поехал дальше. Полицейские начали преследование. Водителю удалось выехать за границы Зеленограда, где автоинспекторы заблокировали автомобиль и остановили его. Водитель вышел из машины и п

🤬17🤣31

10 Aug 2026, 06:27 UTC≈3,090 views37 reactionsread 12 August 2026
Forwarded from @voditeli_zelenogradPhoto

Километровая пробка образовалась в понедельник утром на въезде в Зеленоград на Панфиловский проспект По словам водителей, причина — поломанный светофор на перекрестке Панфиловского и Центрального проспекта. Светофор не работает с субботу, хотя водители оставляли заявки в департамент транспорта по телефону 3210. Водители Зеленограда / Чат водителей

😡29🤬52😁1

9 Aug 2026, 13:33 UTC≈4,220 views27 reactionsread 12 August 2026
Photo

В «Зеленопарке» началась эвакуация после письма с угрозой взрыва ❗️Обновление: эвакуация завершена — ТЦ открыт Посетителей выводят из торгового центра, в том числе из кинотеатра. Причина эвакуации официально не объявлена, однако незадолго до этого «Зеленопарк» и ещё несколько организаций Зеленограда получили письма с угрозами. Очевидцы жалуются на организацию эвакуации. По словам посетительницы, сообщение о необхо

🤯185🥰2🤣1🙏1

9 Aug 2026, 12:22 UTC≈14,500 views9 reactionsread 12 August 2026

Нескольким торговым центрам Зеленограда отправили письма с угрозой взрыва Автор письма утверждает, что здания заминированы, и требует в течение часа два миллиона рублей, чтобы «избежать последствий». Письмо отправлено в 14:31 и пока никаких последствий не было. В списке получаталей указаны адреса электронной почты торговых центров «Столица», «Панфиловский», «Грин» и «Зеленопарк», фудмола «Станция», а также Культурн

9

7 Aug 2026, 19:27 UTC≈4,590 viewsread 12 August 2026
Forwarded from @zelenograd_17mkr

Потерян кейс от AirPods 4 6 августа около 22:00 в 17-м микрорайоне был потерян кейс от AirPods 4. Кейс находился в фиолетовом чехле. Если вы нашли его, пожалуйста, свяжитесь в Telegram: https://t.me/DirtiestFrame Новости 17-го микрорайона | Чат в Телеграме | Чат в Максе

7 Aug 2026, 08:59 UTC≈20,800 views69 reactionsread 12 August 2026

Источником громкого хлопка оказался самолёт Причиной оказался пролетавший на сверхзвуковой скорости самолёт Су-35, по данным мониторинговых каналов. Ранее, примерно в 11:15, жители Зеленограда и ближайших территорий сообщили о громком звуке, похожем на хлопок. Об этом писали в чатах «Зеленоград.ру», звук также слышали в разных районах Москвы. @zelenograd_chp | Канал в Максе | Канал в ВК

😁45👎192🤔2👍1

7 Aug 2026, 08:41 UTC≈18,200 views14 reactionsread 12 August 2026

Громкий хлопок услышали жители Зеленограда и окрестностей В чатах «Зеленоград.ру» пишут, что его также слышали в разных районах Москвы. По сообщениям мониторинговых каналов (так называемые «радары»), звуки опасности не несут, на территории региона проводятся работы по уничтожению обломков. Официальной информации о произошедшем пока нет. Если вы знаете подробности, напишите в комментариях. @zelenograd_chp | Канал

👍10🙏3🍾1

7 Aug 2026, 05:14 UTC≈4,200 views37 reactionsread 12 August 2026
Forwarded from @zelenogradruPhoto

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

🤬26🤯65

6 Aug 2026, 18:56 UTC≈4,360 views2 reactionsread 12 August 2026
Forwarded from @zelenograd_andreevka

Электричество отключат на один час 7 августа в части Андреевки В пятницу технические работы на электросетях проведут в микрорайоне Высокое и коттеджном посёлке «Зелёный городок». Работы запланированы с 8:00 до 17:00, однако продолжительность отключения для абонентов не должна превысить одного часа. Точное время отключения не указано. По вопросам электроснабжения можно обращаться в круглосуточный контактный центр «

2

Showing the 12 most recent of 29 posts we hold for @zelenograd_chp. 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 — 127,080 of 1,151,006entries 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

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.

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

“Зеленоград - происшествия, розыск и находки” (@zelenograd_chp), 11,666 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/zelenograd_chp.

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.