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 10 August 2026 and assigned it the closest of 31 fixed categories, at 99% 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.
Views per post sit far above this size band
44,000 average views per post against 37,840 subscribers — an engagement rate of 116.2%. Across the 573 registered channels in the same cohort — 31,684–99,950 subscribers, posting mainly in Ukrainian — the middle half sit between 10.2% and 26.3%, with a median of 17.2%.
What this was computed from
Window
30 days (6 October 2026 – 5 November 2026)
Posts measured
27 of 27 published in the window (0 exact, 27 rounded by Telegram)
Views totalled
1,187,600
Mature posts only
128.7% over 23 posts read at least 24h after publication
When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.
This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.
Recorded under the key err_high, last confirmed 5 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.
Growth
60 measurements spanning 93 days, net +155. 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 37,683–38,315 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 60
Measured (UTC)
Subscribers
Change
9 Nov 2026, 00:38
38,207
+72
7 Nov 2026, 15:50
38,135
+79
6 Nov 2026, 17:06
38,056
+86
5 Nov 2026, 19:27
37,970
+130
4 Nov 2026, 15:48
37,840
+55
3 Nov 2026, 19:09
37,785
+29
2 Nov 2026, 20:45
37,756
-7
1 Nov 2026, 20:55
37,763
-6
31 Oct 2026, 19:58
37,769
-12
30 Oct 2026, 20:51
37,781
-5
29 Oct 2026, 19:58
37,786
-17
28 Oct 2026, 16:35
37,803
-9
27 Oct 2026, 14:07
37,812
-2
26 Oct 2026, 14:14
37,814
-6
25 Oct 2026, 11:37
37,820
-2
24 Oct 2026, 09:16
37,822
-9
23 Oct 2026, 10:46
37,831
-8
22 Oct 2026, 09:47
37,839
-2
21 Oct 2026, 03:09
37,841
-6
19 Oct 2026, 23:56
37,847
first reading
Engagement
97 posts held, back to 24 June 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 176 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
104.8%
avg views ÷ 38,207 subscribers
Avg views / post
40,000
43 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
43
of 97 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 5 of 43 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 8 November 2026
Posts held
97 (24 June 2026 – 8 November 2026)
Views total
1,721,000
Reactions total
0
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
9 Nov 2026, 11:00 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
56
Links
369
Lifetime counters from Telegram’s own channel header, read 9 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Telegram Stars
Stars received
41
across the posts below
Posts paid on
13
of 97 we hold a reading for · 13%
Most on one post
12
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @chornomorsk_svitlo. 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 97 most recent posts we hold for this entry, published 24 June 2026 to 8 November 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
Telegram’s own ‘edited’ marker: 7 of 43 posts held from the last 30 days (16.3%) 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).
💡Чорноморськ: графік відключень електроенергії на 7 листопада
❎з 5:00 до 12:30
❎з 15:30 до 22:30
⌛️Всього без світла: 14:30
Також з 08:00 до 19:00 можливі короткочасні перерви в електропостачанні (до години) в частині Одеського району.
💡Чорноморськ: графік відключень електроенергії на 6 листопада
❎з 0:00 до 1:30
❎з 8:00 до 15:30
❎з 18:30 до 22:30
⌛️Всього без світла: 13:00
Showing the 12 most recent of 97 posts we hold for @chornomorsk_svitlo. 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
@chornomorsk_svitlo edited 4 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
10 August 2026
Most recent edit
3 November 2026
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
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.
Chornomorsk INFO @ourChornomorsk · 22,935 Telegram ranks this channel #2 of 63 here — alongside 62 others — read 23 September 2026
Новости Одесса | Одеса @our_odessa · 438,197 Telegram ranks this channel #35 of 81 here — alongside 80 others — read 10 August 2026
Черноморск, как он есть @chornomorsk · 29,951 Telegram ranks this channel #43 of 80 here — alongside 79 others — read 8 September 2026
ОДЕССА ИНФО | Свет | Радар @inform_odesa · 32,792 Telegram ranks this channel #43 of 63 here — alongside 62 others — read 3 September 2026
Одесса INFO ⚓️ 🇺🇦 Новости | Одеса @odessa_infonews · 991,514 Telegram ranks this channel #52 of 79 here — alongside 78 others — read 8 August 2026
Черный список Одесса @black_list_odessa · 23,139 Telegram ranks this channel #55 of 74 here — alongside 73 others — read 19 September 2026
Світло ОДЕСА | Вода, Газ @odesa_svet1 · 20,647 Telegram ranks this channel #63 of 68 here — alongside 67 others — read 22 September 2026
🚨КАЛІБР🚨 @temporis_odesa · 93,114 Telegram ranks this channel #67 of 73 here — alongside 72 others — read 17 August 2026
ОДЕССА ИНФО LIVE - радар Одеса @odessa_inform · 375,529 Telegram ranks this channel #69 of 75 here — alongside 74 others — read 10 August 2026
Повітряна тривога️ | Бережіть себе! @raketna_neb · 215,786 Telegram ranks this channel #73 of 76 here — alongside 75 others — read 11 August 2026
Хуевая Одесса @xydessa · 944,866 Telegram ranks this channel #77 of 83 here — alongside 82 others — read 8 August 2026
This channel appears in 11 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 9 November 2026 — this
entry's latest reading, not the date you are reading this.
“Отключения света - Черноморск” (@chornomorsk_svitlo), 38,207 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/chornomorsk_svitlo.
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.
