Telegram RegisterThe public register of Telegram
Telegram profile photo for Строгино 24/7 • СЗАО

Channel

Строгино 24/7 • СЗАО

@strogino_news24

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Citations · Cite this entry

8,229subscribers

-156 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002423318336
TypeChannel
Username@strogino_news24
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live15 September 2026
Measurements held15
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/strogino_news24

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

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@strogino_mow/51255 Aug 2026, 14:02 UTC@strogino_news24/7109 · this entry5 Aug 2026, 14:02 UTC1.00under a minute
@strogino_mow/51275 Aug 2026, 16:07 UTC@strogino_news24/7111 · this entry5 Aug 2026, 16:07 UTC1.00under a minute
@strogino_mow/51306 Aug 2026, 03:04 UTC@strogino_news24/7114 · this entry6 Aug 2026, 03:04 UTC1.00under a minute
@strogino_mow/51326 Aug 2026, 08:06 UTC@strogino_news24/7116 · this entry6 Aug 2026, 08:06 UTC1.00under a minute
@strogino_mow/51366 Aug 2026, 16:07 UTC@strogino_news24/7120 · this entry6 Aug 2026, 16:07 UTC1.00under a minute
@strogino_mow/51407 Aug 2026, 08:05 UTC@strogino_news24/7124 · this entry7 Aug 2026, 08:05 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@strogino_mow10 (8/8 hand-verifiable sample passed)1.00under a minute@strogino_mow (100)

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. 8 of the 10 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 25 comparable posts for this entry, running 4 August 2026 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.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 2, the earliest publisher we hold is @strogino_mow. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

8,2298,3858,3076 August 2026 — 8,385 subscribers6 August 2026 — 8,385 subscribers7 August 2026 — 8,379 subscribers10 August 2026 — 8,382 subscribers13 August 2026 — 8,374 subscribers16 August 2026 — 8,369 subscribers19 August 2026 — 8,348 subscribers22 August 2026 — 8,338 subscribers25 August 2026 — 8,323 subscribers28 August 2026 — 8,306 subscribers31 August 2026 — 8,293 subscribers3 September 2026 — 8,278 subscribers8 September 2026 — 8,263 subscribers12 September 2026 — 8,249 subscribers15 September 2026 — 8,229 subscribers6 August 202615 September 2026
15 measurements spanning 40 days, net -156. 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 8,206–8,408 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 19:218,229-20
12 Sept 2026, 12:208,249-14
8 Sept 2026, 19:028,263-15
3 Sept 2026, 15:418,278-15
31 Aug 2026, 15:448,293-13
28 Aug 2026, 22:468,306-17
25 Aug 2026, 13:348,323-15
22 Aug 2026, 19:468,338-10
19 Aug 2026, 20:478,348-21
16 Aug 2026, 21:548,369-5
13 Aug 2026, 08:388,374-8
10 Aug 2026, 16:358,382+3
7 Aug 2026, 07:578,379-6
6 Aug 2026, 09:018,385no change
6 Aug 2026, 08:528,385first reading

Engagement

186 posts held, back to 4 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 23 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
8.96%
avg views ÷ 8,229 subscribers
Avg views / post
738
39 posts measured
Reaction rate
0.736%
reactions ÷ views · ER floor
Posts in window
39
of 186 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 33 of 39 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 28 August 2026
Posts held186 (4 August 202628 August 2026)
Views total28,765
Reactions total191
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 17:57 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

Video runtime
4m 28s
Average length
30s

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

1,078 reactions across 137 posts, in 8 distinct kinds. The most used accounts for 25.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍27625.6%
23221.5%
👎18317.0%
🤬18216.9%
😁898.26%
😱837.70%
💔282.60%
😍50.464%

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 149 of the 186 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 1,124 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 186 most recent posts we hold, published 4 August 2026 to 28 August 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
3.23%
6 of 186 posts carry an ad marker
Regulatory tokens
6
posts carrying an erid · 6 distinct tokens
Median views · ads
732
over 6 measured posts
Median views · rest
933
over 180 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.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2VtzqvbJz5H125 August 202625 August 2026
2VtzqwNxmTh118 August 202618 August 2026
2Vtzqwqaqw1117 August 202617 August 2026
2Vtzqx23kh9111 August 202611 August 2026
2VtzqxJR4wD126 August 202626 August 2026
2Vtzqxdjah1124 August 202624 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 186 most recent posts we hold, published 4 August 2026 to 28 August 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

28 Aug 2026, 16:08 UTC339 views5 reactionsread 28 August 2026
Photo

⚒️ На станции «Строгино» продолжаются работы перед открытием Перед запуском участка от «Делового центра» до «Бульвара Генерала Карбышева» на станциях и в вагонах обновляют навигацию. Открытие предварительно намечено на 5 сентября.

5

28 Aug 2026, 13:36 UTC527 views2 reactionsread 28 August 2026
Photo

🚘 Козероги и Раки оказались самыми опасными водителями, подсчитали аналитики Они чаще других обращаются по ОСАГО в страховую компанию. Самыми безопасными названы Стрельцы и Скорпионы. Исследование основано на статистике обращений. Астрология, похоже, добралась и до автострахования.‍

😁2

28 Aug 2026, 12:04 UTC573 views9 reactionsread 28 August 2026
Photo

🛠 В сквере напротив Катукова детскую площадку вернут в 2027 году В сквере напротив дома по адресу улица Катукова, 2к1, навели порядок и установили качели. Новая игровая зона появится только через год.

👎3🤬3💔2👍1

28 Aug 2026, 10:03 UTC696 views10 reactionsread 28 August 2026

💸 Платить за долгий брак начали в России Например, в некоторых регионах за 50, 60 и 70 лет совместной жизни можно получить 50, 100 и 150 тысяч рублей соответственно. В Москве выплаты составляют до 44,4 тысяч рублей.

😁8👍2

28 Aug 2026, 08:01 UTC729 views4 reactionsread 28 August 2026
Photo

📹 29 августа в КЦ «Строгино» пройдёт «Строгинский арт-вояж» В программе: концерты, Антикварный цирк, парад студий, танцы. Внутри — бесплатные мастер-классы по фитнесу, хореографии и вокалу. Вход на уличную программу свободный, на мастер-классы — по регистрации.

3👎1

28 Aug 2026, 05:48 UTC777 views7 reactionsread 28 August 2026

🤑 Военкоматы смогут получать больше данных о военнообязанных В перечень сведений, которые смогут передавать военкоматам, вошли данные о банковских счетах, кредитах, налоговых декларациях, месте работы и медицинских данных. Также речь идёт о сведениях о браке, загранпаспортах, ДТП, административных и уголовных делах. Отдельно предусмотрен сбор информации о близких родственниках.

👎5👍2

28 Aug 2026, 05:48 UTC733 views4 reactionsread 28 August 2026

🤑 Военкоматы смогут получать больше данных о военнообязанных В перечень сведений, которые смогут передавать военкоматам, вошли данные о банковских счетах, кредитах, налоговых декларациях, месте работы и медицинских данных. Также речь идёт о сведениях о браке, загранпаспортах, ДТП, административных и уголовных делах. Отдельно предусмотрен сбор информации о близких родственниках.

👍21👎1

28 Aug 2026, 05:05 UTC803 views16 reactionsread 28 August 2026

⚡️ Военкоматы получат доступ ко всем данным военнообязанных и их родственников Речь идёт о финансовой, налоговой и трудовой информации, сведениях о кредитах, долгах, ДТП, документах и правонарушениях. Также в перечень могут попасть медицинские данные, включая сведения о заболеваниях и зависимостях. Информацию смогут получать и о близких родственниках военнообязанных — супруге, детях, родителях, братьях и сёстрах.

🤬13👍2👎1

28 Aug 2026, 03:01 UTC780 views3 reactionsread 28 August 2026
Photo

🎯 День для одной важной цели Желаем выбрать дело, которое давно хотелось завершить, и наконец уделить ему заслуженное внимание. Не обязательно сделать всё сразу — главное, начать. Пусть сегодняшний результат станет началом большого достижения.

👍3

27 Aug 2026, 18:37 UTC900 views6 reactionsread 28 August 2026

❄️ Предстоящая ночь может стать одной из самых холодных за лето в Москве, — Гидрометцентр Температура воздуха опустится до +4 градусов. В Подмосковье также возможен местами кратковременный дождь и туман.

😱51

27 Aug 2026, 16:01 UTC944 views3 reactionsread 28 August 2026
Photo

🛠 Ремонт младшей школы на Кулакова близится к завершению Основные отделочные работы закончены, обновляют газоны и дорожки, появилась спортивная площадка. К новому учебному году всё должно быть готово.

😍21

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

Forward network

Republished by

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

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 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 15 September 2026 — this entry's latest reading, not the date you are reading this.

“Строгино 24/7 • СЗАО” (@strogino_news24), 8,229 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/strogino_news24.

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.