Telegram RegisterThe public register of Telegram
Telegram profile photo for Київщина не спить | Ірпінь | Буча | Вишневе

Channel

Київщина не спить | Ірпінь | Буча | Вишневе

@kyivshchyna_night

On this record: Topic · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Cite this entry

16,033subscribers

+3,152 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001169974255
TypeChannel
Username@kyivshchyna_night
Created14 July 2020measured — cross-checked against a third-party dataset (TGDataset)
First recorded7 August 2026
Last confirmed live19 September 2026
Measurements held28
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/kyivshchyna_night

Topic

National news — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 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.

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

116,0338,0177 August 2026 — 12,881 subscribers7 August 2026 — 12,925 subscribers8 August 2026 — 13,075 subscribers9 August 2026 — 13,046 subscribers10 August 2026 — 1 subscribers17 August 2026 — 13,824 subscribers18 August 2026 — 13,858 subscribers19 August 2026 — 13,873 subscribers20 August 2026 — 13,852 subscribers21 August 2026 — 13,854 subscribers22 August 2026 — 13,817 subscribers24 August 2026 — 13,775 subscribers25 August 2026 — 14,123 subscribers26 August 2026 — 14,357 subscribers27 August 2026 — 14,456 subscribers29 August 2026 — 14,449 subscribers29 August 2026 — 14,480 subscribers31 August 2026 — 14,442 subscribers1 September 2026 — 14,960 subscribers2 September 2026 — 15,121 subscribers3 September 2026 — 15,388 subscribers5 September 2026 — 15,497 subscribers8 September 2026 — 15,515 subscribers11 September 2026 — 15,864 subscribers13 September 2026 — 15,858 subscribers15 September 2026 — 15,855 subscribers16 September 2026 — 16,006 subscribers19 September 2026 — 16,033 subscribers7 August 202619 September 2026
28 measurements spanning 43 days, net +3,152. 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”.
Measurement log — every subscribers count we have recorded, most recent 20 of 28
Measured (UTC)SubscribersChange
19 Sept 2026, 05:3816,033+27
16 Sept 2026, 20:5616,006+151
15 Sept 2026, 00:0115,855-3
13 Sept 2026, 06:1515,858-6
11 Sept 2026, 05:1815,864+349
8 Sept 2026, 09:1415,515+18
5 Sept 2026, 02:0015,497+109
3 Sept 2026, 05:4815,388+267
2 Sept 2026, 00:5415,121+161
1 Sept 2026, 00:3714,960+518
31 Aug 2026, 01:3714,442-38
29 Aug 2026, 23:0414,480+31
29 Aug 2026, 00:0414,449-7
27 Aug 2026, 23:5514,456+99
26 Aug 2026, 21:0514,357+234
25 Aug 2026, 19:4614,123+348
24 Aug 2026, 16:5513,775-42
22 Aug 2026, 23:0513,817-37
21 Aug 2026, 15:0613,854+2
20 Aug 2026, 11:5313,852first reading

Engagement

520 posts held, back to 6 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 45 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
12.2%
avg views ÷ 16,033 subscribers
Avg views / post
1,960
263 posts measured
Reaction rate
1.48%
reactions ÷ views · ER floor
Posts in window
263
of 520 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 3 September 2026
Posts held520 (6 August 20263 September 2026)
Views total516,042
Reactions total7,619
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 10:50 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

Video runtime
52m 40s
Average length
38s

Measured directly from 83 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

15,139 reactions across 518 posts, in 17 distinct kinds. The most used accounts for 23.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🙏3,54523.4%
2,35915.6%
🤬2,11814.0%
😢1,79411.9%
👍1,60610.6%
😱1,3238.74%
🤯9946.57%
👎3622.39%
🤡2561.69%
😁2491.64%
🔥2111.39%
❤‍🔥1931.27%
💔750.495%
🥰270.178%
👏120.079%
💯120.079%
😍30.02%

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

Measured over the 520 most recent posts we hold, published 6 August 2026 to 3 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.

Telegram Stars

Stars received
3
across the posts below
Posts paid on
2
of 520 we hold a reading for · 0.4%
Most on one post
2
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @kyivshchyna_night. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 520 most recent posts we hold for this entry, published 6 August 2026 to 3 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

3 Sept 2026, 10:34 UTC484 views14 reactionsread 3 September 2026
Photo

🔴Уже завтра буде введено в обіг нову банкноту — 2000 грн: це буде найбільший номінал в Україні, — НБУ. Василь Стус — видатна постать на банкноті номіналом 2 000 гривень. Київщина не спить I Підписатися

😢9👍31👎1

3 Sept 2026, 09:49 UTC982 views30 reactionsread 3 September 2026

🔴БПЛА на Ірпінь Київщина не спить I Підписатися

🙏17🤬9😢3🤯1

3 Sept 2026, 09:15 UTC≈1,260 views39 reactionsread 3 September 2026

🔴Бучанський район, наразі видихаємо Київщина не спить I Підписатися

🙏2311👍4👏1

3 Sept 2026, 08:43 UTC≈1,440 views36 reactionsread 3 September 2026

🔴Ворожий БпЛА Буча/Гостомель Київщина не спить I Підписатися

🙏26🤯5😢3🤬2

3 Sept 2026, 08:36 UTC≈1,480 views28 reactionsread 3 September 2026

🔴2 реактивних заходять на Димер. Один за одним. Йдуть, поки, в бік Гостомеля. Київщина не спить I Підписатися

🤬13🙏10😱5

3 Sept 2026, 08:06 UTC≈1,590 views29 reactionsread 3 September 2026

🔴Гостомель знову, кружляє Київщина не спить I Підписатися

🙏19😢5😱3🤬2

3 Sept 2026, 08:02 UTC≈2,700 views29 reactionsread 3 September 2026

🔴Також додатково пуски 8 реактивних дронів з Орла, - монітори Київщина не спить I Підписатися

🙏15🤬102🤯1😢1

3 Sept 2026, 08:00 UTC≈1,580 views25 reactionsread 3 September 2026

🔴БпЛА на Гостомель/Ірпінь Київщина не спить I Підписатися

🙏15🤯6😱3🤬1

3 Sept 2026, 07:55 UTC≈1,580 views22 reactionsread 3 September 2026
Video

🔴 В Бучанському районі повітряна тривога Київщина не спить I Підписатися

🤯11🙏6😱31🤬1

3 Sept 2026, 07:49 UTC≈2,630 views27 reactionsread 3 September 2026

🔴«росіяни не планують зменшувати обертів»: Зеленський про тривалі тривоги та удари рф по Україні. Київщина не спить I Підписатися

🤯15🙏6🤬5😱1

3 Sept 2026, 07:32 UTC≈2,680 views26 reactionsread 3 September 2026
Photo

🔴Унаслідок ранкової атаки у селі Святопетрівське зафіксовано падіння уламків БпЛА, – сільрада Влучання реактивного шахеду в районі Чайки-Шевченкове-Білогородка-Святопетрівське. За уточненою інформацією усі 3 реактивні шахеди було збито у момент падіння на складські приміщення. Київщина не спить I Підписатися

🙏16👍52😱2🤡1

3 Sept 2026, 06:44 UTC≈2,730 views47 reactionsread 3 September 2026
Video

🔴«Дефіциту продуктів в Україні немає і не може бути», — економіст Новак За його словами, Україна має власне перевиробництво продовольства, а імпорт також продовжує працювати. Тому відсутність окремого товару в конкретному магазині ще не означає дефіцит: «Немає в одному — буде в іншому або на ринку», — пояснив економіст. Київщина не спить I Підписатися

👍30🤡6🙏54😱2

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

Posts edited after publishing

@kyivshchyna_night edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
26 August 2026
Most recent edit
26 August 2026

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

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

“Київщина не спить | Ірпінь | Буча | Вишневе” (@kyivshchyna_night), 16,033 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/kyivshchyna_night.

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.