Telegram RegisterThe public register of Telegram

Channel

Центральный район Сочи 🌴

@centralniy_sochi

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

2,706subscribers

+11 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1003060030143
TypeChannel
Username@centralniy_sochi
CreatedBetween 1 August 2025 and 31 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/centralniy_sochi

Growth

2,6912,7062,698.56 August 2026 — 2,695 subscribers6 August 2026 — 2,695 subscribers9 August 2026 — 2,691 subscribers12 August 2026 — 2,706 subscribers6 August 202612 August 2026
4 measurements spanning 6 days, net +11. 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 2,689–2,708 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 13:452,706+15
9 Aug 2026, 10:512,691-4
6 Aug 2026, 05:192,695no change
6 Aug 2026, 04:522,695first reading

Engagement

21 posts held, back to 20 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
35.4%
avg views ÷ 2,706 subscribers
Avg views / post
958
8 posts measured
Reaction rate
0.546%
reactions ÷ views · ER floor
Posts in window
8
of 21 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 3 of 8 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 6 August 2026
Posts held21 (20 June 20266 August 2026)
Views total7,663
Reactions total21
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 16:14 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
2m 33s
Average length
51s

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

24 reactions across 6 posts, in 4 distinct kinds. The most used accounts for 54.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😱1354.2%
625.0%
416.7%
💯14.17%

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

Measured over the 21 most recent posts we hold, published 20 June 2026 to 6 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.

Recent posts

6 Aug 2026, 16:03 UTC125 viewsread 7 August 2026
Forwarded from @sochi_ponaehiPhoto

Актуальный топ-10 сочинских рынков, где можно найти свежие сезонные фрукты 🍈Адлерский рынок — Демократическая, 38/3А. Парковка: небольшая у главного входа, днём часто забита. Средняя оценка: 4,9 / 5 🍎Ярмарка на Фабрициуса — Яна Фабрициуса, 37/1. Парковка: собственная площадка, как правило есть места. Средняя оценка: 4,9 / 5 🍆Рынок “Кудепста” — Ростовская, 14. Парковка: бесплатная стоянка прямо у входа (≈20 машин).

6 Aug 2026, 15:03 UTC256 viewsread 7 August 2026
Photo

❌Эти методы вам не помогут! Шея болит. Голова гудит. Ночью немеют руки 🥲 «Я перепробовала всё — массажи, таблетки, остеопатов… Ничего не помогает надолго. Голова и шея болят, руки немеют по ночам…» - Айгуль, 41 год Знакомо? ▪️ Массаж помогает… на пару недель. ▪️ Таблетки снимают боль… до следующего обострения. ▪️ Уколы приносят облегчение… ненадолго. А потом всё возвращается. И становится только хуже. ☝️Знаете, п

3 Aug 2026, 14:30 UTC194 views1 reactionsread 7 August 2026
Forwarded from @talalin_romaPhoto

С парковками в центре Сочи всё сложно, поэтому любое новое место сразу становится событием У бывшего кинотеатра “Спутник” на улице Несебрской открыли новую муниципальную парковку. После возврата участка в город его решили не застраивать, а временно использовать под стоянку — именно об этом давно просили автомобилисты. Всего здесь 123 машиноместа, включая 13 мест для людей с инвалидностью. Парковка работает круглосу

1

3 Aug 2026, 05:50 UTC513 viewsread 7 August 2026

⚡️ Ночью в центре Сочи возможны перебои с водой В ночь с 3 на 4 августа (с 23:00 до 06:00) в Центральном районе будут проводить ремонт водовода на улице Пионерской. Из-за этого в ряде домов возможно пониженное давление вплоть до полного отсутствия воды. Под отключение частично попадают: • ул. Пионерская • ул. Мичурина • ул. Красная • ул. Молодогвардейская • ул. Кошевого Жителям рекомендуют заранее сделать запас в

23 Jul 2026, 17:35 UTC≈1,670 views11 reactionsread 7 August 2026
Video

Сочинка искала квартиры в сети и увидела объявление с фотографиями своей Удивлению девушки не было предела. ℹ️ Наши страницы

5😱5💯1

22 Jul 2026, 20:02 UTC895 viewsread 7 August 2026
Forwarded from @love_sochiPhoto

⚡️Сразу два пожара в Сочи в эти минуты На пляже Куба сгорел склад с сапами, а в Нижней Шиловке горит сарай. /// 📹@chp_sochi ℹ️ Наши страницы

19 Jul 2026, 14:01 UTC≈2,030 viewsread 7 August 2026

⚡️ Горячую воду отключат на 11 дней 📍Котельная № 15 (Барановское шоссе): с 20 по 31 июля 🏠 Адреса: - Гайдара, д. 1, 10, 11; - Перевальная, д. 19; - Барановское шоссе, д. 6, 7, - Ленинградская, д. 7, 7а (Мотель Меридиан), - Батумское шоссе, д. 10, 12, 14, 14а (УК Гранд), 16, 18, 18 (Дагомысчай), 22, 23, 24, 25, 26, 27, 28, 29/1, 31, 33, 35, 35а, 37, 39, 39а, 41, 43, 45, 47, 49, 51, 53, 55, 59, 63, 67, 67а, 67б, 67в;

17 Jul 2026, 17:55 UTC≈1,980 views9 reactionsread 7 August 2026
Video

⚡️ На защиту Сочи от оползней требуется более 700 млрд рублей Проблема оползней в Сочи остаётся одной из самых серьёзных для города. По данным администрации, сейчас на курорте насчитывается более 2600 оползневых участков, где необходимы противооползневые мероприятия. Как сообщил глава Сочи Андрей Прошунин, чтобы комплексно решить эту проблему, потребуется свыше 700 млрд рублей. Для сравнения: годовой бюджет города

😱81

6 Jul 2026, 08:46 UTC≈1,570 views0 reactionsread 7 August 2026

Ведутся работы на участке водовода диаметром 100 мм по улице Альпийская. На период проведения работ ограничение водоснабжения может наблюдаться у жителей ряда домов по улицам Альпийская 37. Завершить необходимый комплекс работ планируется до 15:00. ℹ️ Наши страницы

5 Jul 2026, 14:05 UTC≈1,430 viewsread 7 August 2026

Напоминаем об отключении горячего водоснабжения 📍Котельная №14 зона "Ареда": с 06 по 17 июля 🏠 Адреса: - Альпийская, д. 7, 9, 13, 15, 17, 19, 31а, 33, 33а, 35, 37, 39, 41, 80, 82; - Параллельная, д. 8, 11-12б/1, 18, 20, 23, 24, 25, 26, 27, 30, 34, 36, 38; - Севастопольская, д. 9, 11, 17, 18, 22, 27а, 27б, 29, 31, 33, 35, 37, 39, 39литА; - Невская, д. 2, 4, 6, 8, 10, 12, 14, 16, 21, 21а, 32, 58; - Тоннельная, д. 1,

5 Jul 2026, 14:03 UTC≈1,210 views1 reactionsread 7 August 2026

Напоминаем об отключении горячего водоснабжения 📍Котельная №1: с 06 июля по 10 июля 🏠 Адреса: - Курортный проспект, д. 1; - Виноградная, д. 2 (к.3, 4, 8,), 2/3 (к.5, 6, 7, 9), 2б, 8, 10, 12, 13, 14, 15/1, 17, 22, 25, 27а, 31, 33а, 43/2; - Госпитальная, д. 6, - Цюрупы, д. 3, 4б, 5, 6, 7, 7а, 9, 9а, 11, 11а, 13а, 16. Диспетчерская служба: 264-30-33 ℹ️ Наши страницы

1

1 Jul 2026, 16:40 UTC≈1,210 viewsread 7 August 2026

Сообщаем, что 02.07.2026 г. с 09:00 до 15:00 в связи с работами, проводимыми на тепловых сетях, возможны перебои ГВС у абонентов по адресам: - Юных Ленинцев, д. 7, 9 - Конституции, д. 38 Диспетчерская служба: 264-30-33 ℹ️ Наши страницы

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

Citation-graph rank

Citation-graph rank — 193,877 of 1,480,688entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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

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

“Центральный район Сочи 🌴” (@centralniy_sochi), 2,706 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/centralniy_sochi.

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.