Telegram RegisterThe public register of Telegram
Telegram profile photo for Світло Олександрійщини

Channel

Світло Олександрійщини

@SvitloOleksandriyskohoRaionu

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

35,008subscribers

-487 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001875739370
TypeChannel
Username@SvitloOleksandriyskohoRaionu
Created3 January 2023 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded7 August 2026
Last confirmed live27 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 27 September 2026
On Telegramt.me/SvitloOleksandriyskohoRaionu

Topic

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 98% 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 4 other registered channels. 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 (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@SvitloNovoarhangelsk_REM/167229 Jun 2026, 06:27 UTC@SvitloOleksandriyskohoRaionu/1686 · this entry29 Jun 2026, 06:27 UTC1.00under a minute
@SvitloNovoarhangelsk_REM/167329 Jun 2026, 06:32 UTC@SvitloOleksandriyskohoRaionu/1687 · this entry29 Jun 2026, 06:32 UTC1.00under a minute
@SvitloNovoarhangelsk_REM/167529 Jun 2026, 14:14 UTC@SvitloOleksandriyskohoRaionu/1689 · this entry29 Jun 2026, 14:15 UTC1.00under a minute
@SvitloNovoarhangelsk_REM/167830 Jun 2026, 13:28 UTC@SvitloOleksandriyskohoRaionu/1692 · this entry30 Jun 2026, 13:28 UTC1.00under a minute
@SvitloNovoarhangelsk_REM/168030 Jun 2026, 19:31 UTC@SvitloOleksandriyskohoRaionu/1694 · this entry30 Jun 2026, 19:31 UTC1.00under a minute
@SvitloNovoarhangelsk_REM/16811 Jul 2026, 12:58 UTC@SvitloOleksandriyskohoRaionu/1695 · this entry1 Jul 2026, 12:58 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@SvitloNovoarhangelsk_REM17 (8/8 hand-verifiable sample passed)1.00under a minute@SvitloNovoarhangelsk_REM (12–5)
@SvitloHolovanivskohoRayonu17 (8/8 hand-verifiable sample passed)1.00under a minute@SvitloHolovanivskohoRayonu (13–4)
@SvitloSvitlovodskohoRaionu17 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (10–7)
@SvitloKropyvnytskyiMisto17 (8/8 hand-verifiable sample passed)1.00under a minute@SvitloKropyvnytskyiMisto (13–4)

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. 1 of the 45 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 18 comparable posts for this entry, running 27 May 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 5, the earliest publisher we hold is @SvitloHolovanivskohoRayonu. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_mutual, last confirmed 8 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 4 other registered channels, 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

35,00835,49535,251.57 August 2026 — 35,495 subscribers7 August 2026 — 35,495 subscribers7 August 2026 — 35,493 subscribers8 August 2026 — 35,488 subscribers9 August 2026 — 35,475 subscribers10 August 2026 — 35,463 subscribers11 August 2026 — 35,448 subscribers13 August 2026 — 35,442 subscribers14 August 2026 — 35,432 subscribers15 August 2026 — 35,412 subscribers16 August 2026 — 35,401 subscribers18 August 2026 — 35,384 subscribers19 August 2026 — 35,376 subscribers19 August 2026 — 35,371 subscribers21 August 2026 — 35,355 subscribers22 August 2026 — 35,347 subscribers24 August 2026 — 35,328 subscribers25 August 2026 — 35,300 subscribers26 August 2026 — 35,285 subscribers27 August 2026 — 35,269 subscribers28 August 2026 — 35,265 subscribers29 August 2026 — 35,243 subscribers30 August 2026 — 35,232 subscribers31 August 2026 — 35,210 subscribers1 September 2026 — 35,204 subscribers2 September 2026 — 35,192 subscribers4 September 2026 — 35,181 subscribers6 September 2026 — 35,164 subscribers10 September 2026 — 35,146 subscribers12 September 2026 — 35,116 subscribers14 September 2026 — 35,104 subscribers15 September 2026 — 35,094 subscribers17 September 2026 — 35,085 subscribers27 September 2026 — 35,008 subscribers7 August 202627 September 2026
34 measurements spanning 51 days, net -487. 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 34,935–35,568 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
27 Sept 2026, 06:3735,008-77
17 Sept 2026, 14:1635,085-9
15 Sept 2026, 13:1835,094-10
14 Sept 2026, 00:0035,104-12
12 Sept 2026, 08:5635,116-30
10 Sept 2026, 03:2035,146-18
6 Sept 2026, 20:2135,164-17
4 Sept 2026, 08:2035,181-11
2 Sept 2026, 20:3835,192-12
1 Sept 2026, 19:0435,204-6
31 Aug 2026, 18:3535,210-22
30 Aug 2026, 15:5435,232-11
29 Aug 2026, 13:2835,243-22
28 Aug 2026, 10:2435,265-4
27 Aug 2026, 10:1635,269-16
26 Aug 2026, 08:0335,285-15
25 Aug 2026, 08:2235,300-28
24 Aug 2026, 04:5735,328-19
22 Aug 2026, 10:5735,347-8
21 Aug 2026, 03:0835,355first reading

Engagement

23 posts held, back to 22 May 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 86 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
96.0%
avg views ÷ 35,008 subscribers
Avg views / post
33,600
2 posts measured
Reaction rate
0.552%
reactions ÷ views · ER floor
Posts in window
2
of 23 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 17 September 2026
Posts held23 (22 May 2026 – 17 September 2026)
Views total67,200
Reactions total371
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken27 Sept 2026, 05:51 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

6,982 reactions across 23 posts, in 13 distinct kinds. The most used accounts for 48.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤3,38148.4%
🤬2,02929.1%
👍5297.58%
👎2233.19%
😢1922.75%
😁1502.15%
😱1171.68%
🤔981.40%
🤯670.96%
🎉660.945%
🔥470.673%
🥰440.63%
👏390.559%

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

Measured over the 23 most recent posts we hold, published 22 May 2026 to 17 September 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

17 Sept 2026, 11:59 UTC≈24,100 views212 reactionsread 27 September 2026

Шановні споживачі! З метою покращення якості роботи та підвищення рівня обслуговування кол-центру ПрАТ "Кіровоградобленерго", повідомляємо, що з 21 вересня 2026 року в тестовому режимі розпочинає роботу новий номер телефону кол-центру — 0-800-300-552. Просимо споживачів використовувати зазначений номер для звернень до кол-центру ПрАТ "Кіровоградобленерго" та врахувати цю інформацію під час подальшої комунікації з Т…

👍110❤74🤬8🎉7🤔6👏4😁2👎1

31 Aug 2026, 06:06 UTC≈43,100 views159 reactionsread 27 September 2026
Photo

Шановні споживачі! Для коректного нарахування спожитої електроенергії, споживачу необхідно щомісяця фіксувати фактичні показники лічильника в період: останні 2 дні місяця (30-31) по 3 число наступного місяця та передати через будь-який зручний для вас онлайн сервіс: 1.Сайт ПрАТ «Кіровоградобленерго» www.kiroe.com.ua, функція «Передача показників лічильника». 2. Кол-центр: 067-521-15-70, 050-488-80-63, 0-800-501-148…

❤118👍18🤬10😱5👎4😁3🔥1

24 Aug 2026, 07:06 UTC≈49,600 views652 reactionsread 27 September 2026
Photo

Вітаємо з Днем Незалежності України! Нехай цей день об’єднує нас навколо найважливіших цінностей — свободи, гідності, єдності та любові до рідної землі! Бажаємо нашій державі миру, сили та процвітання, а кожному з нас — впевненості у завтрашньому дні, міцного здоров’я, добробуту й родинного тепла! Україна вистоїть, переможе та неодмінно стане країною, якою ми всі будемо пишатися! Колектив ПрАТ "Кіровоградобленерг…

❤505👍79😁20👎15🥰15🤬8🤯6🔥2

6 Aug 2026, 14:34 UTC≈55,100 views211 reactionsread 27 September 2026
Photo

УВАГА! Штормове попередження! За даними Кіровоградського обласного центру з гідрометеорології, до кінця дня 06 серпня в західній частині Кіровоградської області очікуються гроза, місцями пориви вітру з 15 до 20 м/с. ПрАТ "Кіровоградобленерго" сповіщає, що внаслідок несприятливих погодних умов на території нашої області можуть статися обриви проводів ліній електропередач. ПОПЕРЕДЖАЄМО! Обірвані проводи, що лежать н…

❤125🤔36😱15👍14🎉7👎7🤬7

28 Jul 2026, 13:27 UTC≈52,900 views280 reactionsread 27 September 2026
Photo

Увага! Фіксується масова розсилка на електронні адреси споживачів фейкових листів, які маскують під офіційні повідомлення від Міненерго й Державної інспекції енергетичного нагляду. У повідомленнях повідомляється, що за їхніми адресами нібито виявлено «критичну розбіжність між розподіленою та облікованою потужністю». Як повідомили в Міністерстві енергетики України, ці повідомлення є підробкою. Міненерго не має повнов…

❤169😱53👍27🤬16👎8🤯3🔥2😢2

28 Jul 2026, 05:58 UTC≈39,600 views148 reactionsread 27 September 2026
Photo

УВАГА! Штормове попередження! За даними Кіровоградського обласного центру з гідрометеорології, протягом доби 28 липня по м. Кропивницькому та області очікуються гроза, місцями пориви вітру з 15 до 20 м/с. ПрАТ "Кіровоградобленерго" сповіщає, що внаслідок несприятливих погодних умов на території нашої області можуть статися обриви проводів ліній електропередач. ПОПЕРЕДЖАЄМО! Обірвані проводи, що лежать на землі, ви…

❤108👍15😱15🤬6👎4

15 Jul 2026, 06:08 UTC≈55,000 views430 reactionsread 27 September 2026
Photo

Photo, posted without a caption

❤330🤬27👍25😁16😢8🎉6👏5🤔4

14 Jul 2026, 11:22 UTC≈54,900 views204 reactionsread 27 September 2026
Photo

УВАГА! Штормове попередження! За даними Кіровоградського обласного центру з гідрометеорології, протягом доби 14 липня по м. Кропивницькому та області очікуються гроза, град та пориви вітру до 6 - 19 м/с, місцями шквал 15 20 м/с. ПрАТ "Кіровоградобленерго" сповіщає, що внаслідок несприятливих погодних умов на території нашої області можуть статися обриви проводів ліній електропередач. ПОПЕРЕДЖАЄМО! Обірвані проводи…

❤130👍32🤯12🤬10😁8🤔5😢4👎2

1 Jul 2026, 14:25 UTC≈62,300 views347 reactionsread 27 September 2026
Photo

⚡ Зміни на 17:25 01.07.2026 до графіка погодинних відключень За розпорядженням НЕК "Укренерго" 01.07.2026 внесено зміни до графіка погодинних відключень (ГПВ): Черга 1.1: - Черга 1.2: 20-22 Черга 2.1: - Черга 2.2: - Черга 3.1: - Черга 3.2: - Черга 4.1: - Черга 4.2: - Черга 5.1: - Черга 5.2: - Черга 6.1: 19-20 Черга 6.2: -

❤160🤬125👍25👎9🎉7😁7👏6😢4

1 Jul 2026, 12:58 UTC≈51,900 views229 reactionsread 27 September 2026
Photo

⚡ Зміни на 15:56 01.07.2026 до графіка погодинних відключень За розпорядженням НЕК "Укренерго" 01.07.2026 внесено зміни до графіка погодинних відключень (ГПВ): Черга 1.1: - Черга 1.2: 20-22 Черга 2.1: - Черга 2.2: - Черга 3.1: - Черга 3.2: - Черга 4.1: - Черга 4.2: - Черга 5.1: - Черга 5.2: - Черга 6.1: 18-20 Черга 6.2: -

❤131🤬57👍14🎉7👎7🥰4😁4😢3

30 Jun 2026, 19:31 UTC≈47,500 views311 reactionsread 27 September 2026
Photo

⚡ Зміни на 22:31 01.07.2026 до графіка погодинних відключень За розпорядженням НЕК "Укренерго" 01.07.2026 внесено зміни до графіка погодинних відключень (ГПВ): Черга 1.1: 20-22 Черга 1.2: 20-22 Черга 2.1: - Черга 2.2: - Черга 3.1: 17-18 Черга 3.2: 17-18 Черга 4.1: - Черга 4.2: - Черга 5.1: - Черга 5.2: - Черга 6.1: 18-20 Черга 6.2: 18-20

🤬136❤129😁15😢10👎6👍5🔥5🥰5

30 Jun 2026, 15:35 UTC≈34,600 views243 reactionsread 27 September 2026
Photo

⚡ Зміни на 18:34 30.06.2026 до графіка погодинних відключень За розпорядженням НЕК "Укренерго" 30.06.2026 внесено зміни до графіка погодинних відключень (ГПВ): Черга 1.1: - Черга 1.2: - Черга 2.1: - Черга 2.2: 20-22 Черга 3.1: - Черга 3.2: - Черга 4.1: 18-20 Черга 4.2: - Черга 5.1: - Черга 5.2: - Черга 6.1: - Черга 6.2: -

🤬114❤93👍14👎6😁6🤔3🔥2🤯2

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

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.

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

“Світло Олександрійщини” (@SvitloOleksandriyskohoRaionu), 35,008 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/SvitloOleksandriyskohoRaionu.

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.