❗️Горить автомобіль в Бортничах, ймовірно підпал. Інформація уточнюється Надсилайте новини в анонімний бот ➡️@novosty_kiev_bot 🇺🇦 ➡️ ПІДПИСАТИСЬ ⤵️ LIVE
🤯164🙏95🤬59❤27😱11😢8custom 54564374992178448246custom 52355546283340131725

Channel
@kievinfo_kyiv
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · View velocity · Reactions · Stars · Advertising · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Domains linked from posts · Cite this entry
1,198,280subscribers
-2,878 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among the largest entries.
| Telegram ID | -1001206439755 |
|---|---|
| Type | Channel |
| Username | @kievinfo_kyiv |
| Description | ⚡️Актуальні події Києва 💥 Яскравий контент 24/7 👉 З питань реклами: @reklama_uabot 💵 Платимо гроші за унікальний контент 👉 Надсилай адміну контент: @novosty_kieva_bot @novosty_kiev_bot 👇🏻 Посилання для запрошення друзів: https://t.me/+aAaZ8kQkkpo2ZjRi |
| Created | 24 February 2019 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/kievinfo_kyiv |
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 8 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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.
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.
Posts published here appear word for word on 7 other registered channels. They sit inside a group of 377 channels that share the same post bodies 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @times_ukraina/694618 Jul 2026, 07:00 UTC | @kievinfo_kyiv/92067 · this entry8 Jul 2026, 08:30 UTC | 0.99 | 1.5 hours |
| @times_ukraina/7027423 Jul 2026, 07:00 UTC | @kievinfo_kyiv/92921 · this entry23 Jul 2026, 08:15 UTC | 0.99 | 76 minutes |
| @times_ukraina/4469813 Jan 2025, 08:00 UTC | @kievinfo_kyiv/59315 · this entry13 Jan 2025, 09:00 UTC | 0.99 | 60 minutes |
| @kievinfo_kyiv/60610 · this entry1 Feb 2025, 08:00 UTC | @times_ukraina/453251 Feb 2025, 10:00 UTC | 0.98 | 2.0 hours |
| @times_ukraina/4591815 Feb 2025, 08:00 UTC | @kievinfo_kyiv/61614 · this entry15 Feb 2025, 08:17 UTC | 0.98 | 18 minutes |
| @kievinfo_kyiv/93178 · this entry27 Jul 2026, 07:00 UTC | @times_ukraina/7044227 Jul 2026, 08:00 UTC | 0.96 | 60 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @times_ukraina | 10 (8/8 hand-verifiable sample passed) | 0.97 | 76 minutes | @times_ukraina (7–3) |
| @kiev_information | 9 (7/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (9–0) |
| @peace4Ukr | 9 (8/8 hand-verifiable sample passed) | 1.00 | 8 days | this entry (9–0) |
| @kievreal1 | 9 (8/8 hand-verifiable sample passed) | 1.00 | 2.4 hours | @kievreal1 (6–3) |
| @truexanewsua | 8 (8/8 hand-verifiable sample passed) | 1.00 | 3.3 hours | this entry (5–3) |
| @odessa_infonews | 7 (7/7 hand-verifiable sample passed) | 0.98 | 5 minutes | this entry (7–0) |
| @insiderukr | 6 (6/6 hand-verifiable sample passed) | 1.00 | 1.5 hours | @insiderukr (6–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. None of the 22 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 2,371 comparable posts for this entry, running 27 December 2024 to 8 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.
Across the whole group of 377, the earliest publisher we hold is @mash. That is a statement about our reading window, not a claim of authorship.
On 2 of the 254 posts we watched over 30days, the view counter climbed while the reaction counter stayed where it was — by more than this channel’s own reactions-per-view rate can account for. That rate, measured on this entry, is 0.0065 reactions per view.
| Post | Over | Views | Reactions | Expected |
|---|---|---|---|---|
| /940898 Aug 2026, 20:04 UTC | 12 hours | 323,000 → 373,000at least +49,000 | 1,945 → 1,985at most +50 | +316.6 |
| /940999 Aug 2026, 00:18 UTC | 12 hours | 296,000 → 353,000at least +56,000 | 1,114 → 1,161at most +57 | +361.8 |
Expectedis the view gain multiplied by this channel’s own prior reactions-per-view rate over the same post — not a corpus average, so a channel whose audience never reacts is compared only against itself. Every interval is credited in the direction that makes the observation harder to record, never easier: t.me renders views and reactions to three significant figures above ~1,000, so a raw delta can be a rendering step. Every delta below is at least 4 x the coarser reading's step, the view gain is discounted by a full step and the reaction gain credited with one. Measured by tgregister velocity.py (our own t.me/s/ readings).
What this does and does not say.It says the two counters moved apart, by more than rounding and more than this channel’s own history predicts. It asserts no cause. Views arriving from outside Telegram, an embedded or forwarded copy of the post, and a burst of readers who simply do not react all produce this shape. This detector has recorded very few observations across the whole register, and its precision has not been measured; treat it as an anomaly worth looking at, not as a finding.
Recorded under the keys clone_copy · clone_mutual · clone_source · view_reaction_decoupling, last confirmed 13 August 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.
This channel’s posts match, word for word or near enough, posts on 376 other registered channels, 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.
326 more channels are in this same group but not listed individually here.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 13:05 | 1,198,280 | +156 |
| 11 Aug 2026, 09:48 | 1,198,124 | +85 |
| 10 Aug 2026, 09:26 | 1,198,039 | -431 |
| 9 Aug 2026, 10:01 | 1,198,470 | -1,861 |
| 8 Aug 2026, 11:31 | 1,200,331 | -161 |
| 7 Aug 2026, 12:27 | 1,200,492 | +339 |
| 6 Aug 2026, 13:30 | 1,200,153 | -1,005 |
| 6 Aug 2026, 00:41 | 1,201,158 | first reading |
4,763 posts held, back to 27 December 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 298 pagesof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 12 August 2026 |
|---|---|
| Posts held | 4,763 (27 December 2024 – 12 August 2026) |
| Views total | 411,593,003 |
| Reactions total | 4,009,183 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Aug 2026, 00: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.
Lifetime counters from Telegram’s own channel header, read 12 August 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.
Measured directly from 50 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.
How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.
Computed from 277 of this channel’s own posts over the last 30 days (5 of the 24-hour readings behind this are interpolated, not measured directly): across 118of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 1.9 hours of being posted; a typical post has already reached 37.3% of its 24-hour view count within the first hour, and 77.3% within the first six; the median 24-hour reach across those posts is 368,500 views — 30.8% of this channel’s own subscriber count (90th percentile 444,900).
| Post | Readings | Latest reading | Curve | 24h reach | Half of last-observed views by |
|---|---|---|---|---|---|
| /9430012 Aug 2026, 23:45 UTC | 131 minutes – 31 minutes old | 20,800 views ~278 reactions | no checkpoint reading yet | not yet at 24h | not measurable yet |
| /9429912 Aug 2026, 23:07 UTC | 233 minutes – 68 minutes old | 35,900 views ~326 reactions | 60 minutes: 31,869 interp. | not yet at 24h | 33 minutesupper bound — already past half at first reading · provisional — final view count still climbing |
| /9429812 Aug 2026, 22:23 UTC | 412 minutes – 1.9 hours old | 64,800 views ~832 reactions | 60 minutes: 45,300 interp.still climbing at last reading | not yet at 24h | 31 minutesprovisional — final view count still climbing |
| /9429612 Aug 2026, 20:04 UTC | 816 minutes – 4.2 hours old | 214,000 views ~13,888 reactions | 60 minutes: 140,818 interp. → 3.0 hours: 200,000still climbing at last reading | not yet at 24h | 36 minutesprovisional — final view count still climbing |
| /9429512 Aug 2026, 17:14 UTC | 1321 minutes – 7.0 hours old | 343,000 views ~13,065 reactions | 60 minutes: 148,960 interp. → 3.0 hours: 280,000 → 6.0 hours: 337,000still climbing at last reading | not yet at 24h | 78 minutesprovisional — final view count still climbing |
| /9429412 Aug 2026, 15:03 UTC | 1717 minutes – 9.2 hours old | 378,000 views ~7,563 reactions | 60 minutes: 139,293 interp. → 3.0 hours: 258,000 → 6.0 hours: 355,000still climbing at last reading | not yet at 24h | 2.0 hoursprovisional — final view count still climbing |
| /9428412 Aug 2026, 13:30 UTC | 206 minutes – 11 hours old | 391,000 views ~4,372 reactions | 60 minutes: 113,855 interp. → 3.0 hours: 232,000 → 6.0 hours: 331,000still climbing at last reading | not yet at 24h | 2.1 hoursprovisional — final view count still climbing |
| /9428312 Aug 2026, 11:41 UTC | 2314 minutes – 13 hours old | 362,000 views ~3,482 reactions | 60 minutes: 147,041 interp. → 3.0 hours: 237,000 → 6.0 hours: 304,000 → 12 hours: 361,000still climbing at last reading | not yet at 24h | 1.6 hoursprovisional — final view count still climbing |
Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed viewsis the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.
884,062 reactions across 286 posts, in 17 distinct kinds. The most used accounts for 29.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🙏 | 258,847 | 29.3% | |
| 🤬 | 249,388 | 28.2% | |
| 😢 | 120,129 | 13.6% | |
| 😁 | 94,326 | 10.7% | |
| ❤ | 84,396 | 9.55% | |
| 🤯 | 26,954 | 3.05% | |
| custom 5269531045165816230 | 17,439 | 1.97% | |
| 😱 | 11,967 | 1.35% | |
| custom 5456437499217844824 | 3,941 | 0.446% | |
| custom 5474390217702009301 | 3,464 | 0.392% | |
| 💔 | 3,241 | 0.367% | |
| custom 5422407416769702242 | 3,101 | 0.351% | |
| 💯 | 2,352 | 0.266% | |
| custom 5235554628334013172 | 1,278 | 0.145% | |
| custom 5355294343701747258 | 1,186 | 0.134% | |
| custom 5235564098736890654 | 1,123 | 0.127% | |
| ⚡ | 930 | 0.105% |
Custom emoji. 7 of the rows above are 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 counts beside them areTelegram’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 1,000 of the 1,000 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 3,390,415reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 18 July 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @kievinfo_kyiv. 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 18 July 2026 to 12 August 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.
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. They are printed side by side with the count behind each rather than as a ratio: an ad and an ordinary post are not otherwise matched — for topic, for length, for hour of day — so the gap between them is a description of two groups and not the effect of one being an ad.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 18 July 2026 to 12 August 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.
❗️Горить автомобіль в Бортничах, ймовірно підпал. Інформація уточнюється Надсилайте новини в анонімний бот ➡️@novosty_kiev_bot 🇺🇦 ➡️ ПІДПИСАТИСЬ ⤵️ LIVE
🤯164🙏95🤬59❤27😱11😢8custom 54564374992178448246custom 52355546283340131725
✅ВІДБІЙ ПОВІТРЯНОЇ ТРИВОГИ ✅
🙏300❤47😁6custom 54224074167697022424💯2🤬2custom 52355546283340131721custom 52695310451658162301
🔴 Вишгородський район - повітряна тривога! Загроза по БпЛА з Чернігівщини Детальний радар 👉🏽 @kievinform_ua1
🙏510🤬271❤37😁14custom 545643749921784482411custom 53552943437017472587custom 52355546283340131726custom 52695310451658162306
🤯Ситуація погіршується: порожні полиці в супермаркетах Київщини, – місцеві ЗМІ. Сьогодні постраждав склад логістичної компанії, що перевозила товари для «АТБ», «Metro», «NOVUS», «Ашан» та «Сільпо». Надсилайте новини в анонімний бот ➡️@novosty_kiev_bot 🇺🇦 ➡️ ПІДПИСАТИСЬ ⤵️ LIVE
😁5,000custom 52695310451658162304,230😢2,970🤬971🙏345❤258🤯57custom 545643749921784482442
❗️путін зупинить війну, у нас є план: «Ми розуміємо, що маємо робити», — Зеленський ㅤ Надсилайте новини в анонімний бот ➡️@novosty_kiev_bot 🇺🇦 ➡️ ПІДПИСАТИСЬ ⤵️ LIVE
😁5,660🙏4,120custom 52695310451658162301,770❤637custom 5456437499217844824279🤬205custom 5422407416769702242199💯83
❗️Після цих «Шахедів» уночі можливий обстріл балістикою, про який попереджали раніше.
🤬4,820🙏1,830😢356❤164custom 526953104516581623093custom 545643749921784482487😁86custom 542240741676970224265
😔Кадри з місця російського удару по логістичних об’єктах у Броварському районі На одній з локацій рятувальники вже приборкали пожежу, на інших — роботи ще тривають. ㅤ Надсилайте новини в анонімний бот ➡️@novosty_kiev_bot 🇺🇦 ➡️ ПІДПИСАТИСЬ ⤵️ LIVE
😢2,560🤬771🙏429❤419😁47🤯44💔43custom 526953104516581623043
🔴🚀Момент стрімкого падіння збитого ШАХЕДА в Києві ❗️У Деснянському районі Києва внаслідок падіння уламків пошкоджений вхід до одного із комунальних медзакладів, — Кличко Потерпілих немає. ㅤ Надсилайте новини в анонімний бот ➡️@novosty_kiev_bot 🇺🇦 ➡️ ПІДПИСАТИСЬ ⤵️ LIVE
🙏2,310❤473🤯241🤬204😢89😁63custom 526953104516581623052custom 523555462833401317222
✅ВІДБІЙ ПОВІТРЯНОЇ ТРИВОГИ ✅
🙏945❤128😁21custom 523556409873689065417custom 542240741676970224214🤬8custom 52695310451658162307💯5
❗️У Броварах пошкоджено склад логістичної компанії, яка здійснювала перевезення для таких мереж, як АТБ, МЕТРО, НОВУС, АШАН, СІЛЬПО та працювала по всій Європі, — ЗМІ Троя, ТЕЦ - 6 — БпЛА✈️⚠️ 14:25 ✈️Дорозвідка ㅤ Надсилайте новини в анонімний бот ➡️@novosty_kiev_bot 🇺🇦 ➡️ ПІДПИСАТИСЬ ⤵️ LIVE
🤬4,980😢1,020🙏381❤325🤯129😁72custom 545643749921784482454💔39
Шо по цінам на таксі 👀 ㅤ Надсилайте новини в анонімний бот ➡️@novosty_kiev_bot 🇺🇦 ➡️ ПІДПИСАТИСЬ ⤵️ LIVE
🤬1,630🤯356❤216😁110🙏70custom 545643749921784482467😱42custom 542240741676970224233
У Дарницькому районі, внаслідок падіння БпЛА, пошкоджене нежитлове приміщення, – Кличко. Пожежі немає. Екстрені служби прямують на місце. 🇺🇦 Київ ІНФО | Надіслати новину
🙏1,190🤬361😢93❤91😱31😁18🤯9💔8
Showing the 12 most recent of 4,763 posts we hold for @kievinfo_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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
@kievinfo_kyiv edited 6 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.
Citation-graph rank — 855,606 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
Named by 4 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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.
Read from Telegram’s recommendation API, most recently 8 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.
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.
This channel appears in 141 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
31 domainsthis channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“Київ ІНФО | Новини Україна 🇺🇦” (@kievinfo_kyiv), 1,198,280 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/kievinfo_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.