Telegram RegisterThe public register of Telegram
Telegram profile photo for Київ ІНФО - LIVE | радар

Channel

Київ ІНФО - LIVE | радар

@kievinform_ua1

On this record: Topic · Growth · Engagement · What this channel posts · Stars · Advertising · Posts · Citations · Cite this entry

175,338subscribers

+27,797 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID-1001597308289
TypeChannel
Username@kievinform_ua1
DescriptionКанал ППО Київщини — точно та швидко інформуємо про загрози 👉 З питань реклами: @reklama_uabot
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live18 September 2026
Measurements held35
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/kievinform_ua1

Topic

National news — 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 9 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 why it has no browse page of its own yet.

Growth

147,528175,338161,4336 August 2026 — 147,541 subscribers6 August 2026 — 147,541 subscribers6 August 2026 — 147,528 subscribers7 August 2026 — 147,563 subscribers8 August 2026 — 147,821 subscribers9 August 2026 — 148,786 subscribers10 August 2026 — 148,851 subscribers11 August 2026 — 149,084 subscribers12 August 2026 — 149,304 subscribers12 August 2026 — 150,123 subscribers14 August 2026 — 150,129 subscribers15 August 2026 — 150,041 subscribers17 August 2026 — 150,307 subscribers18 August 2026 — 150,406 subscribers19 August 2026 — 150,898 subscribers20 August 2026 — 152,846 subscribers21 August 2026 — 153,030 subscribers22 August 2026 — 153,355 subscribers24 August 2026 — 153,278 subscribers25 August 2026 — 153,247 subscribers26 August 2026 — 153,276 subscribers27 August 2026 — 155,585 subscribers28 August 2026 — 157,314 subscribers29 August 2026 — 158,200 subscribers30 August 2026 — 160,600 subscribers31 August 2026 — 161,788 subscribers2 September 2026 — 162,719 subscribers2 September 2026 — 164,220 subscribers4 September 2026 — 166,011 subscribers7 September 2026 — 167,756 subscribers10 September 2026 — 172,200 subscribers12 September 2026 — 173,636 subscribers14 September 2026 — 173,683 subscribers16 September 2026 — 174,284 subscribers18 September 2026 — 175,338 subscribers6 August 202618 September 2026
35 measurements spanning 43 days, net +27,797. 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 143,357–179,510 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 35
Measured (UTC)SubscribersChange
18 Sept 2026, 12:19175,338+1,054
16 Sept 2026, 03:16174,284+601
14 Sept 2026, 06:16173,683+47
12 Sept 2026, 17:41173,636+1,436
10 Sept 2026, 19:58172,200+4,444
7 Sept 2026, 18:17167,756+1,745
4 Sept 2026, 16:40166,011+1,791
2 Sept 2026, 23:56164,220+1,501
2 Sept 2026, 00:05162,719+931
31 Aug 2026, 23:34161,788+1,188
30 Aug 2026, 21:15160,600+2,400
29 Aug 2026, 17:43158,200+886
28 Aug 2026, 19:01157,314+1,729
27 Aug 2026, 17:39155,585+2,309
26 Aug 2026, 16:49153,276+29
25 Aug 2026, 13:23153,247-31
24 Aug 2026, 11:36153,278-77
22 Aug 2026, 18:13153,355+325
21 Aug 2026, 10:23153,030+184
20 Aug 2026, 09:48152,846first reading

Engagement

1,734 posts held, back to 5 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 106 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
17.8%
avg views ÷ 175,338 subscribers
Avg views / post
31,200
1,111 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
1,111
of 1,734 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. It is computed over the 22 of 1,111 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 26 September 2026
Posts held1,734 (5 August 2026 – 26 September 2026)
Views total34,618,105
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken26 Sept 2026, 20:49 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
≈1,770
Videos
≈737
Links
≈334

Lifetime counters from Telegram’s own channel header, read 26 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
6m 06s
Average length
14s

Measured directly from 26 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.

Telegram Stars

Stars received
441
across the posts below
Posts paid on
20
of 1,000 we hold a reading for · 2%
Most on one post
366
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @kievinform_ua1. 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 1,000 most recent posts we hold for this entry (the sample is capped at 1,000), published 30 August 2026 to 26 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.

Advertising

Ad load
0.1%
1 of 1,000 posts carry an ad marker
Regulatory tokens
0
none — marked by hashtag only
Median views · ads
17,200
over 1 measured post
Median views · rest
30,300
over 999 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 30 August 2026 to 26 September 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

26 Sept 2026, 20:31 UTC≈11,100 viewsread 26 September 2026

Реактивний БпЛА курсом на Макарів Реактивний БпЛА курсом на Димер

26 Sept 2026, 19:47 UTC≈30,400 viewsread 26 September 2026

реактивний повз Христинівку в напрямку Київщини

26 Sept 2026, 19:38 UTC≈39,400 viewsread 26 September 2026

✈️ Поки що курс на Петрівці / Вишгород

26 Sept 2026, 19:36 UTC≈40,400 viewsread 26 September 2026

🟡 м. Київ - повітряна тривога! Дронова загроза (жовтий рівень)

26 Sept 2026, 19:33 UTC≈42,500 viewsread 26 September 2026

Герань-5 підлітає до Києва, готовність!

Showing the 12 most recent of 1,734 posts we hold for @kievinform_ua1. 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

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

“Київ ІНФО - LIVE | радар” (@kievinform_ua1), 175,338 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/kievinform_ua1.

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.