Telegram RegisterThe public register of Telegram
Telegram profile photo for БЛИСКАВКА Київщина

Channel

БЛИСКАВКА Київщина

@blyskavka_kyivshchyna

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

5,172subscribers

-23 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-1002447656574
TypeChannel
Username@blyskavka_kyivshchyna
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 November 2026
Measurements held26
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/blyskavka_kyivshchyna

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 13 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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 1 other registered channel. This entry also sits inside a group of 3 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 (1 of the pairs behind the counts below)
Posted firstThenOverlapGap
@blyskavka_kyiv/6701212 Aug 2026, 03:43 UTC@blyskavka_kyivshchyna/47780 · this entry12 Aug 2026, 03:43 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
@blyskavka_kyiv5 (5/5 hand-verifiable sample passed)1.0022 minutes@blyskavka_kyiv (3–2)

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 1 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 53 comparable posts for this entry, running 7 August 2026 to 12 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).

Of the group of 3 channels, the one whose matching posts we hold earliest is @blyskavka_ua. That channel is not among the channels listed above, so this entry may share no posts with it and this does not say where this entry’s content came from. It is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_mutual, last confirmed 13 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 3 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

5,1555,3595,2577 August 2026 — 5,195 subscribers8 August 2026 — 5,215 subscribers11 August 2026 — 5,199 subscribers15 August 2026 — 5,200 subscribers18 August 2026 — 5,199 subscribers21 August 2026 — 5,203 subscribers24 August 2026 — 5,192 subscribers27 August 2026 — 5,298 subscribers30 August 2026 — 5,353 subscribers2 September 2026 — 5,351 subscribers6 September 2026 — 5,359 subscribers11 September 2026 — 5,346 subscribers14 September 2026 — 5,326 subscribers19 September 2026 — 5,310 subscribers29 September 2026 — 5,258 subscribers6 October 2026 — 5,248 subscribers12 October 2026 — 5,219 subscribers15 October 2026 — 5,208 subscribers18 October 2026 — 5,193 subscribers21 October 2026 — 5,192 subscribers24 October 2026 — 5,183 subscribers27 October 2026 — 5,176 subscribers30 October 2026 — 5,164 subscribers2 November 2026 — 5,155 subscribers9 November 2026 — 5,161 subscribers14 November 2026 — 5,172 subscribers5,1727 August 202614 November 2026
26 measurements spanning 99 days, net -23. 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 5,124–5,390 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 26
Measured (UTC)SubscribersChange
14 Nov 2026, 21:185,172+11
9 Nov 2026, 10:465,161+6
2 Nov 2026, 07:565,155-9
30 Oct 2026, 18:105,164-12
27 Oct 2026, 20:005,176-7
24 Oct 2026, 13:365,183-9
21 Oct 2026, 13:565,192-1
18 Oct 2026, 18:415,193-15
15 Oct 2026, 15:455,208-11
12 Oct 2026, 12:095,219-29
6 Oct 2026, 02:205,248-10
29 Sept 2026, 03:165,258-52
19 Sept 2026, 02:365,310-16
14 Sept 2026, 23:185,326-20
11 Sept 2026, 06:385,346-13
6 Sept 2026, 12:175,359+8
2 Sept 2026, 02:585,351-2
30 Aug 2026, 03:295,353+55
27 Aug 2026, 10:355,298+106
24 Aug 2026, 14:475,192first reading

Engagement

99 posts held, back to 7 August 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 7 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 99 posts for this entry, the most recent from 12 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
11m 19s
Average length
1m 15s

Measured directly from 9 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

1,049 reactions across 91 posts, in 17 distinct kinds. The most used accounts for 34.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🙏36534.8%
😢17316.5%
❤14914.2%
🤬908.58%
🤣726.86%
👍716.77%
😭646.10%
💔171.62%
🥰90.858%
💩80.763%
😱80.763%
🤔70.667%
🤯70.667%
👏50.477%
😁20.191%
👎10.095%
🔥10.095%

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

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

12 Aug 2026, 04:35 UTC32 views0 reactionsread 12 August 2026

⚡ У повітряному просторі зафіксовано БпЛА. Сили ППО працюють по цілях, - КОВА.

12 Aug 2026, 04:16 UTC291 views7 reactionsread 12 August 2026

⚡Реактивний БпЛА курс на Бровари з півночі. 7:20 Ще 5 реактивних повз Славутич в напрямку столиці/Броварів.

🙏7

12 Aug 2026, 03:43 UTC586 views10 reactionsread 12 August 2026

⚡ Рух поїздів Kyiv City Express тимчасово призупинено через підвищену загрозу для столиці та Київського регіону. Рух Kyiv City Express буде відновлено по завершенні повітряної загрози.

🙏6🤬4

12 Aug 2026, 03:42 UTC612 viewsread 12 August 2026

⚡Фастівський, Обухівський, Білоцерківський райони - відбій 🟢

12 Aug 2026, 03:02 UTC852 views12 reactionsread 12 August 2026

⚡ БпЛА з півдня та заходу Чернігівщини, курс на Київщину. 6:06 Реактивні БпЛА з півночі Київщини та з Київського водосховища, курс на столицю. 6:09 На Велику Димерку з півночі. 6:13 На Київщині, в районі Броварів, пролунали звуки вибухів 6:19 Відбій загрози застосування балістичного озброєння.

🙏8🤬4

12 Aug 2026, 02:56 UTC885 views14 reactionsread 12 August 2026

⚡Київська область - повітряна тривога 🔴

🙏10🤬3🔥1

11 Aug 2026, 20:42 UTC≈1,240 views9 reactionsread 12 August 2026
Sticker

Sticker, posted without a caption

🙏9

11 Aug 2026, 20:35 UTC≈1,260 views6 reactionsread 12 August 2026

⚡️Броварський, Бориспільський райони — повітряна тривога🔴 👉 БЛИСКАВКА Київщина | Реклама | Обговорення

🙏6

11 Aug 2026, 18:59 UTC≈1,420 views14 reactionsread 12 August 2026
Photo

⚡️На архівних фото — будівництво Київського водосховища та люди, які працювали над його створенням. Минуло багато років, і Київське море стало частиною життя краю — місцем для відпочинку, риболовлі та прогулянок. 👉 БЛИСКАВКА Київщина | Реклама | Обговорення

🙏7❤6👍1

11 Aug 2026, 18:26 UTC≈1,240 views6 reactionsread 12 August 2026
Photo

⚡️Поліція Київщини відкрила кримінальне провадження через забруднення водойм та масову загибель риби у Петропавлівській Борщагівці. 👉 БЛИСКАВКА Київщина | Реклама | Обговорення

👍6

11 Aug 2026, 17:57 UTC878 views4 reactionsread 12 August 2026
Forwarded from @blyskavka_uaVideo

⚡️Начальник ГУР МО Олег Іващенко доповів про підготовку нової хвилі мобілізації в росії на осінь, — Зеленський. Ці плани підтверджуються внутрішніми російськими документами. Після так званих парламентських виборів кремль нібито планує мобілізувати кілька сотень тисяч людей до кінця року та ще стільки ж — у 2027 році. «Готуємося до своїх активних дій, максимального ускладнення росії в реалізації таких планів», — зая…

🤬4

11 Aug 2026, 17:30 UTC≈1,150 views24 reactionsread 12 August 2026
Photo

⚡️У Києві та області через російські обстріли знищено 80–100 тис. кв. м холодних складів, що може призвести до подорожчання окремих продуктів на 5–6%, пише РБК-Україна. Регіон втратив значну частину складських приміщень для зберігання м’яса, молочних продуктів, овочів та інших товарів, яким потрібна низька температура, а доступних площ залишилося лише 20–30% від втраченого обсягу. Ритейлерам доведеться використовув…

🤬18😢5❤1

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

Republishes

Channels on the register whose posts this channel has forwarded.

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

“БЛИСКАВКА Київщина” (@blyskavka_kyivshchyna), 5,172 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/blyskavka_kyivshchyna.

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.