Channel
@sochi03
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Posts · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry
40,272subscribers
+2,599 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001781861657 |
|---|---|
| Type | Channel |
| Username | @sochi03 |
| Description | Привет всем ! Все главные новости города здесь! Присылайте свои истории новости @elenagoldi По вопросам сотрудничества @elenagoldi |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 9 November 2026 |
| Measurements held | 64 |
| Confirmed unchanged | 1 time, most recently 9 November 2026 |
| On Telegram | t.me/sochi03 |
National news — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 88% 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.
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 in near-verbatim form on 3 other registered channels. This entry also sits inside a group of 4 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts 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 |
|---|---|---|---|
| @sochi_podslushano/841125 Jul 2026, 09:36 UTC | @sochi03/7892 · this entry25 Jul 2026, 09:36 UTC | 1.00 | under a minute |
| @sochi_podslushano/844221 Aug 2026, 16:00 UTC | @sochi03/7922 · this entry21 Aug 2026, 16:00 UTC | 1.00 | under a minute |
| @sochi03/7943 · this entry9 Sept 2026, 08:32 UTC | @sochi_podslushano/84639 Sept 2026, 08:33 UTC | 1.00 | under a minute |
| @sochi03/7974 · this entry9 Oct 2026, 17:42 UTC | @sochi_podslushano/84939 Oct 2026, 17:46 UTC | 1.00 | 4 minutes |
| @sochi_podslushano/850014 Oct 2026, 05:54 UTC | @sochi03/7981 · this entry14 Oct 2026, 05:54 UTC | 1.00 | under a minute |
| @sochi_podslushano/850519 Oct 2026, 17:18 UTC | @sochi03/7986 · this entry19 Oct 2026, 17:18 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @sochi_podslushano | 113 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @sochi_podslushano (69–44) |
| @typicalsochi | 6 (6/6 hand-verifiable sample passed) | 1.00 | 3.9 hours | @typicalsochi (5–1) |
| @typical_sochi_123 | 5 (5/5 hand-verifiable sample passed) | 1.00 | 4.1 hours | this entry (5–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. 67 of the 74 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 118 comparable posts for this entry, running 21 July 2026 to 10 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.
Of the group of 4 channels, the one whose matching posts we hold earliest is @sochi03 — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_copy · clone_mutual · clone_source, last confirmed 11 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.
This channel is in a group of 4 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Nov 2026, 16:18 | 40,272 | -26 |
| 8 Nov 2026, 08:54 | 40,298 | -31 |
| 7 Nov 2026, 06:11 | 40,329 | -25 |
| 6 Nov 2026, 06:00 | 40,354 | -24 |
| 5 Nov 2026, 04:21 | 40,378 | -28 |
| 4 Nov 2026, 05:17 | 40,406 | -10 |
| 3 Nov 2026, 03:29 | 40,416 | -90 |
| 2 Nov 2026, 00:28 | 40,506 | -1,020 |
| 31 Oct 2026, 21:30 | 41,526 | -43 |
| 30 Oct 2026, 23:51 | 41,569 | -63 |
| 29 Oct 2026, 22:17 | 41,632 | -41 |
| 29 Oct 2026, 00:01 | 41,673 | -62 |
| 28 Oct 2026, 00:09 | 41,735 | -50 |
| 27 Oct 2026, 01:18 | 41,785 | -50 |
| 26 Oct 2026, 02:56 | 41,835 | -981 |
| 25 Oct 2026, 02:55 | 42,816 | -2,848 |
| 24 Oct 2026, 00:16 | 45,664 | -74 |
| 22 Oct 2026, 21:28 | 45,738 | -87 |
| 21 Oct 2026, 16:30 | 45,825 | -52 |
| 20 Oct 2026, 13:40 | 45,877 | first reading |
118 posts held, back to 21 July 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 195 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 10 November 2026 |
|---|---|
| Posts held | 118 (21 July 2026 – 10 November 2026) |
| Views total | 244,090 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Nov 2026, 21:44 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 10 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.
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.
Telegram’s own ‘edited’ marker: 1 of 28 posts held from the last 30 days (3.57%) 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).
25-летняя Света ушла из дома в Сочи и бесследно пропала С 4 ноября ничего не известно о местонахождении жительницы Сочи Светланы Макаровой. Почти неделю родные не знают, где она находится и что с ней. Приметы: рост около 155 см, худощавого телосложения, светло-русые волосы, зелёные глаза. Во что была одета в день исчезновения — неизвестно. Если вы видели Светлану или знаете, где она может находиться, позвоните на …
В центре Сочи произошло столкновение мотоцикла и мопеда. Вчера на улице Горького день завершился аварией с участием двух двухколёсных транспортных средств. По сообщениям очевидцев, обоим водителям потребовалась медицинская помощь.
В Сочи прогнозируются смерчи. По информации метеорологов, до конца суток 8 ноября на территории города Сочи и ФТ Сириус имеется опасность формирования смерчей над морем. Жителям и гостям курорта рекомендовано проявлять внимательность, предпринять все необходимые меры предосторожности. В случае чрезвычайной ситуации необходимо звонить по номеру 112.
В горы Сочи на летней резине лучше не соваться. Госавтоинспекция предупреждает водителей об опасной дорожной обстановке. Из-за снегопадов и понижения температуры в горном кластере возможно образование гололёда и снежного наката. На скользкой дороге тормозной путь увеличивается в разы, а резкий манёвр может закончиться аварией. Водителям рекомендуют заранее переобуть автомобили, снизить скорость и соблюдать дистанц…
В Сочи семилетний мальчик погиб в реке Херота. Трагедия произошла вчера вечером, 5 ноября, в районе Адлерского чайсовхоза на улице Петрозаводской. По словам очевидцев, ребёнок играл с мячом, который в какой-то момент улетел в сторону реки. Мальчик побежал за ним и не вернулся. На поиски ребёнка вышли местные жители, к ним присоединились спасатели МЧС. К сожалению, мальчика нашли погибшим. Официальных комментариев…
Зима уже добралась до сочинских гор. Вершины Красной Поляны побелели от первого осеннего снега. На высоте более 2000 метров склоны укрыло белым покрывалом. На Роза Пик сейчас −1 градус, а горы окутаны густым туманом.
В Сочи две легковушки столкнулись лоб в лоб — сообщается о пострадавших. Серьёзное ДТП произошло на Новой Мацесте. По словам очевидцев, автомобили столкнулись при встречном движении. По предварительным данным, в аварии есть пострадавшие. Сколько человек получили травмы и в каком они состоянии, пока неизвестно. Обстоятельства происшествия уточняются.
У школ и детских садов Сочи на асфальте начали появляться большие предупреждающие надписи «ДЕТИ». Такая разметка должна ещё раз напомнить водителям: впереди участок, где в любой момент на дороге может появиться ребёнок. Значит, самое время убрать ногу с газа и быть особенно внимательным. Надписи наносят непосредственно перед образовательными учреждениями, чтобы предупреждение сложно было не заметить.
За последние семь дней на дорогах курорта зафиксировано 4 дорожно-транспортных происшествия. Травмы различной степени тяжести получили 5 человек, включая одного ребёнка. Половина всех аварий недели — две из четырёх — связана с участием мототранспорта. Наиболее безопасными днями стали вторник и пятница, в которые инциденты не регистрировались.
В Сочи произошло нападение на фармацевта. Согласно сообщениям очевидцев, сегодня на улице Донской мужчина нанёс ножом удар сотруднице аптеки «Апрель». Пострадавшая была доставлена в медицинское учреждение на автомобиле скорой помощи. Информация о задержании нападавшего в настоящее время отсутствует.
В Сочи на автомобиль легковой категории упали фрагменты дерева. В связи с осенними неблагоприятными погодными условиями части дерева отломились и упали на автомобиль марки «Audi», находившийся на улице Бытха, 46. Предварительно, пострадавших нет.
На Сочи и Сириус надвигаются ливни, град и ветер до 20 м/с. С ночи и до конца 31 октября в Сочи и на территории ФТ «Сириус» ожидаются сильные дожди с грозами, градом и шквалистым ветром до 15–20 м/с. На реках возможен резкий подъём воды, в горах — риск небольших селей, в акватории Чёрного моря — опасность смерчей. Все службы работают в усиленном режиме. Жителей и гостей просят не отдыхать у воды и не оставлять маши…
Showing the 12 most recent of 118 posts we hold for @sochi03. 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.
We recorded 2 posts on @sochi03 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.
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.
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 29 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 9 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 9 November 2026 — this entry's latest reading, not the date you are reading this.
“Новости | Сочи | Адлер | Красная поляна | Подслушано” (@sochi03), 40,272 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/sochi03.
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.