Telegram RegisterThe public register of Telegram
Telegram profile photo for Сочи.txt

Channel

Сочи.txt

@sochi_txt

On this record: Topic · Growth · Engagement · What this channel posts · Stars · Posts · Posts edited after publishing · Citations · Cite this entry

66,324subscribers

+11,132 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001868444828
TypeChannel
Username@sochi_txt
DescriptionДостоверно, оперативно
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live17 September 2026
Measurements held35
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/sochi_txt

Topic

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 20 August 2026 and assigned it the closest of 31 fixed categories, at 94% 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.

Growth

55,19266,32460,7586 August 2026 — 55,192 subscribers6 August 2026 — 55,358 subscribers7 August 2026 — 55,945 subscribers8 August 2026 — 55,910 subscribers9 August 2026 — 55,990 subscribers10 August 2026 — 55,925 subscribers11 August 2026 — 55,930 subscribers12 August 2026 — 55,892 subscribers13 August 2026 — 55,905 subscribers14 August 2026 — 56,052 subscribers15 August 2026 — 56,341 subscribers16 August 2026 — 56,569 subscribers17 August 2026 — 56,585 subscribers18 August 2026 — 56,723 subscribers19 August 2026 — 56,687 subscribers20 August 2026 — 56,643 subscribers21 August 2026 — 56,684 subscribers23 August 2026 — 57,006 subscribers24 August 2026 — 56,950 subscribers25 August 2026 — 56,857 subscribers27 August 2026 — 56,791 subscribers28 August 2026 — 56,741 subscribers29 August 2026 — 56,709 subscribers29 August 2026 — 56,635 subscribers30 August 2026 — 56,583 subscribers31 August 2026 — 56,528 subscribers1 September 2026 — 56,707 subscribers3 September 2026 — 56,833 subscribers4 September 2026 — 60,484 subscribers6 September 2026 — 61,434 subscribers10 September 2026 — 63,337 subscribers12 September 2026 — 63,821 subscribers13 September 2026 — 64,411 subscribers15 September 2026 — 66,296 subscribers17 September 2026 — 66,324 subscribers6 August 202617 September 2026
35 measurements spanning 42 days, net +11,132. 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 53,522–67,994 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 35
Measured (UTC)SubscribersChange
17 Sept 2026, 11:3866,324+28
15 Sept 2026, 12:3666,296+1,885
13 Sept 2026, 20:5864,411+590
12 Sept 2026, 06:3863,821+484
10 Sept 2026, 02:3863,337+1,903
6 Sept 2026, 23:2061,434+950
4 Sept 2026, 11:3760,484+3,651
3 Sept 2026, 00:0956,833+126
1 Sept 2026, 18:5556,707+179
31 Aug 2026, 19:4556,528-55
30 Aug 2026, 21:5456,583-52
29 Aug 2026, 23:5756,635-74
29 Aug 2026, 03:2356,709-32
28 Aug 2026, 03:3756,741-50
27 Aug 2026, 00:3756,791-66
25 Aug 2026, 23:1156,857-93
24 Aug 2026, 22:3556,950-56
23 Aug 2026, 11:4357,006+322
21 Aug 2026, 23:4756,684+41
20 Aug 2026, 21:0256,643first reading

Engagement

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

ERR · 30 days
23.8%
avg views ÷ 66,324 subscribers
Avg views / post
15,800
691 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
691
of 1,131 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 62 of 691 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 20 September 2026
Posts held1,131 (5 August 202620 September 2026)
Views total10,925,933
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken20 Sept 2026, 04:33 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

Links
1,740

Lifetime counters from Telegram’s own channel header, read 20 September 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.

Telegram Stars

Stars received
369
across the posts below
Posts paid on
65
of 1,000 we hold a reading for · 7%
Most on one post
42
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @sochi_txt. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 1,000 most recent posts we hold for this entry (the sample is capped at 1,000), published 10 August 2026 to 20 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

20 Sept 2026, 00:14 UTC≈4,990 views0 reactions1 Starread 20 September 2026

Ракетная опасность на территории Краснодарского края, сообщает РСЧС, отмена 03:12

19 Sept 2026, 22:58 UTC≈6,570 viewsread 20 September 2026

Сочи — отбой угрозы атаки БПЛА, сообщил глава администрации Андрей Прошунин

19 Sept 2026, 22:58 UTC≈6,590 views0 reactions4 Starsread 20 September 2026

Аэропорт Сочи — ограничения сняты, сообщает Росавиация

19 Sept 2026, 22:54 UTC≈6,960 viewsread 20 September 2026

Сириус — отбой угрозы атаки БПЛА, сообщает глава администрации Дмитрий Плишкин

19 Sept 2026, 22:51 UTC≈7,010 viewsread 20 September 2026

Отбой угрозы, сообщают речевые установки

19 Sept 2026, 21:24 UTC≈12,200 viewsread 20 September 2026

Сириус — угроза атаки БПЛА, сообщает глава администрации Дмитрий Плишкин

19 Sept 2026, 21:23 UTC≈12,500 viewsread 20 September 2026

Сочи — угроза атаки БПЛА, сообщает глава муниципального образования Андрей Прошунин

19 Sept 2026, 21:23 UTC≈12,800 viewsread 20 September 2026

Воздушная тревога, атака, сирены, всем в укрытие

19 Sept 2026, 20:51 UTC≈14,100 viewsread 20 September 2026

Запуски салютов во время режима атаки в Молдовке ///

19 Sept 2026, 20:47 UTC≈14,400 viewsread 20 September 2026

Аэропорт Сочи — введены ограничения на приём и выпуск рейсов, сообщает Росавиация

19 Sept 2026, 20:34 UTC≈14,600 viewsread 20 September 2026

Аэропорт Сочи — ограничения сняты

19 Sept 2026, 19:58 UTC≈17,400 views0 reactions6 Starsread 20 September 2026

Сочи — отбой угрозы атаки БПЛА, сообщил глава администрации Андрей Прошунин

Showing the 12 most recent of 1,131 posts we hold for @sochi_txt. 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.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Posts edited after publishing

@sochi_txt edited 19 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
8 August 2026
Most recent edit
17 September 2026

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

Named by 9 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.

Names

Channels on the register whose handles appear in this channel's posts.

Любимый❤️Сочи
@love_sochi · 72,917
84 posts
Автомобильный 🚘 Сочи
@sochi_mobil · 8,930
58 posts
Сочи Главный
@sochiglav · 5,917
22 posts
Почти Сочинец
@talalin_roma · 4,192
12 posts
Пляжи ⛱️ Сочи
@beach_sochi · 8,671
10 posts
Экономика 🧮 Сочи
@sochi_economyc · 4,203
9 posts
Понаехи 😎 Сочи | Сириус
@sochi_ponaehi · 11,620
7 posts
Рестораны 🍽️ Сочи
@restaurant_sochi · 7,619
6 posts
Лазаревский район Сочи 🌳
@lazarevss · 1,417
5 posts
Округа́ Сочи 📍
@selo_sochi · 5,515
5 posts
Школы и детсады Сочи
@sochi_edu · 3,852
5 posts
Адлерский район Сочи 🐬
@adlerskyy · 3,818
4 posts
Центральный район Сочи 🌴
@centralniy_sochi · 2,790
4 posts
Адлерский район Сочи
@adler_on · 4,388
3 posts
Сириус • Сочи • барахолка
@allosirius · 4,581
3 posts
Центральный район Сочи
@centrsochi · 5,919
3 posts
Хостинский район Сочи
@khosta_rika · 5,439
3 posts
Лазаревский район Сочи
@laz_on · 3,754
3 posts
Любимый🧡Сочи чат
@love_sochi_life · 11,933
3 posts
Сириусяне 🏘️
@sirius_life · 9,417
3 posts
Сириус 🇷🇺
@sirius_okrug · 30,618
3 posts
Интересный Сочи
@sochi_longrid · 17,081
3 posts
Хостинский район Сочи 🌊
@hostinskiy · 1,737
2 posts
Отели 🏩 Сочи и Сириуса
@sochi_oteli · 3,104
2 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.

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

“Сочи.txt” (@sochi_txt), 66,324 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/sochi_txt.

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.