Telegram RegisterThe public register of Telegram

Channel

Черноморэнерго

@chernomorenergo

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

492subscribers

+249 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003964256960
TypeChannel
Username@chernomorenergo
CreatedBetween 1 April 2026 and 25 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/chernomorenergo

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

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 word for word on 1 other registered channel. 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 (1 of the pairs behind the counts below)
Posted firstThenOverlapGap
@mintransenergoabh/50525 Jul 2026, 05:02 UTC@chernomorenergo/171 · this entry25 Jul 2026, 05:31 UTC1.0029 minutes
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@mintransenergoabh5 (5/5 hand-verifiable sample passed)1.0072 minutes@mintransenergoabh (41)

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. None of the 1 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 18 comparable posts for this entry, running 25 July 2026 to 6 August 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).

Across the whole group of 2, the earliest publisher we hold is @mintransenergoabh. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 7 August 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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

243492367.56 August 2026 — 243 subscribers7 August 2026 — 243 subscribers14 August 2026 — 492 subscribers6 August 202614 August 2026
3 measurements spanning 8 days, net +249. 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 206–529 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 10:35492+249
7 Aug 2026, 02:32243no change
6 Aug 2026, 03:09243first reading

Engagement

18 posts held, back to 25 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
86.3%
avg views ÷ 492 subscribers
Avg views / post
425
18 posts measured
Reaction rate
0.348%
reactions ÷ views · ER floor
Posts in window
18
of 18 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 11 of 18 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 held18 (25 July 20266 August 2026)
Views total7,644
Reactions total22
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 02:32 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.

Reaction mix

22 reactions across 10 posts, in 7 distinct kinds. The most used accounts for 27.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
627.3%
👏418.2%
🔥418.2%
👍313.6%
😭29.09%
🙏29.09%
14.55%

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

Measured over the 18 most recent posts we hold, published 25 July 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, 15:49 UTC88 views2 reactionsread 7 August 2026
Video

Генеральный директор РУП «Черноморэнерго» Тимур Джинджолия прокомментировал ситуацию вокруг сбоев в энергосистеме и рассказал о ходе ликвидации неполадок на ИнгурГЭС После первых масштабных обесточиваний руководство ИнгурГЭС пригласило подрядные организации из Чехии и Германии, которые ранее занимались наладкой противоаварийной защиты и автоматики станции. Накануне иностранные специалисты проводили тестирование си

🔥1🙏1

6 Aug 2026, 08:03 UTC313 views1 reactionsread 7 August 2026
Photo

По итогам предыдущих аварий и прекращений подачи электроэнергии для проведения тестирования противоаварийной автоматики на Ингур ГЭС были привлечены подрядчики из Чехии и Германии. Проведение теста было необходимо для определения причин срабатывания противоаварийной автоматики. В результате вчерашнего тестирования сработала аварийная автоматика, в связи с чем генераторы Ингур ГЭС отключились от общей энергосистемы.

1

5 Aug 2026, 15:01 UTC239 viewsread 7 August 2026
Video

Специалисты РУП «Черноморэнерго» поделились ожиданиями от предстоящей программы повышения квалификации Заместитель главного инженера Галского филиала РУП «ЧерноморЭнерго»Георгий Гвилия подчеркнул значимость обучения для развития отрасли и подготовки управленческих кадров: «Рассчитываем усилить управленческий потенциал и перенять новый опыт. Это необходимо для преодоления кризиса, модернизации сетей и повышения кач

5 Aug 2026, 13:05 UTC228 viewsread 7 August 2026
Video

Саид Блабба: «Наша цель – построить эффективную систему управления для устойчивого развития энергосистемы» Сегодня на предприятии РУП «ЧерноморЭнерго» дан старт специальной рабочей сессии, посвященной повышению продуктивности внутренних регламентов и взаимодействия подразделений. В рамках встреч специалисты проводят детальный анализ текущей деятельности компании, формируют перспективные методики работы и вырабатыва

5 Aug 2026, 11:21 UTC≈3,860 views4 reactionsread 7 August 2026
Video

РУП «Черноморэнерго» приступило к реализации программы поэтапного обучения и повышения квалификации сотрудников Она направлена на подготовку специалистов к модернизации электросетевого комплекса Абхазии и внедрению современной системы учета электроэнергии. Первым этапом программы станет трехдневная стратегическая сессия «Архитектор сложносоставных систем: проектирование развития электроэнергетического комплекса Рес

👏21🙏1

4 Aug 2026, 15:45 UTC670 views2 reactionsread 7 August 2026
Video

РУП «Черноморэнерго» запускает программу поэтапного обучения и повышения квалификации кадров Образовательная программа направлена на развитие системы управления и подготовку специалистов к новым технологическим стандартам на фоне модернизации электросетей и внедрения всеобщего учета электроэнергии в Абхазии. Данная программа обучения будет способствовать формированию качественных кадров в энергетической отрасли,

1👏1

4 Aug 2026, 14:30 UTC142 views6 reactionsread 7 August 2026
Video

В Очамчыре продолжается модернизация энергосетей Завершив работы на пяти трансформаторных подстанциях в черте города, специалисты Очамчырского филиала РУП «ЧерноморЭнерго»приступили к обновлению следующего объекта – КТП 8 по улице Куйбышева. Старая линия электропередачи находилась в аварийном состоянии: имела многочисленные скрутки и сильный провис. В связи с этим энергетики демонтируют изношенные провода и заменяю

🔥3👍2👏1

4 Aug 2026, 09:59 UTC159 views2 reactionsread 7 August 2026
Video

Модернизация энергосетей в Гале: «Черноморэнерго» повышает надежность электроснабжения В рамках производственной программы в селе Хяцха Галского района ведется активная реконструкция изношенных сетей 0,4 кВ. Энергетики Галского филиала РУП Черноморэнерго проводят замену линий электропередачи на современный изолированный провод (СИП) и устанавливают надежные железобетонные опоры. Как сообщил заместитель главного ин

2

3 Aug 2026, 11:01 UTC161 views1 reactionsread 7 August 2026
Photo

Возгорание линии произошло из-за самовольного несанкционированного (безучетного) подключения абонентом электроприемников в обход прибора учета с использованием непригодного провода и кустарной скрутки, не рассчитанной на возникающую нагрузку. Из-за повышенной нагрузки при работе дополнительного силового кабеля в местах «скруток» произошел перегрев с последующим воспламенением изоляции, после чего огонь перешел на ко

1

3 Aug 2026, 08:56 UTC151 viewsread 7 August 2026
Photo

Вчера на ул.Назадзе (Старый поселок) города Сухум произошло возгорание линии электропередач. Рабочая бригада проводит необходимые восстановительные работы. Причины произошедшего уточняются профильными службами. По предварительной оценке, речь идет о локальном нарушении на участке линии, без масштабных последствий для энергосистемы. Ущерб жителям и расположенным рядом домам не нанесен. Последствия на линии будут у

1 Aug 2026, 13:38 UTC159 viewsread 7 August 2026
Forwarded from @mintransenergoabh

Профилактические работы пройдут сегодня на ВЛ-220 кВ «Очамчыра» В связи с этим, с 18:00 до 19:00 без света останутся: город Сухум, часть Сухумского района и часть Гудаутского и Гагрского районов.

30 Jul 2026, 14:44 UTC262 viewsread 7 August 2026

Филиал «СУЭС» РУП «Черноморэнерго» доводит до сведения жителей Нового района,что завтра 31 июля с 10:00 до 14:00 будет прекращена подача электроэнергии из-за расчистки высоковольтной линии электропередач 10 кВ. Просьба отнестись с пониманием. Филиал «СУЭС» приносит свои извинения за неудобства.

Showing the 12 most recent of 18 posts we hold for @chernomorenergo. 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 — 13,049 of 1,345,403entries 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

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.

Mentions

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

“Черноморэнерго” (@chernomorenergo), 492 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/chernomorenergo.

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.