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 81% 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
14 measurements spanning 41 days, net -59. 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 4,668–4,745 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
16 Sept 2026, 10:20
4,677
-7
12 Sept 2026, 16:40
4,684
-2
9 Sept 2026, 01:15
4,686
-4
3 Sept 2026, 08:38
4,690
-7
31 Aug 2026, 09:45
4,697
-4
28 Aug 2026, 08:04
4,701
-5
25 Aug 2026, 01:04
4,706
-4
21 Aug 2026, 14:16
4,710
-9
18 Aug 2026, 22:36
4,719
-9
16 Aug 2026, 08:38
4,728
-5
12 Aug 2026, 20:14
4,733
-1
9 Aug 2026, 10:52
4,734
-2
6 Aug 2026, 10:34
4,736
no change
6 Aug 2026, 09:54
4,736
first reading
Engagement
5 posts held, back to 9 July 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 5 posts for this entry, the most recent from 30 July 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Video runtime
1m 11s
Average length
1m 11s
Measured directly from 1 video 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
411 reactions across 5 posts, in 8 distinct kinds. The most used accounts for 44.0% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
181
44.0%
😢
94
22.9%
😭
77
18.7%
👍
51
12.4%
🤣
4
0.973%
🤔
2
0.487%
👀
1
0.243%
👎
1
0.243%
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 5 of the 5 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 411 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 9 July 2026 to 30 July 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.
#Київ. 1 людина загинула та 2 постраждали внаслідок російської атаки на Київ.
У столиці виникли пожежі у двох районах.
В Оболонському районі сталося загоряння торговельних павільйонів на території ринку є постраждалий.
У Святошинському районі виникла пожежа на території гаражного кооперативу. Під час гасіння виявлено тіло загиблого. Також постраждав чоловік, його госпіталізували. Загоряння ліквідовано.
У цьому ж р…
#Київ: внаслідок російського обстрілу 2 особи загинули та 5 людей поранені, серед них одна дитина
Під ворожим ударом опинилися Святошинський та Дарницький райони Києва.
📍Дарницький район: сталася пожежа в адміністративно-складській будівлі, в поруч припаркованих вантажних автомобілях та в складській будівлі. Пожежі ліквідовано. На жаль, дві особи загинули. 2 людей травмовано, серед них одна дитина.
📍Святошинський …
На Кирилівському озері в Києві триває ліквідація наслідків масштабного забруднення нафтопродуктами, спричиненого російським обстрілом у ніч проти 2 липня
Щодня рятувальники встановлюють бонові загородження, збирають нафтопродукти та роблять усе можливе, щоб не допустити їх подальшого поширення й мінімізувати шкоду для екосистеми.
Станом на сьогодні рятувальники встановили 200 м сорбувальних бонів. Загалом за шість …
😢41❤27
Showing the 5 most recent of 5 posts we hold for @Kyiv_by_Grishyn. 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.
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.
DOSH @lumpen_v · 34,469 Telegram ranks this channel #11 of 76 here — alongside 75 others — read 3 September 2026
Sergii Ivanov @ivanoise · 31,919 Telegram ranks this channel #45 of 73 here — alongside 72 others — read 5 September 2026
This channel appears in 2 seed channels' Telegram-generated recommendation lists 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 16 September 2026 — this
entry's latest reading, not the date you are reading this.
“Чарівний Київ by Грішин” (@Kyiv_by_Grishyn), 4,677 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/Kyiv_by_Grishyn.
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.
