Telegram RegisterThe public register of Telegram
Telegram profile photo for ОК! Москва

Channel

ОК! Москва

@okey_moscow

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

12,829subscribers

-172 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001839528731
TypeChannel
Username@okey_moscow
Description📌Все самое важное и интересное о Москве. Транслируем жизнь твоего города 24/7 По рекламе: @alex_media1 Купить рекламу через биржу: https://telega.in/c/+thiVOXLi9TtmNmQy Зарегистрирован в РКН: https://clck.ru/3Eqoct
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live15 November 2026
Measurements held60
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/okey_moscow

Topic

National news — 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 86% 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 3 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
@moscowach/4228512 Aug 2026, 13:00 UTC@okey_moscow/23479 · this entry12 Aug 2026, 13:31 UTC1.0031 minutes
@moscowach/4240316 Aug 2026, 16:03 UTC@okey_moscow/23545 · this entry16 Aug 2026, 16:51 UTC1.0047 minutes
@moscowach/4266626 Aug 2026, 07:47 UTC@okey_moscow/23715 · this entry26 Aug 2026, 11:51 UTC1.004.1 hours
@moscowach/4267927 Aug 2026, 07:45 UTC@okey_moscow/23729 · this entry27 Aug 2026, 07:55 UTC1.0011 minutes
@moscowach/428161 Sept 2026, 09:20 UTC@okey_moscow/23801 · this entry1 Sept 2026, 10:25 UTC1.0065 minutes
@moscowach/442715 Nov 2026, 11:04 UTC@okey_moscow/24881 · this entry5 Nov 2026, 11:55 UTC1.0050 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
@moscowach25 (8/8 hand-verifiable sample passed)1.0049 minutes@moscowach (25–0)
@seemoscow6 (6/6 hand-verifiable sample passed)1.0061 minutes@seemoscow (5–1)
@mosjournal6 (6/6 hand-verifiable sample passed)0.9164 minutes@mosjournal (6–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. 36 of the 36 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 313 comparable posts for this entry, running 7 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

12,82913,03212,930.57 August 2026 — 13,001 subscribers7 August 2026 — 13,002 subscribers8 August 2026 — 13,004 subscribers9 August 2026 — 12,997 subscribers10 August 2026 — 12,992 subscribers11 August 2026 — 12,987 subscribers12 August 2026 — 12,984 subscribers13 August 2026 — 12,983 subscribers14 August 2026 — 12,986 subscribers16 August 2026 — 12,984 subscribers17 August 2026 — 12,990 subscribers18 August 2026 — 13,006 subscribers20 August 2026 — 13,002 subscribers21 August 2026 — 13,006 subscribers22 August 2026 — 13,012 subscribers24 August 2026 — 13,013 subscribers25 August 2026 — 13,014 subscribers26 August 2026 — 13,012 subscribers27 August 2026 — 13,015 subscribers28 August 2026 — 13,016 subscribers29 August 2026 — 13,032 subscribers30 August 2026 — 13,030 subscribers31 August 2026 — 13,026 subscribers1 September 2026 — 13,020 subscribers2 September 2026 — 13,023 subscribers3 September 2026 — 13,031 subscribers6 September 2026 — 13,030 subscribers9 September 2026 — 13,028 subscribers11 September 2026 — 13,029 subscribers13 September 2026 — 13,020 subscribers15 September 2026 — 13,004 subscribers17 September 2026 — 13,007 subscribers26 September 2026 — 12,994 subscribers4 October 2026 — 12,963 subscribers9 October 2026 — 12,958 subscribers13 October 2026 — 12,949 subscribers14 October 2026 — 12,947 subscribers15 October 2026 — 12,946 subscribers17 October 2026 — 12,942 subscribers18 October 2026 — 12,937 subscribers19 October 2026 — 12,935 subscribers22 October 2026 — 12,929 subscribers23 October 2026 — 12,926 subscribers24 October 2026 — 12,927 subscribers25 October 2026 — 12,916 subscribers26 October 2026 — 12,912 subscribers27 October 2026 — 12,911 subscribers28 October 2026 — 12,904 subscribers29 October 2026 — 12,896 subscribers30 October 2026 — 12,893 subscribers1 November 2026 — 12,890 subscribers2 November 2026 — 12,887 subscribers3 November 2026 — 12,880 subscribers5 November 2026 — 12,873 subscribers6 November 2026 — 12,871 subscribers7 November 2026 — 12,863 subscribers8 November 2026 — 12,856 subscribers10 November 2026 — 12,848 subscribers12 November 2026 — 12,844 subscribers15 November 2026 — 12,829 subscribers7 August 202615 November 2026
60 measurements spanning 100 days, net -172. 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 12,799–13,062 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 60
Measured (UTC)SubscribersChange
15 Nov 2026, 14:5512,829-15
12 Nov 2026, 07:0912,844-4
10 Nov 2026, 06:0512,848-8
8 Nov 2026, 16:3812,856-7
7 Nov 2026, 09:4012,863-8
6 Nov 2026, 06:4012,871-2
5 Nov 2026, 08:2112,873-7
3 Nov 2026, 06:3512,880-7
2 Nov 2026, 09:0712,887-3
1 Nov 2026, 12:4012,890-3
30 Oct 2026, 09:4112,893-3
29 Oct 2026, 11:1612,896-8
28 Oct 2026, 10:2012,904-7
27 Oct 2026, 07:3912,911-1
26 Oct 2026, 06:2912,912-4
25 Oct 2026, 09:3112,916-11
24 Oct 2026, 06:0612,927+1
23 Oct 2026, 04:5712,926-3
22 Oct 2026, 06:2912,929-6
19 Oct 2026, 21:1012,935first reading

Engagement

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

ERR · 30 days
5.69%
avg views ÷ 12,829 subscribers
Avg views / post
730
181 posts measured
Reaction rate
0.475%
reactions ÷ views · ER floor
Posts in window
181
of 515 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 95 of 181 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 held515 (6 August 2026 – 17 November 2026)
Views total132,062
Reactions total341
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 11:34 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
≈8,960
Videos
≈6,700
Links
≈13,900

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 11s
Average length
21s

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

967 reactions across 241 posts, in 25 distinct kinds. The most used accounts for 30.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤29730.7%
🔥12312.7%
👍11712.1%
👎737.55%
🤬697.14%
😱646.62%
🤯313.21%
🤡293.00%
💩252.59%
😁242.48%
😢232.38%
👏222.28%
🤣171.76%
🥰121.24%
🕊80.827%
💔60.62%
🤔60.62%
👀40.414%
🤮40.414%
💊30.31%
5 further kinds101.03%

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

Measured over the 515 most recent posts we hold, published 6 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.

Advertising

Ad load
0.583%
3 of 515 posts carry an ad marker
Regulatory tokens
3
posts carrying an erid · 3 distinct tokens
Median views · ads
750
over 3 measured posts
Median views · rest
749
over 512 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. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2VtzqweEtMR126 August 202626 August 2026
2W5zFJ1Dm6r115 November 202615 November 2026
2W5zFK1KTnR111 August 202611 August 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 515 most recent posts we hold, published 6 August 2026 to 17 November 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

Telegram’s own ‘edited’ marker: 0 of 181 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, 10:28 UTC198 viewsread 17 November 2026
Photo

😳Гигантская выдра из Московского зоопарка в шоке от того, что до Нового года осталось всего 44 дня. Распространите.

17 Nov 2026, 09:08 UTC346 views1 reactionsread 17 November 2026
Video

В московское метро некоторые спускаются на работу доехать, а некоторые — подраться Первый конфликт случился в поезде между станциями «Петровско-Разумовская» и «Владыкино». 17-летний подросток избил мужчину, сломав ему нос. Второй инцидент произошел на станции «Беговая»: после словесной перепалки 22-летний парень набросился на пьяного пассажира. Обоих участников драк задержали, но позже отпустили под подписку о невые…

🤬1

17 Nov 2026, 08:21 UTC468 views1 reactionsread 17 November 2026
Video

❄️ Сильный снегопад начнется завтра утром в Москве, — синоптики. Высота снежного покрова достигнет 3 см. Подпишись на ОК! Москву | MAX

🤣1

17 Nov 2026, 07:32 UTC511 views3 reactionsread 17 November 2026
Video

🚇 Сегодня на Билиотеке им. Ленина было особенно многолюдно.

😱2👍1

17 Nov 2026, 06:02 UTC562 views1 reactionsread 17 November 2026

❗️Около 800 БПЛА летели в сторону Московского региона с 17:00 16 ноября по 07:00 17 ноября, сообщил Сергей Собянин. Большую часть уничтожили на дальних рубежах. 321 беспилотник — на подлёте к Москве. Подпишись на ОК! Москву | MAX

👍1

16 Nov 2026, 17:53 UTC715 views4 reactionsread 17 November 2026
Photo

🐈‍⬛Манул Тимофей из Московского зоопарка спрятался от рабочей недели. 100% понимания, 0% осуждения.

❤3👍1

16 Nov 2026, 16:53 UTC758 views9 reactionsread 17 November 2026
Photo

😖 Мужчина получил тяжелые травмы, упав с высоты на асфальт при выходе из машины у Ленинского проспекта. Пострадавший сломал череп, ключицу и шесть ребер, также у него диагностировали кровоизлияние. Жители района просят установить на опасном участке ограждение или перила, чтобы предотвратить подобные случаи.

🤯7😁1😢1

16 Nov 2026, 13:32 UTC757 views3 reactionsread 17 November 2026
Video

🤖 Кажется, курьерам в Москве пора начинать переживать за свои рабочие места.

❤3

16 Nov 2026, 12:36 UTC809 viewsread 17 November 2026

🥶 Заморозки до -4 ожидаются сегодня ночью в Москве — Гидрометцентр РФ. Утепляемся. Подпишись на ОК! Москву | MAX

Showing the 12 most recent of 515 posts we hold for @okey_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 recorded as deleted after publishing

We recorded 1 post on @okey_moscow 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
15 November 2026
Most recent seen missing
15 November 2026
Median time before seen missing
31 hours
Seen missing in the last 30 days
1

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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.

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.

Appears in Telegram’s recommendations for other channels

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.

Москва Лайв
@seemoscow · 32,493
Telegram ranks this channel #5 of 82 here — alongside 81 others — read 4 September 2026
Котельники 24
@kotelniki_24 · 21,662
Telegram ranks this channel #14 of 51 here — alongside 50 others — read 25 September 2026
Москва №1 • Новости
@moscow_number1 · 36,478
Telegram ranks this channel #22 of 84 here — alongside 83 others — read 31 August 2026
Глаз Москвы • Новости
@glaz_moscow · 93,099
Telegram ranks this channel #26 of 91 here — alongside 90 others — read 16 August 2026
Я❤️Москву
@ilove_moscow · 105,892
Telegram ranks this channel #52 of 88 here — alongside 87 others — read 14 August 2026

This channel appears in 5 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“ОК! Москва” (@okey_moscow), 12,829 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/okey_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.