Telegram RegisterThe public register of Telegram
Telegram profile photo for Новая Москва

Channel

Новая Москва

@novaya_moskva_tinao

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry

9,331subscribers

+102 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001206388901
TypeChannel
Username@novaya_moskva_tinao
DescriptionПрислать новость 👉 t.me/novaya_moskva_tinao?direct По рекламе 👉 @AMRL_RU Новости ТиНАО НАО ТАО 📍Новости Коммунарки, Бекасово, Внуково, Вороново, Филимонковский, Щербинка, Троицк, Краснопахорский, Южное Бутово, Сосенское, Московский, Кокошкино
CreatedBetween 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 November 2026
Measurements held24
Confirmed unchanged2 times, most recently 13 November 2026
On Telegramt.me/novaya_moskva_tinao

Topic

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 11 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 the other topics.

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 in near-verbatim form on 2 other registered channels. 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 (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@tinao_top/366727 Aug 2026, 07:53 UTC@novaya_moskva_tinao/5603 · this entry7 Aug 2026, 17:08 UTC0.979.3 hours
@tinao_top/366807 Aug 2026, 14:52 UTC@novaya_moskva_tinao/5605 · this entry7 Aug 2026, 17:09 UTC0.962.3 hours
@tinao_top/3737826 Aug 2026, 14:51 UTC@novaya_moskva_tinao/6125 · this entry26 Aug 2026, 16:17 UTC0.9586 minutes
@tinao_top/3744628 Aug 2026, 03:47 UTC@novaya_moskva_tinao/6163 · this entry28 Aug 2026, 07:01 UTC0.943.2 hours
@tinao_top/3716121 Aug 2026, 12:41 UTC@novaya_moskva_tinao/6023 · this entry21 Aug 2026, 13:14 UTC0.9134 minutes
@tinao_top/3698115 Aug 2026, 06:45 UTC@novaya_moskva_tinao/5825 · this entry15 Aug 2026, 07:18 UTC0.9133 minutes
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@tinao_top8 (8/8 hand-verifiable sample passed)0.931.9 hours@tinao_top (8–0)
@barmashevonline5 (5/5 hand-verifiable sample passed)0.9439 minutes@barmashevonline (5–0)

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. 13 of the 13 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 237 comparable posts for this entry, running 4 August 2026 to 17 November 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).

Recorded under the key clone_copy, last confirmed 18 November 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.

Growth

9,2299,3439,2866 August 2026 — 9,229 subscribers6 August 2026 — 9,232 subscribers9 August 2026 — 9,248 subscribers12 August 2026 — 9,262 subscribers15 August 2026 — 9,274 subscribers18 August 2026 — 9,271 subscribers21 August 2026 — 9,285 subscribers24 August 2026 — 9,289 subscribers27 August 2026 — 9,293 subscribers30 August 2026 — 9,294 subscribers2 September 2026 — 9,287 subscribers8 September 2026 — 9,291 subscribers12 September 2026 — 9,297 subscribers15 September 2026 — 9,305 subscribers27 September 2026 — 9,319 subscribers5 October 2026 — 9,324 subscribers11 October 2026 — 9,331 subscribers15 October 2026 — 9,343 subscribers18 October 2026 — 9,337 subscribers21 October 2026 — 9,331 subscribers30 October 2026 — 9,334 subscribers2 November 2026 — 9,329 subscribers5 November 2026 — 9,330 subscribers9 November 2026 — 9,331 subscribers9,3316 August 20269 November 2026
24 measurements spanning 95 days, net +102. 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 9,212–9,360 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 24
Measured (UTC)SubscribersChange
9 Nov 2026, 02:009,331+1
5 Nov 2026, 09:499,330+1
2 Nov 2026, 08:389,329-5
30 Oct 2026, 16:209,334+3
21 Oct 2026, 13:289,331-6
18 Oct 2026, 07:049,337-6
15 Oct 2026, 00:399,343+12
11 Oct 2026, 20:199,331+7
5 Oct 2026, 10:179,324+5
27 Sept 2026, 06:389,319+14
15 Sept 2026, 19:199,305+8
12 Sept 2026, 04:419,297+6
8 Sept 2026, 07:009,291+4
2 Sept 2026, 21:189,287-7
30 Aug 2026, 21:379,294+1
27 Aug 2026, 16:049,293+4
24 Aug 2026, 18:479,289+4
21 Aug 2026, 09:389,285+14
18 Aug 2026, 11:179,271-3
15 Aug 2026, 17:559,274first reading

Engagement

319 posts held, back to 4 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 63 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
2.57%
avg views ÷ 9,331 subscribers
Avg views / post
239
127 posts measured
Reaction rate
0.394%
reactions ÷ views · ER floor
Posts in window
127
of 319 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 11 of 127 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 17 November 2026
Posts held319 (4 August 2026 – 17 November 2026)
Views total30,410
Reactions total11
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Nov 2026, 01:13 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
≈5,650
Videos
≈1,120
Links
≈3,610

Lifetime counters from Telegram’s own channel header, read 18 November 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
54m 21s
Average length
45s

Measured directly from 73 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

100 reactions across 38 posts, in 20 distinct kinds. The most used accounts for 18.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1818.0%
😱1717.0%
❤1414.0%
🤬1414.0%
🔥66.00%
👎55.00%
🏆33.00%
😡33.00%
😢33.00%
🤔33.00%
🤯33.00%
💯22.00%
🙏22.00%
👌11.00%
👏11.00%
💩11.00%
🙈11.00%
🙉11.00%
🤮11.00%
🫡11.00%

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

Measured over the 319 most recent posts we hold, published 4 August 2026 to 17 November 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

Telegram’s own ‘edited’ marker: 0 of 127 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

17 Nov 2026, 17:54 UTC116 viewsread 18 November 2026
Photo

🚘В Новой Москве построят пятиэтажный комплекс с паркингом на 720 машин Разрешение на строительство уже выдал Мосгосстройнадзор. Новое здание появится в районе Коммунарка — в составе ЖК «1-й Ясеневский». Что внутри: 🔹 5 этажей, общая площадь — 25 тысяч «квадратов». 🔹 на первых этажах откроются офисы и коммерческие помещения, а также обустроят открытую автостоянку. Подпишись на 👉 @Новая_Москва_ТиНАО ㅤ

17 Nov 2026, 17:54 UTC117 viewsread 18 November 2026
Video

🔪В Троицке мужчина с ножом набросился на девушку Окровавленную 29-летнюю уроженку Воронежской области обнаружили на Волгоградском проспекте. Предварительно установлено, что нападавший и жертва были знакомы. Девушку экстренно увезли в больницу. А ее обидчика задержали, им оказался ранее судимый 26-летний приезжий из другого региона страны. Подпишись на 👉 @Новая_Москва_ТиНАО ㅤ

17 Nov 2026, 17:54 UTC268 viewsread 18 November 2026
Video

⭕️ «Катамаран» для школьников: как в Москве строят школу для будущих водных инженеров ⭕️На берегу Ивановского пруда в Коммунарке строят образовательный комплекс «Корабелка». Здесь школьники смогут проектировать модели судов, собирать их и испытывать. ⭕️В лабораториях оборудуют мини-бассейны, где будут изучать движение моделей по воде и под водой. Испытания продолжат на пруду: рядом с комплексом запланированы набере…

17 Nov 2026, 17:32 UTC100 viewsread 18 November 2026

Канал НОВАЯ МОСКВА в мессенджере 📲МАХ Подпишись 👉 @НОВАЯ_МОСКВА в 📲МАХ ㅤ

17 Nov 2026, 10:03 UTC138 viewsread 18 November 2026

Канал НОВАЯ МОСКВА в мессенджере 📲МАХ Подпишись 👉 @НОВАЯ_МОСКВА в 📲МАХ ㅤ

17 Nov 2026, 07:25 UTC245 viewsread 18 November 2026
Photo

Круглогодичная площадка на Конном пруду готовится к зимнему сезону, похоже, уже скоро здесь будет лед. Подпишись на 👉 @Новая_Москва_ТиНАО ㅤ

17 Nov 2026, 07:23 UTC161 viewsread 18 November 2026
Video

🆘 Шок! Девочка сидит на подоконнике высокого этажа многоквартирного дома, свесив ноги. Не повторять, опасно для жизни! Соседка весь день пыталась связаться с ребёнком и узнать телефон родителей. В итоге — полный игнор… 📍Проспект Куприна, 40к1 Подпишись на 👉 @Новая_Москва_ТиНАО ㅤ

17 Nov 2026, 07:21 UTC150 viewsread 18 November 2026
Photo

Бармашев - И вчера по просьбам читателей еще ушло гулять обращение по Бачуринской, где не потрудились сделать хотя бы временные тротуары из доски от дорожки, которая соединяет пос. Коммунарка с "Новой Звездой" к переходу. А там поток детей идет в обоих направлениях в школу. Подпишись на 👉 @Новая_Москва_ТиНАО ㅤ

16 Nov 2026, 17:52 UTC226 viewsread 18 November 2026
Photo

🚧Очистные сооружения «Рассудово» реконструировали в ТиНАО Заммэра подчеркнул, что в результате производительность очистных увеличилась со 120 до 500 кубометров в сутки. — Акцент сделали на внедрении современных технологий. Например, биологическая стадия очистки включает глубокое удаление биогенных веществ. При проведении работ предпочтение отдавалось оборудованию и материалам отечественного производства, — рассказа…

16 Nov 2026, 17:41 UTC297 viewsread 18 November 2026
Photo

🚋 Сапсан из Петербурга доставили в Щербинку для испытаний Электричку ЭВС1-08 временно переделали в ЭВС2 и будут проверять на переменном токе. Сейчас 16 составов ЭВС1 ходят только на постоянном токе. После запуска ВСМ к 2028 году на них планируют поставить импортозамещённое оборудование переменного тока и пустить по новым маршрутам. Подпишись на 👉 @Новая_Москва_ТиНАО ㅤ

16 Nov 2026, 17:41 UTC175 viewsread 18 November 2026
Photo

🐕Собака укусила 10-летнего мальчика в Новой Москве Инцидент случился 14 ноября в городе Московский — рядом с магазином «Пятерочка» напротив бассейна. Животное было на поводке, его вела женщина. Собака некрупная, черного окраса с белым животом. В результате нападения ребенок получил укус и царапину. Сейчас семья разыскивает владелицу собаки, чтобы выяснить, какие прививки были сделаны животному. Мальчику уже начал…

16 Nov 2026, 17:40 UTC641 viewsread 17 November 2026
Photo

Бармашев - Читатель канала обратил внимание, что сейчас полностью отсутствует возможность безопасно преодолеть перекресток Монаховой-Куприна: с четной стороны вместо тротуара траншея, по нечетной стороне надо идти по проезжей части. По этому поводу ушло обращение в Департамент строительства транспортной и инженерной инфраструктуры. Подпишись на 👉 @Новая_Москва_ТиНАО ㅤ

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

Posts recorded as deleted after publishing

We recorded 1 post on @novaya_moskva_tinao as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
24 August 2026
Most recent seen missing
24 August 2026
Median time before seen missing
24 hours
Seen missing in the last 30 days
0

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 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.

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

“Новая Москва” (@novaya_moskva_tinao), 9,331 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/novaya_moskva_tinao.

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.