😶🌫️Густой туман снова накроет Москву и Подмосковье в ближайший час, — РСЧС. В отдельных районах видимость снизится до 200–700 метров. Туман продержится до 10:00 завтрашнего дня. 😄— Подписаться
❤376💔64🤡28🤬9

Channel
@msk_live
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · View velocity · Reactions · Advertising · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Domains linked from posts · Cite this entry
1,808,438subscribers
-17,397 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among the largest entries.
| Telegram ID | -1001747110091 |
|---|---|
| Type | Channel |
| Username | @msk_live |
| Description | Подпишись, чтобы не потерять. Ссылка для друзей: https://t.me/+MudQsy2gMds3MmVi Прислать новость: @msk_live_bot По вопросам сотрудничества: @evo_anna https://knd.gov.ru/license?id=676418d94de6c36845d97712®istryType=bloggersPermission |
| Created | 22 September 2022 — measured — dated from the channel’s first post |
| First recorded | 6 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 35 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/msk_live |
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 8 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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.
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.
Posts published here appear word for word on 12 other registered channels. They sit inside a group of 377 channels that share the same post bodies with each other. 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @toporlive/1425399 May 2025, 10:11 UTC | @msk_live/23018 · this entry9 May 2025, 10:16 UTC | 1.00 | 6 minutes |
| @msk_live/26687 · this entry13 Nov 2025, 20:07 UTC | @toporlive/16544213 Nov 2025, 20:55 UTC | 1.00 | 47 minutes |
| @msk_live/27382 · this entry17 Dec 2025, 07:40 UTC | @toporlive/16922817 Dec 2025, 08:24 UTC | 1.00 | 44 minutes |
| @msk_live/28211 · this entry30 Jan 2026, 11:25 UTC | @toporlive/17449430 Jan 2026, 13:32 UTC | 1.00 | 2.1 hours |
| @msk_live/28856 · this entry10 Mar 2026, 11:35 UTC | @toporlive/17960410 Mar 2026, 12:22 UTC | 1.00 | 47 minutes |
| @msk_live/29482 · this entry16 Apr 2026, 08:05 UTC | @toporlive/18388316 Apr 2026, 09:53 UTC | 1.00 | 1.8 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @toporlive | 495 (8/8 hand-verifiable sample passed) | 0.99 | 38 minutes | this entry (421–74) |
| @moscowmap | 108 (8/8 hand-verifiable sample passed) | 0.92 | 29 minutes | @moscowmap (101–7) |
| @moscowach | 99 (8/8 hand-verifiable sample passed) | 0.92 | 17 minutes | @moscowach (96–3) |
| @mskint | 63 (8/8 hand-verifiable sample passed) | 0.91 | 25 minutes | this entry (44–19) |
| @ecotopor | 48 (8/8 hand-verifiable sample passed) | 0.95 | 40 minutes | @ecotopor (47–1) |
| @mosnews | 41 (8/8 hand-verifiable sample passed) | 0.92 | 66 minutes | @mosnews (38–3) |
| @mosguru | 27 (8/8 hand-verifiable sample passed) | 0.98 | 2.0 hours | @mosguru (15–12) |
| @bbbreaking | 16 (8/8 hand-verifiable sample passed) | 0.89 | 8 minutes | @bbbreaking (16–0) |
| @msk7days | 9 (8/8 hand-verifiable sample passed) | 0.95 | 31 minutes | this entry (8–1) |
| @live_piter | 6 (6/6 hand-verifiable sample passed) | 1.00 | under a minute | @live_piter (6–0) |
| @moscow | 5 (5/5 hand-verifiable sample passed) | 0.92 | 46 minutes | @moscow (4–1) |
| @kontext_channel | 5 (5/5 hand-verifiable sample passed) | 1.00 | 21 hours | @kontext_channel (3–2) |
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. 3 of the 405 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 16,904 comparable posts for this entry, running 22 September 2022 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.
Across the whole group of 377, the earliest publisher we hold is @mash. That is a statement about our reading window, not a claim of authorship.
On 29 of the 372 posts we watched over 30 days, the view counter climbed while the reaction counter stayed where it was — by more than this channel’s own reactions-per-view rate can account for. That rate, measured on this entry, is 0.0073 reactions per view.
| Post | Over | Views | Reactions | Expected |
|---|---|---|---|---|
| /3197328 Aug 2026, 14:00 UTC | 30 minutes | 37,100 → 47,800at least +10,600 | 607 → 613at most +7 | +76.9 |
| /3197328 Aug 2026, 14:00 UTC | 35 minutes | 47,800 → 61,500at least +13,600 | 613 → 625at most +13 | +98.7 |
| /3197328 Aug 2026, 14:00 UTC | 12 hours | 90,800 → 106,000at least +14,200 | 664 → 680at most +17 | +103.1 |
| /3201030 Aug 2026, 16:41 UTC | 30 minutes | 74,300 → 176,000at least +100,700 | 706 → 803at most +98 | +730.9 |
| /3201030 Aug 2026, 16:41 UTC | 30 minutes | 176,000 → 232,000at least +55,000 | 803 → 852at most +50 | +399.2 |
| /3201030 Aug 2026, 16:41 UTC | 35 minutes | 232,000 → 277,000at least +44,000 | 852 → 912at most +61 | +319.4 |
| /3226910 Sept 2026, 15:32 UTC | 31 minutes | 45,300 → 127,000at least +80,700 | 559 → 655at most +97 | +585.7 |
| /3226910 Sept 2026, 15:32 UTC | 33 minutes | 127,000 → 205,000at least +77,000 | 655 → 759at most +105 | +558.9 |
| /3226910 Sept 2026, 15:32 UTC | 30 minutes | 205,000 → 254,000at least +48,000 | 759 → 809at most +51 | +348.4 |
| /3232513 Sept 2026, 11:41 UTC | 33 minutes | 28,900 → 37,400at least +8,400 | 699 → 712at most +14 | +61.0 |
| /3232513 Sept 2026, 11:41 UTC | 31 minutes | 48,100 → 55,700at least +7,500 | 731 → 737at most +7 | +54.4 |
| /3232513 Sept 2026, 11:41 UTC | 34 minutes | 55,700 → 66,300at least +10,500 | 737 → 749at most +13 | +76.2 |
| /3239818 Sept 2026, 08:50 UTC | 34 minutes | 43,600 → 53,700at least +10,000 | 886 → 902at most +17 | +72.6 |
| /3239818 Sept 2026, 08:50 UTC | 35 minutes | 53,700 → 62,200at least +8,400 | 902 → 912at most +11 | +61.0 |
| /3239818 Sept 2026, 08:50 UTC | 5 days | 114,000 → 139,000at least +24,000 | 991 → 1,011at most +30 | +174.2 |
| /3241919 Sept 2026, 10:05 UTC | 55 minutes | 34,500 → 56,700at least +22,100 | 725 → 751at most +27 | +160.4 |
| /3241919 Sept 2026, 10:05 UTC | 12 hours | 98,200 → 120,000at least +20,800 | 809 → 832at most +24 | +151.0 |
| /3241919 Sept 2026, 10:05 UTC | 13 hours | 120,000 → 157,000at least +36,000 | 832 → 849at most +18 | +261.3 |
| /3200830 Aug 2026, 13:05 UTC | 36 minutes | 142,000 → 208,000at least +65,000 | 695 → 807at most +113 | +471.8 |
| /3200830 Aug 2026, 13:05 UTC | 35 minutes | 208,000 → 251,000at least +42,000 | 807 → 865at most +59 | +304.9 |
| /3203531 Aug 2026, 15:00 UTC | 37 minutes | 59,800 → 72,700at least +12,800 | 422 → 430at most +9 | +92.9 |
| /3203531 Aug 2026, 15:00 UTC | 59 minutes | 72,700 → 95,100at least +22,300 | 430 → 442at most +13 | +161.9 |
| /320852 Sept 2026, 15:00 UTC | 35 minutes | 44,400 → 59,100at least +14,600 | 1,585 → 1,594at most +19 | +106.0 |
| /320852 Sept 2026, 15:00 UTC | 33 minutes | 59,100 → 70,200at least +11,000 | 1,594 → 1,601at most +17 | +79.8 |
| /321375 Sept 2026, 09:00 UTC | 31 minutes | 71,300 → 89,700at least +18,300 | 1,092 → 1,097at most +15 | +132.8 |
| /321375 Sept 2026, 09:00 UTC | 55 minutes | 89,700 → 107,000at least +16,300 | 1,097 → 1,105at most +18 | +118.3 |
Expected is the view gain multiplied by this channel’s own prior reactions-per-view rate over the same post — not a corpus average, so a channel whose audience never reacts is compared only against itself. Every interval is credited in the direction that makes the observation harder to record, never easier: t.me renders views and reactions to three significant figures above ~1,000, so a raw delta can be a rendering step. Every delta below is at least 4 x the coarser reading's step, the view gain is discounted by a full step and the reaction gain credited with one. Measured by tgregister velocity.py (our own t.me/s/ readings).
What this does and does not say. It says the two counters moved apart, by more than rounding and more than this channel’s own history predicts. It asserts no cause. Views arriving from outside Telegram, an embedded or forwarded copy of the post, and a burst of readers who simply do not react all produce this shape. This detector has recorded very few observations across the whole register, and its precision has not been measured; treat it as an anomaly worth looking at, not as a finding.
Recorded under the keys clone_copy · clone_mutual · clone_source · view_reaction_decoupling, last confirmed 26 September 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.
This channel’s posts match, word for word or near enough, posts on 376 other registered channels, 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.
326 more channels are in this same group but not listed individually here.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 23:16 | 1,808,438 | -1,465 |
| 15 Sept 2026, 16:15 | 1,809,903 | +1,060 |
| 14 Sept 2026, 02:20 | 1,808,843 | +6,221 |
| 12 Sept 2026, 08:16 | 1,802,622 | -958 |
| 10 Sept 2026, 02:36 | 1,803,580 | -2,487 |
| 6 Sept 2026, 17:20 | 1,806,067 | -1,496 |
| 4 Sept 2026, 08:58 | 1,807,563 | -879 |
| 2 Sept 2026, 22:58 | 1,808,442 | -1,068 |
| 1 Sept 2026, 17:53 | 1,809,510 | -828 |
| 31 Aug 2026, 15:55 | 1,810,338 | -696 |
| 30 Aug 2026, 18:48 | 1,811,034 | -635 |
| 29 Aug 2026, 18:38 | 1,811,669 | -488 |
| 28 Aug 2026, 21:54 | 1,812,157 | -815 |
| 27 Aug 2026, 22:45 | 1,812,972 | -817 |
| 26 Aug 2026, 20:04 | 1,813,789 | -673 |
| 25 Aug 2026, 22:24 | 1,814,462 | -645 |
| 25 Aug 2026, 01:47 | 1,815,107 | -1,388 |
| 23 Aug 2026, 12:34 | 1,816,495 | -1,060 |
| 21 Aug 2026, 20:15 | 1,817,555 | -944 |
| 20 Aug 2026, 14:43 | 1,818,499 | first reading |
23,730 posts held, back to 22 September 2022 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 2,810 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 26 September 2026 |
|---|---|
| Posts held | 23,730 (22 September 2022 – 26 September 2026) |
| Views total | 101,432,600 |
| Reactions total | 910,801 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 27 Sept 2026, 02:35 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.
Lifetime counters from Telegram’s own channel header, read 26 September 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.
Measured directly from 233 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.
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 372 of this channel’s own posts over the last 30 days (11 of the 24-hour readings behind this are interpolated, not measured directly): across 362 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 3.3 hours of being posted; a typical post has already reached 31.5% of its 24-hour view count within the first hour, and 74.2% within the first six; the median 24-hour reach across those posts is 160,000 views — 8.85% of this channel’s own subscriber count (90th percentile 202,400).
| Post | Readings | Latest reading | Curve | 24h reach | Half of last-observed views by |
|---|---|---|---|---|---|
| /3256626 Sept 2026, 19:41 UTC | 134 minutes – 6.9 hours old | 59,600 views ~477 reactions | 60 minutes: 34,931 interp. → 3.0 hours: 52,097 interp. → 6.0 hours: 58,100still climbing at last reading | not yet at 24h | 44 minutesprovisional — final view count still climbing |
| /3256526 Sept 2026, 17:45 UTC | 1725 minutes – 8.8 hours old | 102,000 views ~4,013 reactions | 60 minutes: 54,274 interp. → 3.0 hours: 88,600 → 6.0 hours: 99,000still climbing at last reading | not yet at 24h | 53 minutesprovisional — final view count still climbing |
| /3256426 Sept 2026, 17:21 UTC | 1819 minutes – 9.2 hours old | 104,000 views ~961 reactions | 60 minutes: 53,949 interp. → 3.0 hours: 88,500 → 6.0 hours: 100,460 interp.still climbing at last reading | not yet at 24h | 56 minutesprovisional — final view count still climbing |
| /3255926 Sept 2026, 16:40 UTC | 1925 minutes – 9.9 hours old | 107,000 views ~682 reactions | 60 minutes: 41,400 → 3.0 hours: 87,600 → 6.0 hours: 104,000still climbing at last reading | not yet at 24h | 77 minutesprovisional — final view count still climbing |
| /3255626 Sept 2026, 16:05 UTC | 1959 minutes – 10 hours old | 105,000 views ~1,268 reactions | 60 minutes: 46,100 → 3.0 hours: 84,900 → 6.0 hours: 101,000views have flattened out | not yet at 24h | 78 minutes |
| /3255426 Sept 2026, 13:45 UTC | 2411 minutes – 13 hours old | 126,000 views ~1,983 reactions | 60 minutes: 44,605 interp. → 3.0 hours: 80,279 interp. → 6.0 hours: 114,000 → 12 hours: 125,000still climbing at last reading | not yet at 24h | 2.2 hoursprovisional — final view count still climbing |
| /3255326 Sept 2026, 13:01 UTC | 2525 minutes – 14 hours old | 118,000 views ~466 reactions | 60 minutes: 41,415 interp. → 3.0 hours: 73,400 → 6.0 hours: 105,000 → 12 hours: 118,000views have flattened out | not yet at 24h | 1.8 hours |
| /3255026 Sept 2026, 12:20 UTC | 2611 minutes – 14 hours old | 117,000 views ~528 reactions | 60 minutes: 38,299 interp. → 3.0 hours: 71,564 interp. → 6.0 hours: 98,500 → 12 hours: 116,000views have flattened out | not yet at 24h | 1.9 hours |
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.
1,496,483 reactions across 751 posts, in 17 distinct kinds. The most used accounts for 24.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤡 | 369,628 | 24.7% | |
| ❤ | 332,659 | 22.2% | |
| 😁 | 165,743 | 11.1% | |
| 🤬 | 131,360 | 8.78% | |
| 🤯 | 107,475 | 7.18% | |
| 👎 | 95,216 | 6.36% | |
| 👍 | 91,720 | 6.13% | |
| 😱 | 49,468 | 3.31% | |
| 😢 | 45,334 | 3.03% | |
| 🔥 | 39,545 | 2.64% | |
| 🥰 | 16,626 | 1.11% | |
| 🤔 | 13,802 | 0.922% | |
| 🤨 | 11,701 | 0.782% | |
| 🙏 | 11,222 | 0.75% | |
| 💔 | 9,479 | 0.633% | |
| 👏 | 3,147 | 0.21% | |
| 🎉 | 2,358 | 0.158% |
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 1,000 of the 1,000 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 2,020,530 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 18 July 2026 to 26 September 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.
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. They are printed side by side with the count behind each rather than as a ratio: an ad and an ordinary post are not otherwise matched — for topic, for length, for hour of day — so the gap between them is a description of two groups and not the effect of one being an ad.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| 2Vtzqub2Xkf | 1 | 12 August 2026 | 12 August 2026 |
| 2Vtzqv7CbXR | 1 | 27 August 2026 | 27 August 2026 |
| 2VtzqvK67P8 | 1 | 20 July 2026 | 20 July 2026 |
| 2VtzqvcPSot | 1 | 25 July 2026 | 25 July 2026 |
| 2VtzqvyfVVD | 1 | 20 August 2026 | 20 August 2026 |
| 2VtzqxL46Pm | 1 | 22 August 2026 | 22 August 2026 |
| 2W5zFGod6Qy | 1 | 24 July 2026 | 24 July 2026 |
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 18 July 2026 to 26 September 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
😶🌫️Густой туман снова накроет Москву и Подмосковье в ближайший час, — РСЧС. В отдельных районах видимость снизится до 200–700 метров. Туман продержится до 10:00 завтрашнего дня. 😄— Подписаться
❤376💔64🤡28🤬9
❗️Европейцы готовятся к войне с Россией, — Лавров. 😄— Подписаться
🤡2,920🤬797🤨209👍87
☀️Конец сентября в Москве будет солнечным и сухим, — синоптики. Следующая неделя будет солнечной и сухой, днём +11…+18. Ночи прохладные, особенно во вторник — до +4…+6. 😄— Подписаться
❤757🥰142🔥34👎28
Москва — город высоких скоростей абсолютно во всём В том числе в создании ситуативов от крупных брендов: МегаФон оригинально поддержал бегунов на Московском марафоне и ещё раз напомнил про запуск 5G сетей в стране — новые скорости уже доступны жителям десяти городов.
🤡506👎94❤43🤬39
🌒Огромная Луна взошла над Москвой. 😄— Подписаться
❤953🥰207👍100😢8
❗️Самый высокий жилой небоскрёб Европы возведут в «Москва-Сити». Проект уже согласован. Башню высотой 450 метров построят на территории «Сити-2» на улице Антонова-Овсеенко. В здании разместятся 95 надземных этажей и 1018 квартир. Подготовка участка к строительству уже началась. 😄— Подписаться
🤡1,460👍295🤯196🥰32
✈️Улететь в Турцию из Москвы можно всего за 5 тысяч рублей. Летим? 😄— Подписаться
❤335🤔63🤡42👍26
🏃♂️➡️ Пробежать мимо Кремля, сталинских высоток и собора Василия Блаженного — и финишировать в Лужниках. Такой маршрут ждёт участников СберПрайм Московского Марафона 26 и 27 сентября: в этом году трассы обеих дистанций полностью обновили. Примерно половина тех, кто зарегистрировался на 42,2 км, собирается пробежать марафон впервые. А после финиша участники смогут выгравировать своё время на медали в зоне СберПрайм…
❤305🤡188🔥30😢5
🎃Заплыв на огромных тыквах пройдёт сегодня на Городской ферме ВДНХ. Участники сделают из тыкв лодки, наденут костюмы и проведут парад на воде с 15:00 до 18:00. Для заплыва будут использовать тыквы весом около 400–500 килограммов. 😄— Подписаться
❤458😁138🥰44🤯31
🦷Москвичке сломали челюсть во время удаления зуба мудрости, — СМИ. Во время процедуры раздался щелчок и появилась резкая боль. Снимок показал перелом. Девушке установили восемь штифтов и зафиксировали челюсть проволокой. До начала октября она сможет питаться только жидкой пищей и почти месяц не сможет работать. 😄— Подписаться
🤯1,480😱428❤77🔥25
🥶Вчерашний день стал самым холодным в Москве с начала осени, — синоптики. Температура воздуха поднялась всего до +12,2°С. 😄— Подписаться
😢518👍90❤71😱35
На сцене Яндекс Еды на New Star Weekend в Сочи девушка из зала держала плакат с желанием услышать «Царицу». Музыканты заметили и сыграли её в моменте. Наманифестировала, получается. Загадываем всё что хочется!
🤡736🥰175👍71👎39
Showing the 12 most recent of 23,730 posts we hold for @msk_live. 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.
@msk_live edited 13 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republished by 89 registered channels. The 48 listed are the ones that have forwarded the most posts; the rest are counted here but not each listed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 24 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.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 7 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
This channel appears in 780 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
36 domains this channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“Москва Live” (@msk_live), 1,808,438 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/msk_live.
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.