Telegram RegisterThe public register of Telegram
Telegram profile photo for Світло Кропивницький місто

Channel

Світло Кропивницький місто

@SvitloKropyvnytskyiMisto

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

90,820subscribers

+5,381 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-1001338051898
TypeChannel
Username@SvitloKropyvnytskyiMisto
Created5 January 2023 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded7 August 2026
Last confirmed live12 November 2026
Measurements held65
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/SvitloKropyvnytskyiMisto

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 96% 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.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 7 other registered channels. This entry also sits inside a group of 7 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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
@SvitloKropyvnytskyiMisto/1696 · this entry29 Jun 2026, 06:27 UTC@SvitloOleksandriyskohoRaionu/168629 Jun 2026, 06:27 UTC1.00under a minute
@SvitloKropyvnytskyiMisto/1697 · this entry29 Jun 2026, 06:32 UTC@SvitloOleksandriyskohoRaionu/168729 Jun 2026, 06:32 UTC1.00under a minute
@SvitloKropyvnytskyiMisto/1705 · this entry1 Jul 2026, 12:58 UTC@SvitloOleksandriyskohoRaionu/16951 Jul 2026, 12:58 UTC1.00under a minute
@SvitloKropyvnytskyiMisto/1714 · this entry17 Sept 2026, 11:58 UTC@SvitloOleksandriyskohoRaionu/170417 Sept 2026, 11:59 UTC1.00under a minute
@SvitloKropyvnytskyiMisto/1719 · this entry17 Oct 2026, 07:00 UTC@SvitloOleksandriyskohoRaionu/170917 Oct 2026, 07:00 UTC1.00under a minute
@SvitloKropyvnytskyiMisto/1730 · this entry26 Oct 2026, 13:35 UTC@SvitloOleksandriyskohoRaionu/172026 Oct 2026, 13:35 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@SvitloOleksandriyskohoRaionu36 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (29–7)
@SvitloHolovanivskohoRayonu36 (8/8 hand-verifiable sample passed)1.00under a minute@SvitloHolovanivskohoRayonu (27–9)
@SvitloKropyvnytskohoRaionu36 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (29–7)
@SvitloSvitlovodskohoRaionu36 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (29–7)
@znamelektro33 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (18–15)
@SvitloNovoarhangelsk_REM26 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (21–5)
@hyevuy_alex7 (7/7 hand-verifiable sample passed)1.004 minutesthis entry (7–0)

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. 29 of the 68 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 121 comparable posts for this entry, running 27 May 2026 to 15 November 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).

Of the group of 7 channels, the one whose matching posts we hold earliest is @SvitloHolovanivskohoRayonu. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_mutual · clone_source, last confirmed 16 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.

Channels linked by matching posts

This channel is in a group of 7 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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

84,06590,82087,442.57 August 202612 November 2026
65 measurements spanning 97 days, net +5,381. 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 83,052–91,833 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)SubscribersChange
12 Nov 2026, 21:5090,820+369
10 Nov 2026, 15:2190,451+241
9 Nov 2026, 02:1990,210+325
7 Nov 2026, 19:0789,885+121
6 Nov 2026, 19:4589,764+254
5 Nov 2026, 20:3689,510+394
4 Nov 2026, 23:4089,116+928
4 Nov 2026, 01:3888,188+1,411
2 Nov 2026, 23:0686,777+14
2 Nov 2026, 02:3686,763-33
1 Nov 2026, 00:3086,796-2
31 Oct 2026, 02:1886,798-33
30 Oct 2026, 04:0886,831-23
29 Oct 2026, 05:3886,854-14
28 Oct 2026, 03:3986,868+13
27 Oct 2026, 00:0186,855+228
26 Oct 2026, 01:3886,627+22
24 Oct 2026, 23:1186,605-16
23 Oct 2026, 22:2786,621-11
23 Oct 2026, 00:4786,632first reading

Engagement

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

ERR · 30 days
67.7%
avg views ÷ 90,820 subscribers
Avg views / post
61,500
99 posts measured
Reaction rate
0.977%
reactions ÷ views · ER floor
Posts in window
99
of 130 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 15 November 2026
Posts held130 (22 May 2026 – 15 November 2026)
Views total6,084,600
Reactions total59,440
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Nov 2026, 07:14 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
843
Videos
8
Links
243

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

Reaction mix

81,210 reactions across 130 posts, in 13 distinct kinds. The most used accounts for 42.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤬34,58942.6%
❤30,12237.1%
👍5,2936.52%
👎2,5313.12%
😢2,1872.69%
🤔1,6742.06%
😁1,1871.46%
😱8951.10%
🤯8040.99%
🔥7360.906%
🎉6030.743%
🥰3420.421%
👏2470.304%

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

Measured over the 130 most recent posts we hold, published 22 May 2026 to 15 November 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

Telegram’s own ‘edited’ marker: 0 of 99 posts held from the last 30 days (0%) 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).

15 Nov 2026, 23:36 UTC≈38,100 views460 reactionsread 16 November 2026
Photo

На 16.11.2026 за розпорядженням НЕК "Укренерго" внесено зміни до графіка погодинних відключень (ГПВ) станом на 01:36 16.11.2026: Черга 1.1: 12-14, 16-18 Черга 1.2: 12-14, 16-18 Черга 2.1: 00-01:30, 08-10, 16-18, 20-22 Черга 2.2: 08-10, 16-18, 20-22 Черга 3.1: 08-10, 12-14, 20-22 Черга 3.2: 00-01:30, 08-10, 12-14, 20-22 Черга 4.1: 10-12, 14-16, 18-20 Черга 4.2: 10-12, 14-16, 18-20 Черга 5.1: 07-08, 10-12, 18-20, 22-…

🤬227❤170👎19😢19🤔11👍10🔥3🤯1

15 Nov 2026, 20:41 UTC≈41,000 views288 reactionsread 16 November 2026
Photo

На 15.11.2026 за розпорядженням НЕК "Укренерго" внесено зміни до графіка погодинних відключень (ГПВ) станом на 22:41 15.11.2026: Черга 4.1: 22-24 Черга 4.2: 22-24 Черга 5.1: 22-23 Черга 5.2: 22-23 Черга 6.1: 22-24 Черга 6.2: 22-24

❤145🤬101🤔17👍14👎6🎉3👏1🔥1

15 Nov 2026, 18:50 UTC≈44,500 views583 reactionsread 16 November 2026
Photo

На 15.11.2026 за розпорядженням НЕК "Укренерго" внесено зміни до графіка погодинних відключень (ГПВ) станом на 20:50 15.11.2026: Черга 4.1: 22-24 Черга 4.2: 22-24 Черга 5.1: 22-24 Черга 5.2: 22-24 Черга 6.1: 22-24 Черга 6.2: 22-24

🤬331❤128👎41😁24🤔17👍16😢14🔥5

15 Nov 2026, 18:41 UTC≈44,500 views472 reactionsread 16 November 2026
Photo

16.11.2026 за розпорядженням НЕК "Укренерго" буде діяти наступний графік погодинних відключень (ГПВ): Черга 1.1: 04-06, 12-14, 16-18 Черга 1.2: 04-06, 12-14, 16-18 Черга 2.1: 00-02, 08-10, 16-18, 20-22 Черга 2.2: 08-10, 16-18, 20-22 Черга 3.1: 08-10, 12-14, 20-22 Черга 3.2: 00-02, 08-10, 12-14, 20-22 Черга 4.1: 02-04, 10-12, 14-16, 18-20 Черга 4.2: 02-04, 10-12, 14-16, 18-20 Черга 5.1: 06-08, 10-12, 18-20, 22-24 Чер…

🤬275❤114👎20😢19🤔14👍13😱7🥰4

15 Nov 2026, 18:24 UTC≈43,200 views701 reactionsread 16 November 2026

15.11.2026 за наказом НЕК "Укренерго" ГПВ та ГОП скасовано до окремого розпорядження.

❤469🎉107👍94😁21👏6👎2🤔2

15 Nov 2026, 15:50 UTC≈47,100 views579 reactionsread 16 November 2026
Photo

На 15.11.2026 за розпорядженням НЕК "Укренерго" внесено зміни до графіка погодинних відключень (ГПВ) станом на 17:49 15.11.2026: Черга 2.1: 20-22 Черга 2.2: 20-22 Черга 3.1: 20-22 Черга 3.2: 20-22 Черга 4.2: 22-24 Черга 6.1: 22-24 Черга 6.2: 22-24

🔥179❤174🤬111👍47👎15🤔14😁14🥰9

15 Nov 2026, 13:45 UTC≈49,200 views432 reactionsread 16 November 2026
Photo

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

❤219🤬143👍40🤔19😁5🔥3👏2😢1

15 Nov 2026, 06:29 UTC≈51,800 views554 reactionsread 16 November 2026
Photo

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

❤358🤬99👍62🤔22🎉9👎3🤯1

15 Nov 2026, 05:41 UTC≈51,900 views246 reactionsread 16 November 2026
Photo

На 15.11.2026 за розпорядженням НЕК "Укренерго" внесено зміни до графіка погодинних відключень (ГПВ) станом на 07:41 15.11.2026: Черга 1.1: 16-18 Черга 1.2: 16-18 Черга 2.1: 12-14, 16-18, 20-22 Черга 2.2: 09-10, 16-18, 20-22 Черга 3.1: 09-10, 12-14, 20-22 Черга 3.2: 09-10, 12-14, 20-22 Черга 4.1: 10-12, 18-20 Черга 4.2: 10-12, 18-20, 22-24 Черга 5.1: 10-12, 18-20 Черга 5.2: 14-16, 18-20 Черга 6.1: 14-16, 22-24 Черг…

🤬116❤91👍18🤔11👎8🔥1😁1

14 Nov 2026, 18:51 UTC≈52,400 views567 reactionsread 16 November 2026
Photo

15.11.2026 за розпорядженням НЕК "Укренерго" буде діяти наступний графік погодинних відключень (ГПВ): Черга 1.1: 16-18 Черга 1.2: 16-18 Черга 2.1: 12-14, 16-18, 20-22 Черга 2.2: 08-10, 16-18, 20-22 Черга 3.1: 08-10, 12-14, 20-22 Черга 3.2: 08-10, 12-14, 20-22 Черга 4.1: 10-12, 18-20 Черга 4.2: 10-12, 18-20, 22-24 Черга 5.1: 10-12, 18-20 Черга 5.2: 14-16, 18-20 Черга 6.1: 14-16, 22-24 Черга 6.2: 14-16, 22-24

❤270🤬191🤔34👍26👎13😢13👏9😁5

14 Nov 2026, 16:25 UTC≈51,900 views588 reactionsread 16 November 2026
Photo

На 14.11.2026 за розпорядженням НЕК "Укренерго" внесено зміни до графіка погодинних відключень (ГПВ) станом на 18:25 14.11.2026: Черга 1.1: 18-18:30 Черга 1.2: 18-18:30 Черга 3.1: 18-18:30 Черга 3.2: 18-18:30 Черга 4.1: 00-00:30, 16-18 Черга 4.2: 00-00:30, 16-18 Черга 5.1: 00-00:30, 16-18 Черга 5.2: 16-18

❤389👍85🤬54🤔22🤯17🥰8👏7🔥4

14 Nov 2026, 13:01 UTC≈50,800 views483 reactionsread 16 November 2026
Photo

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

🤬272❤134👍33😢14👎12🤔12😁4👏2

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

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

Труха⚡️Кропивницький
@truexakropivnicky · 204,259
#1
🇺🇦 Андрій Райкович/ Кіровоградська ОДА (ОВА)
@kirovogradskaODA · 64,589
#2
kirovograd_official🇺🇦Кропивницький
@kirovograd_official · 78,183
#3
ХК | Кропивницький 🇺🇦
@xk_krop · 40,034
#4
Суспільне Кропивницький
@suspilnekropyvnytskyi · 47,133
#5
KROP.POLICE | КРОПИВНИЦЬКИЙ 🔍 НОВИНИ
@kroppolice2 · 10,503
#6
Кіровоградська Правда
@k_pravda · 50,019
#7
КП "Електротранс"
@kp_elektrotrans_new · 3,684
#8
Патрульна поліція Кіровоградської області
@kroppolice · 1,346
#9
Тусовка Кропивницький
@tusovkakrop · 1,180
#10
Без купюр Кропивницький 🇺🇦
@kypurnet · 1,499
#11
Ти в курсі? Кропивницький
@news_kropyvnytskyy · 2,950
#12
❗️СИРЕНА КІРОВОГРАДЩИНА🔊
@surenakrop · 52,652
#13
Кропивницький Ваньок
@krop_vanek · 89,510
#14
Лачен пише
@lachentyt · 1,576,100
#15
Труха⚡️Україна
@truexanewsua · 3,165,061
#16
Повітряні Сили ЗС України / Air Force of the Armed Forces of Ukraine
@kpszsu · 938,428
#17
Карта повітряних тривог 🇺🇦
@alarmua · 941,284
#18
monitor
@war_monitor · 958,023
#19
CBN|Кіровоградщина
@cbnua · 8,935
#20
Карта повітряних тривог ‼️ Вибухи ‼️ Ракети ‼️
@povitryanatrivogaaa · 728,432
#21
Кіровоградська ОДА/ОВА
@kirovohradskaODA · 5,316
#22
Обмін валют Кропивницький «X-Change»💶
@xchange_kropyvnytskyi · 5,646
#23
🇺🇦 ЛАВРУСЬ 🇺🇦
@A_Lavrus · 2,490
#24
Кропивницький Джокер
@krop_joker · 3,003
#25
Україна Online: Новини | Політика
@UaOnlii · 1,536,697
#26
Куди піти? | Кропивницький
@kudy_pity_krop · 2,391
#27
Gre4ka.info
@gre4kainfo · 3,077
#28
Реальна Війна | Україна | Новини
@voynareal · 1,541,547
#29
Кропивницький КИТ Group
@obmenka_kropyvnytskyi · 2,023
#30
УС: Україна, новини, політика, війна
@u_now · 1,403,118
#31
Кропивницький Обмін валют
@money24kr · 526
#32
ТСН новини / ТСН.ua
@tch_channel · 729,418
#33
Onix-Systems
@onixkrua · 409
#34
Затишно space Кропивницький | Схід SOS
@zatyshnoKropyvnytsky · 1,110
#35
Доступ Медіа: Кропивницький
@dostup_media · 2,607
#36
Кіровоградська обласна прокуратура
@kirgpua · 1,390
#37
Український Наступ | #УкрТг ∆
@ukrnastup · 132,804
#38
✙DeepState✙🇺🇦
@deepstateua · 750,849
#39
Ukraine NOW
@UkraineNow · 404,377
#40
Укренерго
@Ukrenergo · 100,021
#41
Фунтик
@funtik_kr · 1,407
#42
Тривога України | Радар
@kiev_nebo · 539,280
#43
Лебидло
@lebigaa · 417,203
#44
Гончаренко Центр Кропивницький
@GoncharenkoCentreKrop · 3,183
#45
Студентська рада ЦНТУ
@studprostirCNTU · 389
#46
Тотальна Зрада
@totallzrada · 265,783
#47
Ринда моніторить
@kudy_letyt · 159,456
#48
Vitalii KIM | Official
@VitaliiKimOfficial · 250,936
#49
Чому тривога | Радар
@raketa_trevoga · 472,563
#50
Кіровоградський обласний центр з гідрометеорології | Погода | Прогноз | КРОПИВНИЦЬКИЙ | КІРОВОГРАДЩИНА
@kircgm · 1,407
#51
Оперативний ЗСУ
@operativnoZSU · 359,722
#52
INSIDER UA | Україна | Новини
@insiderukr · 2,141,667
#53
Бавовна
@ukrbavovna · 801,855
#54
STERNENKO
@ssternenko · 879,724
#55
Всевидящее ОКО (миллион подписчиков)
@oko_ua · 1,751
#56
Алексей Шевцов
@jolybells · 357,346
#57
Hebi Hebi Agency
@hebihebi_agency · 12,082
#58
Вестник Шевцова
@jolynews · 206,371
#59
Куди летить? | Тривога
@radar_raketaa · 490,712
#60
Скринька Пандори
@pandoras_box_ua · 157,815
#61
што блін
@kati0sik1 · 108
#62
Бро скинув мем
@bromeeems · 310,153
#63
Новини ЦДУ
@cuspu · 722
#64
✙ 🔼Вертикаль
@vert2026 · 113,508
#65
Новинач
@novinach · 142,284
#66
Говорять Снайпер ꑭ
@stanislav_osman · 287,836
#67
Zelenskiy / Official
@v_zelenskiy_official · 665,469
#68
Канал Ростіка
@crypto_rostik · 116,753
#69
Батальйон Монако
@batalionmonako · 712
#70

Read from Telegram’s recommendation API, most recently 18 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

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.

Труха⚡️Кропивницький
@truexakropivnicky · 204,259
Telegram ranks this channel #1 of 76 here — alongside 75 others — read 12 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list 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 12 November 2026 — this entry's latest reading, not the date you are reading this.

“Світло Кропивницький місто” (@SvitloKropyvnytskyiMisto), 90,820 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/SvitloKropyvnytskyiMisto.

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.