Channel

Москва сегодня

@moscow

Verified by Telegram2 usernames

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · View velocity · Advertising · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Telegram's recommendations · Domains linked from posts · Cite this entry

2,655,291subscribers

-84,365 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among the largest entries.

Register entry

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 8 August 2026 and assigned it the closest of 31 fixed categories, at 87% 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.

Recorded under the keys clone_copy · clone_source, last confirmed 8 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 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.

Growth

Engagement

19,301 posts held, back to 25 February 2018 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 5,113 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days

4.18%

avg views ÷ 2,655,291 subscribers

Avg views / post

111,000

559 posts measured

Reaction rate

—

this channel exposes no reaction counts

Posts in window

559

of 19,301 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.

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

≈11,700

Videos

≈5,020

Links

≈4,570

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

Video runtime

1h 01m

Average length

22s

Measured directly from 165 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 512 of this channel’s own posts over the last 30 days: across 499 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 3.7 hours of being posted; a typical post has already reached 30.3% of its 24-hour view count within the first hour, and 72.1% within the first six; the median 24-hour reach across those posts is 92,100 views — 3.47% of this channel’s own subscriber count (90th percentile 110,000).

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.

Advertising

Ad load

1.20%

12 of 1,000 posts carry an ad marker

Regulatory tokens

12

posts carrying an erid · 11 distinct tokens

Median views · ads

91,700

over 12 measured posts

Median views · rest

112,000

over 988 measured posts

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.

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 30 July 2026 to 22 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.

Recent posts

Showing the 12 most recent of 19,301 posts we hold for @moscow. 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 edited after publishing

@moscow edited 9 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.

First edit seen

11 August 2026

Most recent edit

19 September 2026

Handles this channel named that no longer answer

Dead references

27

handles named in this channel’s posts, vacant today

Evidenced gone

0

we ourselves saw one of these resolve, at some point

Never seen alive

27

vacant every time we have ever looked

@moscow named 27 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.

Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.

Never seen alive

References a handle that is not a live channel — we have no record it ever was one.

Domains linked from posts

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

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

“Москва сегодня” (@moscow), 2,655,291 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/moscow.

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.