Telegram RegisterThe public register of Telegram
Telegram profile photo for Московский Портал 24

Channel

Московский Портал 24

@moscowportal

On this record: Topic · Observations · Growth · Engagement · What this channel posts · View velocity · Posts · Citations · Cite this entry

849,214subscribers

-197,344 since we began measuring on 10 August 2026

Risers and fallers across the register · movement among entries of 316,228–1,000,000.

Register entry

Telegram ID-1002177296687
TypeChannel
Username@moscowportal
Description‼️КАНАЛ ПРОДАЁТСЯ‼️Писать @vr777 ⏱️Московский Портал 24 🇷🇺Все новости Москвы в одном канале Реклама и сотрудничество писать сюда @vr777 🤖Прислать новость Bot - @Moscowportalbot #москва #новости #срочно #Россия
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live16 November 2026
Measurements held62
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/moscowportal

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 89% 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 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
@moscowmap/7976511 Nov 2026, 06:21 UTC@moscowportal/6096 · this entry11 Nov 2026, 06:21 UTC0.90under a minute
@moscowmap/7884722 Sept 2026, 16:03 UTC@moscowportal/5839 · this entry22 Sept 2026, 16:03 UTC0.87under a minute
@moscowmap/785104 Sept 2026, 05:33 UTC@moscowportal/5747 · this entry4 Sept 2026, 05:33 UTC0.86under a minute
@moscowmap/791367 Oct 2026, 06:28 UTC@moscowportal/5922 · this entry7 Oct 2026, 06:28 UTC0.86under a minute
@moscowmap/7949927 Oct 2026, 04:50 UTC@moscowportal/6017 · this entry27 Oct 2026, 04:50 UTC0.86under a minute
@moscowmap/784843 Sept 2026, 05:03 UTC@moscowportal/5742 · this entry3 Sept 2026, 05:03 UTC0.85under a minute
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
@moscowmap7 (7/7 hand-verifiable sample passed)0.86under a minute@moscowmap (7–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. 7 of the 7 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 435 comparable posts for this entry, running 8 August 2026 to 16 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 17 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

849,2141,046,558947,88610 August 202616 November 2026
62 measurements spanning 97 days, net -197,344. 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 819,612–1,076,160 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 62
Measured (UTC)SubscribersChange
16 Nov 2026, 01:39849,214-6,234
12 Nov 2026, 17:58855,448-3,535
10 Nov 2026, 14:46858,983-1,969
9 Nov 2026, 01:28860,952-2,944
7 Nov 2026, 18:06863,896-1,539
6 Nov 2026, 20:09865,435-2,302
5 Nov 2026, 18:40867,737-1,548
4 Nov 2026, 18:17869,285-1,811
3 Nov 2026, 16:17871,096-2,155
2 Nov 2026, 18:40873,251-1,432
1 Nov 2026, 15:24874,683-2,176
31 Oct 2026, 16:15876,859-1,928
30 Oct 2026, 15:08878,787-2,583
29 Oct 2026, 12:36881,370-2,208
28 Oct 2026, 08:29883,578-2,173
27 Oct 2026, 06:01885,751-2,282
26 Oct 2026, 02:36888,033-973
25 Oct 2026, 04:48889,006-1,067
24 Oct 2026, 05:41890,073-1,957
23 Oct 2026, 08:48892,030first reading

Engagement

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

ERR · 30 days
2.54%
avg views ÷ 849,214 subscribers
Avg views / post
21,500
148 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
148
of 467 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 17 November 2026
Posts held467 (8 August 2026 – 17 November 2026)
Views total3,186,100
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 13: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.

What this channel posts

Photos
≈2,810
Videos
≈1,320
Links
≈1,500

Lifetime counters from Telegram’s own channel header, read 17 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
38m 57s
Average length
28s

Measured directly from 84 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.

View velocity

How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.

Computed from 7 of this channel’s own posts over the last 30 days: across 2 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 24 minutes of being posted.

7 most recently posted, with a view-velocity reading
PostReadingsLatest readingCurve24h reachHalf of last-observed views by
/566212 Aug 2026, 07:04 UTC1711 minutes – 11 hours old17,200 views ~no reaction reading60 minutes: 14,812 interp. → 3.0 hours: 17,200 → 6.0 hours: 17,200views have flattened outnot yet at 24h35 minutes
/566112 Aug 2026, 06:17 UTC1828 minutes – 12 hours old22,100 views ~no reaction reading60 minutes: 22,100 → 3.0 hours: 22,100 → 6.0 hours: 22,100 → 12 hours: 22,100views have flattened outnot yet at 24h28 minutesupper bound — already past half at first reading
/566012 Aug 2026, 05:48 UTC1922 minutes – 12 hours old23,200 views ~no reaction reading60 minutes: 23,200 interp. → 3.0 hours: 23,200 → 6.0 hours: 23,200 → 12 hours: 23,200views have flattened outnot yet at 24h22 minutesupper bound — already past half at first reading
/565912 Aug 2026, 05:33 UTC207 minutes – 13 hours old23,000 views ~no reaction reading60 minutes: 23,000 interp. → 3.0 hours: 23,000 interp. → 6.0 hours: 23,000 → 12 hours: 23,000views have flattened outnot yet at 24h12 minutes
/565812 Aug 2026, 05:18 UTC2112 minutes – 13 hours old23,500 views ~no reaction reading60 minutes: 23,500 interp. → 3.0 hours: 23,500 → 6.0 hours: 23,500 → 12 hours: 23,500views have flattened outnot yet at 24h12 minutesupper bound — already past half at first reading
/565712 Aug 2026, 05:06 UTC2124 minutes – 13 hours old23,300 views ~no reaction reading60 minutes: 23,300 interp. → 3.0 hours: 23,300 interp. → 6.0 hours: 23,300 → 12 hours: 23,300views have flattened outnot yet at 24h24 minutesupper bound — already past half at first reading
/565612 Aug 2026, 04:52 UTC2138 minutes – 13 hours old23,700 views ~no reaction reading60 minutes: 23,700 interp. → 3.0 hours: 23,700 → 6.0 hours: 23,700 → 12 hours: 23,700views have flattened outnot yet at 24h38 minutesupper bound — already past half at first reading

Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed views is the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 148 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, 08:18 UTC≈16,600 viewsread 17 November 2026

👨🏻‍⚕️ Максимальные выплаты по больничному в России вырастут с 6827 ₽ до 7860 ₽ в месяц с 2027 года Итоговая сумма зависит от зарплаты и стажа: при стаже от 8 лет выплачивают 100% среднего заработка, от 5 до 8 лет — 80%, а при меньшем стаже — 60%. #новости #москва #россия #важное #срочное #события #мероприятия

17 Nov 2026, 07:04 UTC≈22,300 viewsread 17 November 2026
Photo

🍔 Мини-роверов завезли во «Вкусно — и точку» Малышей можно забрать в Кидз Комбо вместе с бургером и напитком на выбор. В коллекции также есть четыре помогучика, которых посадили в блайнд-боксы. #новости #москва #россия #важное #срочное #события #мероприятия

17 Nov 2026, 04:47 UTC≈28,400 viewsread 17 November 2026
Photo

🥗 Cелёдка под шубой обойдётся в 2 раза дешевле оливье: 317₽ против 609₽ Рассчитывали по рецептам: сельдь слабосолёная 350 г, картофель 400 г, свёкла 350 г, морковь 200 г, яйца 2 шт, лук 100 г, майонез 300 г; оливье: картофель 500 г, морковь 200 г, яйца 5 шт, варёная колбаса 300 г, лук 100 г, горошек 400 г, огурцы 400 г, майонез 200 г, укроп 50 г. Спрос на ингредиенты для этих салатов неизменно растёт в преддверии …

17 Nov 2026, 03:11 UTC≈28,300 viewsread 17 November 2026

⚡️ Атака БПЛА на Москву продолжается: сбито 113 беспилотников, — Собянин Специалисты экстренных служб работают на месте падения обломков. #новости #москва #россия #важное #срочное #события #мероприятия

16 Nov 2026, 21:04 UTC≈28,600 viewsread 17 November 2026

🤫 17 ноября наступит «цифровой апокалипсис», утверждают сторонники теории заговора Якобы по всему миру хакеры обнулят банковские счета и на три месяца отключат интернет. Люди останутся без связи, света и отопления. Некоторые уже подготовились к «катастрофе» — запаслись наличными, едой, водой и генераторами. #новости #москва #россия #важное #срочное #события #мероприятия

16 Nov 2026, 09:20 UTC≈19,200 viewsread 17 November 2026

💁‍♂️Работодатели обязаны индексировать зарплату, — эксперты Отсутствие индексации зарплаты — это нарушение трудового законодательства. Работодатель обязан повышать реальное содержание выплат с учётом роста потребительских цен. Цены растут, а зарплата нет #новости #москва #россия #важное #срочное #события #мероприятия

16 Nov 2026, 08:50 UTC≈21,700 viewsread 17 November 2026
Video

🇰🇵 Гастротуры в Северную Корею запустили в России Туристы смогут посетить рестораны Пхеньяна, которые недоступны в обычной поездке, и попробовать там разные блюда, включая фуа-гра и кимчи. Раз в месяц группы до 10 человек будут отправляться на 4 дня в КНДР. #новости #москва #россия #важное #срочное #события #мероприятия

16 Nov 2026, 08:38 UTC≈22,800 viewsread 17 November 2026
Video

🚽 На походы в туалет тоже нужно накопить #новости #москва #россия #важное #срочное #события #мероприятия

16 Nov 2026, 08:12 UTC≈24,600 viewsread 17 November 2026
Photo

🇺🇬 Уганда готова вместе с Россией исследовать Луну и Венеру Сейчас ведутся переговоры о совместной космической программе. #новости #москва #россия #важное #срочное #события #мероприятия

16 Nov 2026, 06:33 UTC≈28,500 viewsread 17 November 2026

👨‍⚖️ В России собираются повысить штрафы сразу по 29 статьям Законопроект предполагает ужесточение наказания за продажу алкоголя несовершеннолетним, распитие спиртного и употребление наркотических средств в общественных местах, за курение там, где оно запрещено, мелкое хулиганство, производство и массовое распространение экстремистских материалов, а также за дискредитацию Вооруженных сил России. #новости #москва #ро…

15 Nov 2026, 09:57 UTC≈23,800 viewsread 17 November 2026

🐀Крысиное нашествие ожидает Россию в ближайшие 2 года Размножению крыс способствуют тёплая погода, пищевые отходы и укрытия в подвалах и канализации. Жители мегаполисов уже замечают чаще крыс в своих районах. Грызуны могут переносить инфекции, в том числе лептоспироз и сальмонеллёз. Возбудители попадают к людям через загрязнённые воду, еду и поверхности. #новости #москва #россия #важное #срочное #события #мероприят…

15 Nov 2026, 09:31 UTC≈25,500 viewsread 17 November 2026
Photo

🤔 Если уж метро не определилось с нормами русского языка, то как нам решить? #новости #москва #россия #важное #срочное #события #мероприятия

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

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.

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.

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

“Московский Портал 24” (@moscowportal), 849,214 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/moscowportal.

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.