Telegram RegisterThe public register of Telegram
Telegram profile photo for Світло Світловодських ЕМ

Channel

Світло Світловодських ЕМ

@SvitloSvitlovodskohoRaionu

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

10,417subscribers

-104 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1001595411604
TypeChannel
Username@SvitloSvitlovodskohoRaionu
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live19 September 2026
Measurements held31
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/SvitloSvitlovodskohoRaionu

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 93% 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@SvitloSvitlovodskohoRaionu/1650 · this entry29 Jun 2026, 06:27 UTC1.00under a minute
@SvitloNovoarhangelsk_REM/167329 Jun 2026, 06:32 UTC@SvitloSvitlovodskohoRaionu/1651 · this entry29 Jun 2026, 06:32 UTC1.00under a minute
@SvitloNovoarhangelsk_REM/167529 Jun 2026, 14:14 UTC@SvitloSvitlovodskohoRaionu/1653 · this entry29 Jun 2026, 14:15 UTC1.00under a minute
@SvitloNovoarhangelsk_REM/167830 Jun 2026, 13:28 UTC@SvitloSvitlovodskohoRaionu/1656 · this entry30 Jun 2026, 13:28 UTC1.00under a minute
@SvitloNovoarhangelsk_REM/168030 Jun 2026, 19:31 UTC@SvitloSvitlovodskohoRaionu/1658 · this entry30 Jun 2026, 19:31 UTC1.00under a minute
@SvitloNovoarhangelsk_REM/16811 Jul 2026, 12:58 UTC@SvitloSvitlovodskohoRaionu/1659 · 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)
@SvitloOleksandriyskohoRaionu17 (8/8 hand-verifiable sample passed)1.00under a minute@SvitloOleksandriyskohoRaionu (10–7)
@SvitloHolovanivskohoRayonu17 (8/8 hand-verifiable sample passed)1.00under a minute@SvitloHolovanivskohoRayonu (13–4)
@SvitloKropyvnytskyiMisto17 (8/8 hand-verifiable sample passed)1.00under a minute@SvitloKropyvnytskyiMisto (12–5)

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 47 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 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

10,41710,52310,4708 August 2026 — 10,521 subscribers8 August 2026 — 10,523 subscribers9 August 2026 — 10,519 subscribers10 August 2026 — 10,520 subscribers11 August 2026 — 10,522 subscribers12 August 2026 — 10,520 subscribers14 August 2026 — 10,514 subscribers15 August 2026 — 10,506 subscribers17 August 2026 — 10,505 subscribers18 August 2026 — 10,501 subscribers19 August 2026 — 10,499 subscribers20 August 2026 — 10,497 subscribers21 August 2026 — 10,495 subscribers22 August 2026 — 10,491 subscribers24 August 2026 — 10,489 subscribers25 August 2026 — 10,484 subscribers27 August 2026 — 10,483 subscribers28 August 2026 — 10,478 subscribers29 August 2026 — 10,475 subscribers30 August 2026 — 10,473 subscribers31 August 2026 — 10,467 subscribers1 September 2026 — 10,461 subscribers2 September 2026 — 10,460 subscribers3 September 2026 — 10,456 subscribers5 September 2026 — 10,452 subscribers8 September 2026 — 10,447 subscribers11 September 2026 — 10,441 subscribers13 September 2026 — 10,433 subscribers15 September 2026 — 10,428 subscribers17 September 2026 — 10,423 subscribers19 September 2026 — 10,417 subscribers8 August 202619 September 2026
31 measurements spanning 43 days, net -104. 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 10,401–10,539 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 31
Measured (UTC)SubscribersChange
19 Sept 2026, 17:0110,417-6
17 Sept 2026, 03:4110,423-5
15 Sept 2026, 06:5510,428-5
13 Sept 2026, 14:3610,433-8
11 Sept 2026, 15:5510,441-6
8 Sept 2026, 22:3810,447-5
5 Sept 2026, 12:1610,452-4
3 Sept 2026, 12:2010,456-4
2 Sept 2026, 04:0410,460-1
1 Sept 2026, 06:1710,461-6
31 Aug 2026, 07:0410,467-6
30 Aug 2026, 06:1610,473-2
29 Aug 2026, 09:1410,475-3
28 Aug 2026, 08:0310,478-5
27 Aug 2026, 07:4810,483-1
25 Aug 2026, 11:5710,484-5
24 Aug 2026, 14:3410,489-2
22 Aug 2026, 21:5410,491-4
21 Aug 2026, 10:2610,495-2
20 Aug 2026, 11:4810,497first reading

Engagement

21 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 35 pages of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 21 posts for this entry, the most recent from 24 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

1,746 reactions across 21 posts, in 12 distinct kinds. The most used accounts for 44.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤77544.4%
🤬35520.3%
😢23213.3%
👍19010.9%
👎573.26%
😁452.58%
😱372.12%
🥰271.55%
🤔150.859%
🎉80.458%
🤯30.172%
🔥20.115%

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 21 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 1,746 reactions 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 22 May 2026 to 24 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

24 Aug 2026, 07:06 UTC≈4,440 views163 reactionsread 29 August 2026
Photo

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

❤129👍22😁7🥰3👎1😢1

6 Aug 2026, 14:34 UTC≈11,200 views75 reactionsread 29 August 2026
Photo

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

❤34😢18👍10😁7🥰6

28 Jul 2026, 13:27 UTC≈14,300 views85 reactionsread 29 August 2026
Photo

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

❤49👍15😁10🤬5😢5👎1

28 Jul 2026, 05:58 UTC≈12,500 views38 reactionsread 29 August 2026
Photo

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

❤15😢12👍11

15 Jul 2026, 06:08 UTC≈14,900 views110 reactionsread 29 August 2026
Photo

Photo, posted without a caption

❤76👍17😁9😢6🎉1👎1

14 Jul 2026, 11:22 UTC≈12,500 views54 reactionsread 29 August 2026
Photo

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

❤24😢18👍6😱5🔥1

1 Jul 2026, 14:25 UTC≈15,500 views93 reactionsread 29 August 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: -

🤬40❤35👍5😢5🤔4👎3😁1

1 Jul 2026, 12:58 UTC≈12,700 views72 reactionsread 29 August 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: -

❤39🤬21👍4👎2😁2😢2🔥1🤔1

30 Jun 2026, 19:31 UTC≈13,800 views83 reactionsread 29 August 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

❤39🤬28😢9🥰5👎2

30 Jun 2026, 15:35 UTC≈8,950 views51 reactionsread 29 August 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: -

❤21🤬16🥰10😢3👎1

30 Jun 2026, 13:28 UTC≈10,600 views64 reactionsread 29 August 2026
Photo

⚡ Зміни на 16:28 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: 19-20 Черга 5.1: - Черга 5.2: - Черга 6.1: - Черга 6.2: -

❤38🤬18😢6🤔2

30 Jun 2026, 06:12 UTC≈10,200 views118 reactionsread 29 August 2026
Photo

⚠ Попередній прогноз по застосуванню графіків погодиних відключень (ГПВ) на СЕРЕДУ, 01 липня 2026 року. Прогнозовано за розпорядженням НЕК "Укренерго" 01.07.2026 з 15:00 до 22:00 дія наступного графіка погодинних відключень (ГПВ): Черга 1.1: 20-22 Черга 1.2: 20-22 Черга 2.1: - Черга 2.2: - Черга 3.1: 16-18 Черга 3.2: 16-18 Черга 4.1: 15-16 Черга 4.2: 15-16 Черга 5.1: - Черга 5.2: 18-20 Черга 6.1: 18-20 Черга 6.2: …

🤬59😢29❤22👍4👎2😁2

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

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.

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

“Світло Світловодських ЕМ” (@SvitloSvitlovodskohoRaionu), 10,417 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/SvitloSvitlovodskohoRaionu.

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.