Telegram RegisterThe public register of Telegram
Telegram profile photo for Світло💡Київ

Channel

Світло💡Київ

@svitloo_kyiv

On this record: Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

3,849subscribers

-19 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002177199209
TypeChannel
Username@svitloo_kyiv
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live18 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 18 August 2026
On Telegramt.me/svitloo_kyiv

Growth

3,8493,8683,858.57 August 2026 — 3,868 subscribers8 August 2026 — 3,866 subscribers11 August 2026 — 3,858 subscribers15 August 2026 — 3,853 subscribers18 August 2026 — 3,849 subscribers7 August 202618 August 2026
5 measurements spanning 11 days, net -19. 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 3,846–3,871 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Aug 2026, 09:363,849-4
15 Aug 2026, 06:073,853-5
11 Aug 2026, 14:153,858-8
8 Aug 2026, 10:333,866-2
7 Aug 2026, 13:323,868first reading

Engagement

28 posts held, back to 5 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
21.9%
avg views ÷ 3,849 subscribers
Avg views / post
842
28 posts measured
Reaction rate
0.594%
reactions ÷ views · ER floor
Posts in window
28
of 28 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 8 August 2026
Posts held28 (5 August 20268 August 2026)
Views total23,588
Reactions total140
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 06: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.

Reaction mix

140 reactions across 27 posts, in 7 distinct kinds. The most used accounts for 47.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🙏6747.9%
😢5438.6%
custom 520398291215163564775.00%
🤔64.29%
🤬32.14%
🤯21.43%
👎10.714%

Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it isTelegram’s.

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

Measured over the 28 most recent posts we hold, published 5 August 2026 to 8 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

8 Aug 2026, 05:59 UTC9 views0 reactionsread 8 August 2026

🕯9:00 – загальнонаціональна хвилина мовчання Зупиніться й згадайте тих, чиї життя забрала війна. Військових і цивільних. Світла пам’ять! Світло💡Київ

8 Aug 2026, 05:01 UTC173 views3 reactionsread 8 August 2026

💡 Нагадуємо, сьогодні цілий день зі світлом. 🔋 Будь ласка, споживайте електроенергію ощадливо. 📢 Нагадуємо про наш новий проект - @kyiv_passtrans Світло💡Київ

custom 52039829121516356473

7 Aug 2026, 20:55 UTC781 views2 reactionsread 8 August 2026

💡 В Подільському районі частково зникло світло через аварійні ремонтні роботи, — ДТЕК. ❗️Орієнтовний час відновлення до 03:00 08.08.2026. Світло💡Київ

😢2

7 Aug 2026, 20:11 UTC821 views3 reactionsread 8 August 2026

💡Частково зникло світло у Подільському районі. Світло💡Київ

😢3

7 Aug 2026, 19:15 UTC844 views3 reactionsread 8 August 2026

💡 Станом на 22:15 🔋Усі групи зі світлом ❤️Тихої ночі! 📢 Нагадуємо про наш новий проект - @kyiv_passtrans Світло💡Київ

🙏2custom 52039829121516356471

7 Aug 2026, 15:02 UTC887 views4 reactionsread 8 August 2026

💡Завтра, 8 СЕРПНЯ, застосування графіків погодинних відключень не прогнозується (для побутових споживачів). 🟠У разі зміни ситуації — про це буде повідомлено додатково. 🔋Будь ласка, споживайте електроенергію ощадливо. ❗️Не вмикайте кілька потужних електроприладів одночасно у період з 8:00 до 11:00 та з 16:00 до 22:00. 📢 Нагадуємо про наш новий проект - @kyiv_passtrans Світло💡Київ

🙏4

7 Aug 2026, 14:31 UTC905 views4 reactionsread 8 August 2026

‼️Київ: частина Подільського та Оболонського районів тимчасово без світла через аварію Енергетики вже працюють та роблять усе можливе, щоб якнайшвидше повернути електрику в домівки киян. Просимо ощадливо використовувати електроенергію та не вмикати одночасно енергоємні прилади. Це дуже допоможе пройти літні піки та уникнути повторних аварій. Світло💡Київ

😢4

7 Aug 2026, 13:32 UTC893 views3 reactionsread 8 August 2026

💡 В Оболонському районі виникли аварійні відключення електроенергії, - ДТЕК. ❗️Орієнтовний час відновлення 19:59 год. Світло💡Київ

🤔2😢1

7 Aug 2026, 13:26 UTC893 views5 reactionsread 8 August 2026

❗️росія масовано атакувала обʼєкти «Укрнафти» Ворог завдав ударів по 7 активах, які забезпечують видобуток нафти та газу. ▪️Крім того, уражено 4 заправки на Запоріжжі та Дніпропетровщині. Світло💡Київ

🙏3🤬2

7 Aug 2026, 13:08 UTC830 views2 reactionsread 8 August 2026

💡Частково зникло світло у Оболонському районі. Світло💡Київ

👎1😢1

7 Aug 2026, 07:20 UTC891 views2 reactionsread 8 August 2026

⚡️ Оперативна ситуація в енергосистемі України станом на ранок 7 серпня ➡️ Внаслідок бойових дій та обстрілів енергетичних об'єктів частина споживачів у Дніпропетровській, Донецькій, Херсонській, Сумській та Харківській областях тимчасово залишається без електропостачання. ➡️ Відновлювальні роботи тривають скрізь, де дозволяє безпекова ситуація. Енергетики працюють, щоб якнайшвидше повернути світло в оселі українці

🙏2

7 Aug 2026, 05:59 UTC778 views7 reactionsread 8 August 2026

🕯9:00 – загальнонаціональна хвилина мовчання Зупиніться й згадайте тих, чиї життя забрала війна. Військових і цивільних. Світла пам’ять! Світло💡Київ

😢4🙏3

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

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.

Моніторинг Київ | Аналітика
@kyiv_monit0ring · 93,188
Telegram ranks this channel #82 of 84 here — alongside 83 others — read 16 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 18 August 2026 — this entry's latest reading, not the date you are reading this.

“Світло💡Київ” (@svitloo_kyiv), 3,849 subscribers as measured 18 August 2026. Telegram Register, tgregister.com/channel/svitloo_kyiv.

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.