Telegram RegisterThe public register of Telegram

Channel

Москва | События | Новости

@Moscow_ti

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

9,318subscribers

-5 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-1001454804812
TypeChannel
Username@Moscow_ti
CreatedBetween 1 April 2019 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/Moscow_ti

Topic

National news — 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 56% 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 (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@Moscow_ti/1943 · this entry13 Nov 2025, 17:57 UTC@Moscow_nauch/161914 Nov 2025, 14:37 UTC1.0021 hours
@Moscow_ti/1944 · this entry14 Nov 2025, 16:42 UTC@Moscow_nauch/162015 Nov 2025, 20:34 UTC1.0028 hours
@Moscow_ti/1946 · this entry16 Nov 2025, 18:27 UTC@Moscow_nauch/162217 Nov 2025, 16:05 UTC1.0022 hours
@Moscow_ti/1947 · this entry17 Nov 2025, 17:21 UTC@Moscow_nauch/162419 Nov 2025, 16:46 UTC1.0047 hours
@Moscow_ti/1950 · this entry20 Nov 2025, 17:37 UTC@Moscow_nauch/162520 Nov 2025, 20:31 UTC1.002.9 hours
@Moscow_ti/1956 · this entry26 Nov 2025, 18:50 UTC@Moscow_nauch/163227 Nov 2025, 17:48 UTC1.0023 hours
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@Moscow_nauch6 (6/6 hand-verifiable sample passed)1.0022 hoursthis entry (60)

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 0 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 18 comparable posts for this entry, running 11 November 2025 to 29 November 2025. 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 @Moscow_ti — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, 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

9,3189,3239,320.56 August 2026 — 9,323 subscribers6 August 2026 — 9,323 subscribers9 August 2026 — 9,321 subscribers12 August 2026 — 9,318 subscribers6 August 202612 August 2026
4 measurements spanning 6 days, net -5. 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,317–9,324 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 16:539,318-3
9 Aug 2026, 18:119,321-2
6 Aug 2026, 19:319,323no change
6 Aug 2026, 17:179,323first reading

Engagement

20 posts held, back to 11 November 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 14 pagesof 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 20 posts for this entry, the most recent from 30 November 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

30 Nov 2025, 17:24 UTC≈13,000 viewsread 12 August 2026
Photo

Канал временно не обслуживается, по вопросам обращаться @Sanya_rekLama

29 Nov 2025, 18:45 UTC≈12,200 viewsread 12 August 2026
Photo

В Подмосковье появилось село без въезда и выезда. С одной стороны путь перекрыл Росавтодор, а с другой мужчина начал строить дом прямо на дороге. Жители села Тишково-Спасское оказались в ловушке. По данным «Базы», один из двух въездов в село перекрыл Росавтодор, так как признал его опасным и аварийным. А второй заблокировал собственник придорожного участка. Анатолий С. предлагал жителям села скинуться и выкупить ег

28 Nov 2025, 16:57 UTC≈12,100 viewsread 12 August 2026
Photo

Между станциями МЦД-3 прямо во время поездки около головы пассажира разбилось стекло. Никто не пострадал, пассажир отделался испугом

27 Nov 2025, 17:57 UTC≈12,100 viewsread 12 August 2026
Photo

В Москве и области начались проблемы с интернетом, сообщают сотовые операторы. Москвичи жалуются, что у них не работает ни мобильный интернет, ни Wi-Fi.

26 Nov 2025, 18:50 UTC≈12,100 viewsread 12 August 2026
Photo

В Москве арестовали строителя за мат в метро, когда он ехал в травмпункт после падения с 5 метровой высоты. 46-летний уроженец Тывы Маадыр М. работает строителем в компании «А-101». 23 ноября его задержали, так как он матерился в метро на станции «Теплый стан». Позже на судебном заседании он пояснил, что пассажиры первыми начали его оскорблять, посчитав, что он пьяный. Он просто им отвечал, а сам направлялся в трав

25 Nov 2025, 17:11 UTC≈12,600 viewsread 12 August 2026
Photo

В ЖК Горки Парк Ленинского городского округа жители по утрам вынуждены стоять в огромных очередях, чтобы уехать в Москву. На линию пустили дополнительный маршрут, но пассажиры говорят, что этого мало — очереди не уменьшаются.

24 Nov 2025, 17:18 UTC≈12,300 viewsread 12 August 2026
Photo

Проститутки пожаловались на резкое падение спроса. Из-за экономической ситуации жрицы любви вынуждены делать скидки, чтобы хоть как-то выживать.

23 Nov 2025, 18:28 UTC≈13,200 viewsread 12 August 2026
Photo

Снег стремительно тает, но в столичном районе Очаково-Матвеевское местные жители совсем не готовы с этим мириться и вовсю лепят снеговичков.

22 Nov 2025, 17:42 UTC≈12,100 viewsread 12 August 2026
Photo

Семь машин и два мотоцикла уничтожены в результате поджога в Москве. Инцидент произошел в ночь на 22 ноября. Неизвестный поджег помойку во дворе дома на Донецкой улице. Огонь перекинулся на машины. Сгорели семь автомобилей и два мотоцикла. Спасатели ликвидировали огонь. Поджигателя ищут правоохранители. Пострадавших нет.

21 Nov 2025, 17:31 UTC≈12,100 viewsread 12 August 2026
Photo

Гагаринский так хорошо припорошило вторым первым снегом. Между тем в городе ввели желтый уровень погодной опасности из-за тумана вечером и ночью.

20 Nov 2025, 17:37 UTC≈12,100 viewsread 12 August 2026
Photo

Полицейский насмерть сбил женщину и скрылся в Сергиевом Посаде. Женщина переходила дорогу на зеленый сигнал светофора, когда ее сбила машина. Выяснилось, водителем был пьяный 26-летний сотрудник ППС. Его задержали, возбуждено уголовное дело.

19 Nov 2025, 17:39 UTC≈12,100 viewsread 12 August 2026
Photo

Электрическая зубная щётка застряла в заднем проходе 19-летнего москвича. Она вибрировала там до госпитализации Подросток включил щётку на максимально активный режим чистки и засунул в место не по назначению. А ещё и другой стороной. В процессе манипуляций чистящая насадка электрощётки оторвалась и осталась у него в руке. А основная часть прибора — застряла прямо там. Блок вибрировал ещё больше часа. Сначала пацан

Showing the 12 most recent of 20 posts we hold for @Moscow_ti. 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 — 1,135,421 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.

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.

“Москва | События | Новости” (@Moscow_ti), 9,318 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/Moscow_ti.

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.