Channel
@vostorgsochi
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
6,019subscribers
-114 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001685317383 |
|---|---|
| Type | Channel |
| Username | @vostorgsochi |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 4 October 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 4 October 2026 |
| On Telegram | t.me/vostorgsochi |
Travel — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 41% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Oct 2026, 22:35 | 6,019 | -33 |
| 25 Sept 2026, 09:17 | 6,052 | -12 |
| 16 Sept 2026, 18:18 | 6,064 | +1 |
| 9 Sept 2026, 05:00 | 6,063 | -14 |
| 4 Sept 2026, 05:00 | 6,077 | -36 |
| 31 Aug 2026, 23:25 | 6,113 | -5 |
| 28 Aug 2026, 21:08 | 6,118 | -2 |
| 26 Aug 2026, 04:03 | 6,120 | -3 |
| 22 Aug 2026, 22:07 | 6,123 | +1 |
| 19 Aug 2026, 03:45 | 6,122 | -6 |
| 16 Aug 2026, 04:28 | 6,128 | -4 |
| 12 Aug 2026, 22:24 | 6,132 | -5 |
| 10 Aug 2026, 07:00 | 6,137 | +2 |
| 7 Aug 2026, 02:37 | 6,135 | +2 |
| 6 Aug 2026, 17:48 | 6,133 | first reading |
5 posts held, back to 23 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 9 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 5 posts for this entry, the most recent from 31 July 2026. An engagement rate over an empty window would be a number about nothing.
197 reactions across 5 posts, in 10 distinct kinds. The most used accounts for 53.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 106 | 53.8% | |
| 👍 | 48 | 24.4% | |
| 🔥 | 23 | 11.7% | |
| 💯 | 6 | 3.05% | |
| ❤🔥 | 4 | 2.03% | |
| 🆒 | 3 | 1.52% | |
| 🤨 | 3 | 1.52% | |
| 🥱 | 2 | 1.02% | |
| 👎 | 1 | 0.508% | |
| 💔 | 1 | 0.508% |
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 5 of the 5 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 197 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 23 July 2026 to 31 July 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.
Мы с Натой, моей женой, регулярно ломаем голову над вопросом «куда сходить». Не потому что мало мест, а потому что мы привыкаем к однообразию времяпрепровождения, и охота за новыми совместными впечатлениями стала заметной. Если вы понимаете, о чём я говорю, возьмите на заметку формат совместного массажа: когда вас и вашу половинку мнут одновременно два мастера. Массаж — в целом занятие раскайфовочное и релаксационно…
🔥20❤7
Кормилец Адлер Сто лет назад, когда Сочи приобретал облик стильного города-курорта, на отшибе стоял Адлер. Грубый, но наглядный пример: если тогдашний Сочи — это палуба «Титаника», где гости ходят в костюмах и платьях, пьют шампанское и вот это всё, то Адлер — машинный зал, где трудились рабочие в поте лица, дабы вся эта махина была на плаву. Советский Адлер был профилирован под район сельхозназначения. Идея была п…
❤42👍15💯6
Огненный бой в небе Сочи В годы ВОВ в Большом Сочи не происходило боевых действий на суше — это многим знакомая аксиома. Но это не совсем так. Действительно, вражеские войска не дошли до Сочи пешком, но боевые столкновения советской армии с фашистами велись на воде и в воздухе. Про морские сражения я немного писал здесь. В военное время у Сочи было две основные функции: быть городом-госпиталем и выполнять роль стра…
👍25❤12❤🔥3🥱2💔1
Кофейня «Истории» (ранее Stories) пригласили чету Набоковых на дегустацию летнего меню. Мы любим Хосту, это заведение и, конечно, не можем отказаться от щедрых дегустаций. Ниже — текст моей жены Наташи, которая особенно вкусно отрецензировала угощения. Вафля с тунцом и яйцом — это взрыв насыщенности вкуса, но в очень деликатной и нежной комбинации ингредиентов. Плюс десятибалльное попадание в тренд на белковые блюда…
❤24👍8🔥3🆒3❤🔥1
график топовых групповых многодневных походов от экотрип на август и сентябрь! > 8–12 августа | легендарная «тридцатка» лаго-наки, восхождение на оштен, приют фишт — всё это один из главных маршрутов причерноморского кавказа, любимый туристами на протяжении многих поколений. цена: 19.5к / чел. + допы ~4к (ласточка, гостевой дом, трансфер, уазик, пропуск в заповедник). ___ > 17–20 августа | озеро кардывач и синеок…
❤21🤨3👎1
Showing the 5 most recent of 5 posts we hold for @vostorgsochi. 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.
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.
Named by 3 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.
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 27 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 4 October 2026 — this entry's latest reading, not the date you are reading this.
“Восторг Сочи | блог сочинца” (@vostorgsochi), 6,019 subscribers as measured 4 October 2026. Telegram Register, tgregister.com/channel/vostorgsochi.
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.