Telegram RegisterThe public register of Telegram
Telegram profile photo for ЧС СОЧИ 🔞

Channel

ЧС СОЧИ 🔞

@chs_sochi_tg

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Polls · Citations · Telegram's recommendations · Cite this entry

6,754subscribers

-17 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001396138399
TypeChannel
Username@chs_sochi_tg
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live12 November 2026
Measurements held25
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/chs_sochi_tg

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 35% 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 5 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.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@chplazarevskoe/218779 Aug 2026, 04:47 UTC@chs_sochi_tg/8527 · this entry9 Aug 2026, 04:47 UTC1.00under a minute
@chs_sochi_tg/8533 · this entry10 Aug 2026, 05:59 UTC@chplazarevskoe/2190310 Aug 2026, 06:00 UTC1.00under a minute
@chplazarevskoe/2201714 Aug 2026, 19:31 UTC@chs_sochi_tg/8563 · this entry14 Aug 2026, 19:31 UTC1.00under a minute
@chplazarevskoe/2212719 Aug 2026, 06:07 UTC@chs_sochi_tg/8584 · this entry19 Aug 2026, 06:08 UTC1.00under a minute
@chplazarevskoe/233396 Nov 2026, 10:40 UTC@chs_sochi_tg/8838 · this entry6 Nov 2026, 10:40 UTC1.00under a minute
@typicalsochi/303819 Aug 2026, 04:35 UTC@chs_sochi_tg/8527 · this entry9 Aug 2026, 04:47 UTC1.0013 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
@chplazarevskoe51 (8/8 hand-verifiable sample passed)1.00under a minute@chplazarevskoe (48–3)
@typicalsochi29 (8/8 hand-verifiable sample passed)1.001.6 hours@typicalsochi (28–1)
@sochitypical8 (8/8 hand-verifiable sample passed)1.0068 minutes@sochitypical (6–2)
@mcusochi6 (6/6 hand-verifiable sample passed)1.0039 minutes@mcusochi (4–2)
@officialsochi5 (5/5 hand-verifiable sample passed)1.0013 minutes@officialsochi (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. 77 of the 77 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 83 comparable posts for this entry, running 2 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).

Of the group of 4 channels, the one whose matching posts we hold earliest is @chplazarevskoe. That is a statement about our reading window, not a claim of authorship.

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.

Channels linked by matching posts

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.

Growth

6,7546,8656,809.57 August 2026 — 6,771 subscribers7 August 2026 — 6,771 subscribers8 August 2026 — 6,774 subscribers11 August 2026 — 6,781 subscribers14 August 2026 — 6,803 subscribers17 August 2026 — 6,819 subscribers21 August 2026 — 6,795 subscribers24 August 2026 — 6,815 subscribers27 August 2026 — 6,819 subscribers30 August 2026 — 6,814 subscribers2 September 2026 — 6,811 subscribers7 September 2026 — 6,835 subscribers11 September 2026 — 6,856 subscribers15 September 2026 — 6,854 subscribers27 September 2026 — 6,865 subscribers5 October 2026 — 6,854 subscribers11 October 2026 — 6,844 subscribers18 October 2026 — 6,842 subscribers21 October 2026 — 6,834 subscribers24 October 2026 — 6,823 subscribers27 October 2026 — 6,803 subscribers30 October 2026 — 6,785 subscribers2 November 2026 — 6,766 subscribers8 November 2026 — 6,764 subscribers12 November 2026 — 6,754 subscribers7 August 202612 November 2026
25 measurements spanning 97 days, net -17. 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 6,737–6,882 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 25
Measured (UTC)SubscribersChange
12 Nov 2026, 10:576,754-10
8 Nov 2026, 11:016,764-2
2 Nov 2026, 15:316,766-19
30 Oct 2026, 08:466,785-18
27 Oct 2026, 18:406,803-20
24 Oct 2026, 08:256,823-11
21 Oct 2026, 16:296,834-8
18 Oct 2026, 04:176,842-2
11 Oct 2026, 23:386,844-10
5 Oct 2026, 07:216,854-11
27 Sept 2026, 05:396,865+11
15 Sept 2026, 08:216,854-2
11 Sept 2026, 18:186,856+21
7 Sept 2026, 02:176,835+24
2 Sept 2026, 20:346,811-3
30 Aug 2026, 12:436,814-5
27 Aug 2026, 11:026,819+4
24 Aug 2026, 20:386,815+20
21 Aug 2026, 03:056,795-24
17 Aug 2026, 17:576,819first reading

Engagement

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

ERR · 30 days
5.80%
avg views ÷ 6,754 subscribers
Avg views / post
392
53 posts measured
Reaction rate
0.56%
reactions ÷ views · ER floor
Posts in window
53
of 121 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 30 of 53 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 16 November 2026
Posts held121 (1 August 2026 – 16 November 2026)
Views total20,774
Reactions total68
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Nov 2026, 15:05 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
≈2,180
Videos
≈1,270
Links
≈1,660

Lifetime counters from Telegram’s own channel header, read 16 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
17m 42s
Average length
41s

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

122 reactions across 45 posts, in 19 distinct kinds. The most used accounts for 17.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍2117.2%
🔥1713.9%
🙏1613.1%
❤1310.7%
😱119.02%
🤬97.38%
🤔64.92%
🤝64.92%
👎54.10%
👏32.46%
🗿32.46%
😨32.46%
🕊21.64%
🥴21.64%
⚡10.82%
😢10.82%
🙊10.82%
🤣10.82%
🫡10.82%

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

Measured over the 121 most recent posts we hold, published 1 August 2026 to 16 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
5.79%
7 of 121 posts carry an ad marker
Regulatory tokens
7
posts carrying an erid · 7 distinct tokens
Median views · ads
427
over 7 measured posts
Median views · rest
410
over 114 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
2VtzqvMwNU3117 August 202617 August 2026
2VtzqvQuM2j118 August 202618 August 2026
2Vtzqvgn7Le14 August 20264 August 2026
2VtzqwUgHzv111 November 202611 November 2026
2VtzqxCRzmU15 November 20265 November 2026
2VtzqxXy5iA15 August 20265 August 2026
2VtzqxgsfgR126 October 202626 October 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 121 most recent posts we hold, published 1 August 2026 to 16 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 53 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).

16 Nov 2026, 12:17 UTC76 views0 reactionsread 16 November 2026
Photo

💧 ДОСТАВКА ВОДЫ И ПРОМЫВКА СКВАЖИН! Оказываем услуги по доставке питьевой и технической воды, а также промывке скважин. 🚛 Доставка воды объёмом 5 и 10 кубов: • Питьевая и техническая вода. • Заполнение бассейнов и любых ёмкостей. • Полив цветов, клумб, участков и зелёных насаждений. • Мойка автомобильных дорог и территорий. 🔧 ПРОМЫВКА СКВАЖИН Проводим промывку скважин. Поможем с решением вопросов, связанных с обс…

16 Nov 2026, 09:42 UTC159 viewsread 16 November 2026
Video

🥲 Грустное зрелище, половина отделов закрыта, людей нет.

16 Nov 2026, 05:46 UTC201 views3 reactionsread 16 November 2026
Photo

🚘 РОЗЫГРЫШ TOYOTA PRADO! 🖤 Мечтаете о своём внедорожнике? Возможно, именно вам улыбнётся удача! 🎁 Разыгрываем Toyota Prado! Как участвовать: ✅ Подписаться на канал автосалона:@AutoEuropaLuxemburg ✅ Написать нашему менеджеру @asistent_eurocars 📩 Сообщение: «Хочу Авто» 🎯 Победители определяются случайным образом. ‼️Итоги розыгрыша — 18.11.2026 в 12:30 (МСК) 🎖 Участникам СВО — специальная скидка в нашем автосалон…

🔥2👍1

15 Nov 2026, 17:48 UTC240 viewsread 16 November 2026

16 ноября с 04:00 до полуночи в акваториях морского порта Сочи и Имеретинского порта Сириуса пройдут учебные стрельбы и гранатометания

15 Nov 2026, 05:59 UTC357 viewsread 16 November 2026

❗️Атака беспилотников остановила поезда в Ростовской области. Есть погибший и пострадавшие. Силы ПВО уничтожили около 50 БПЛА над Таганрогом, Ростовом-на-Дону и семью районами области, сообщил губернатор Юрий Слюсарь. ▪️В Таганроге повреждена электроподстанция, обслуживающая железную дорогу. Погиб главный инженер. ▪️Из-за отключения электричества движение поездов на участке от Таганрога-Пассажирского до станции Ми…

14 Nov 2026, 19:40 UTC389 views1 reactionsread 16 November 2026

🌊 В Черном море у берегов Кубани вода все еще находится на отметке примерно +17 градусов В середине ноября море пока не спешит остывать: температура воды на курортах края остается сравнительно высокой.

👍1

14 Nov 2026, 19:37 UTC356 viewsread 16 November 2026

В Сочи пройдут учебные стрельбы ️❗️15 ноября с 04:00 до 24:00 в акватории Морского порта Сочи состоятся учебные стрельбы. Просим вас сохранять спокойствие. Отработка действий военными – залог нашей с вами безопасности!

14 Nov 2026, 19:32 UTC344 viewsread 16 November 2026
Video

Антону Купидону сорвали рекламную интеграцию 😁

14 Nov 2026, 17:26 UTC306 views1 reactionsread 16 November 2026
Forwarded from @chplazarevskoeVideo

Поздравление с днем рождения в Абхазии 🍊 Ну и как же тут без букета из мандаринов.

👍1

14 Nov 2026, 08:37 UTC335 viewsread 16 November 2026
Photo

🌊 Землетрясение магнитудой 3,1 произошло в Чёрном море недалеко от Сочи. Подземные толчки зафиксировали около пяти утра. По данным мониторинга IDP-CS, очаг находился на глубине всего 2 км, а эпицентр — в акватории Чёрного моря, неподалёку от побережья курорта. Магнитуда составила 3,1 📷 Карта: IDP-CS

14 Nov 2026, 07:50 UTC315 views1 reactionsread 16 November 2026

В Сочи пройдут учебные стрельбы ️️❗14 ноября с 09:00 до 15 ноября 00:00 в акватории Морского порта Сочи состоятся учебные гранатометания. Просим вас сохранять спокойствие. Отработка действий военными – залог нашей с вами безопасности!

🫡1

13 Nov 2026, 11:14 UTC339 views1 reactionsread 16 November 2026

С 7 по 13 ноября силами Черноморского флота в северо-западной части Чёрного моря уничтожено два БЭКа, сообщает МО РФ

🤝1

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

Polls

The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

4 Nov 2026, 20:23 UTCAnonymous Poll181 voters

Почувствовали?

  1. Да50%
  2. Нет51%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

28 Oct 2026, 17:16 UTCAnonymous Poll169 voters

Согласны?

  1. Да51%
  2. Нет22%
  3. Мне все равно31%

The shares total 104%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 121 most recent posts we hold, published 1 August 2026 to 16 November 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Forward network

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

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.

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.

Новости Сочи 24
@sochi24tv · 32,038
Telegram ranks this channel #9 of 92 here — alongside 91 others — read 5 September 2026
ПОДСЛУШАНО Лазаревское 🌴
@Podslushano_Laza · 19,294
Telegram ranks this channel #19 of 36 here — alongside 35 others — read 1 October 2026
Новости | Сочи | Адлер | Красная поляна | Подслушано
@sochi03 · 40,159
Telegram ranks this channel #20 of 80 here — alongside 79 others — read 29 August 2026
Подслушано Сочи
@sochi_podslushano · 44,269
Telegram ranks this channel #46 of 84 here — alongside 83 others — read 27 August 2026

This channel appears in 4 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 12 November 2026 — this entry's latest reading, not the date you are reading this.

“ЧС СОЧИ 🔞” (@chs_sochi_tg), 6,754 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/chs_sochi_tg.

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.