Telegram RegisterThe public register of Telegram
Telegram profile photo for ФК Динамо Київ

Channel

ФК Динамо Київ

@fcdynamokyiv

On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry

681subscribers

-37 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001165737759
TypeChannel
Username@fcdynamokyiv
Created24 January 2018 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live16 November 2026
Measurements held14
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/fcdynamokyiv

Topic

Sports — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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.

Growth

681718699.56 August 2026 — 718 subscribers6 August 2026 — 718 subscribers14 August 2026 — 713 subscribers20 August 2026 — 708 subscribers27 August 2026 — 709 subscribers3 September 2026 — 708 subscribers12 September 2026 — 707 subscribers30 September 2026 — 698 subscribers10 October 2026 — 697 subscribers17 October 2026 — 692 subscribers24 October 2026 — 691 subscribers31 October 2026 — 689 subscribers7 November 2026 — 684 subscribers16 November 2026 — 681 subscribers6 August 202616 November 2026
14 measurements spanning 102 days, net -37. 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 675–724 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Nov 2026, 08:06681-3
7 Nov 2026, 12:17684-5
31 Oct 2026, 00:06689-2
24 Oct 2026, 15:04691-1
17 Oct 2026, 22:46692-5
10 Oct 2026, 01:56697-1
30 Sept 2026, 09:56698-9
12 Sept 2026, 13:41707-1
3 Sept 2026, 12:18708-1
27 Aug 2026, 11:54709+1
20 Aug 2026, 23:03708-5
14 Aug 2026, 23:55713-5
6 Aug 2026, 16:16718no change
6 Aug 2026, 03:46718first reading

Engagement

20 posts held, back to 13 January 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page 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 20 posts for this entry, the most recent from 30 January 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

91 reactions across 20 posts, in 10 distinct kinds. The most used accounts for 50.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍4650.5%
🔥1819.8%
❤1718.7%
👌22.20%
😭22.20%
🤔22.20%
😁11.10%
🙏11.10%
🤡11.10%
🤮11.10%

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

Measured over the 20 most recent posts we hold, published 13 January 2025 to 30 January 2025, 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

30 Jan 2025, 21:55 UTC≈1,910 views18 reactionsread 6 August 2026
Photo

⏱ Матч завершено! Закінчуємо єврокубковий сезон з перемогою над РФШ 🤍💙 🇺🇦 Динамо 1️⃣:0️⃣ РФШ 🇱🇻

👍13❤4🤮1

30 Jan 2025, 19:04 UTC≈1,650 views2 reactionsread 6 August 2026
Photo

🔹 Наш склад на гру з РФШ 👊

❤1🤡1

30 Jan 2025, 08:03 UTC≈1,250 views4 reactionsread 6 August 2026

🥹 Останнє інтерв’ю Георгія Бущана в «Динамо» 🎤 Дивіться зворушливе відео, насичене багатьма унікальними історіями, на нашому YouTube ▶️

👍2❤1👌1

30 Jan 2025, 07:42 UTC992 views7 reactionsread 6 August 2026
Photo

День матчу!🔹Сьогодні «Динамо» в Лізі Європи зіграє проти латвійського клубу РФШ 🌍 🏆 Ліга Європи, 8-й тур ⚽️ #ДинамоРФШ ⏰ 22:00 (21:00 СЕТ) 🏟 Volksparkstadion 📺 MEGOGO

👍7

29 Jan 2025, 18:03 UTC668 views3 reactionsread 6 August 2026

Передматчева пресконференція головного тренера Олександра Шовковського та півзахисника Андрія Ярмоленка

❤3

29 Jan 2025, 17:33 UTC585 views3 reactionsread 6 August 2026
Photo

ℹ️ Георгій Бущан перейшов у клуб із Саудівської Аравії. 📑 Місцевий «Аль-Шабаб» провів успішні перемовини з нашим клубом щодо трансферу Бущана. Голкіпер пройшов медогляд в Ер-Ріяді, узгодив деталі особистого контракту та підписав угоду строком на 2,5 роки. 🔹 Відзначимо, що «Аль-Шабаб» виступає в елітному дивізіоні Саудівської Аравії. 🔹 Нагадаємо, 30-річний воротар всю професійну кар’єру провів у київському «Динамо»…

😭2❤1

23 Jan 2025, 14:48 UTC695 views1 reactionsread 6 August 2026
Photo

⏱ 90' – Матч завершено! Граємо внічию в товариській зустрічі з косоварським «Ллапі» 🤝 🇺🇦 Динамо 2️⃣:2️⃣ Ллапі 🇽🇰

🙏1

23 Jan 2025, 12:52 UTC680 views4 reactionsread 6 August 2026
Photo

🔷 Наш склад на гру з «Ллапі» 👊

👍4

23 Jan 2025, 12:51 UTC624 views3 reactionsread 6 August 2026
Photo

День матчу! ⚽️ Сьогодні «біло-сині» проведуть тренувальну гру на турецькому зборі 🆚 Ллапі, Косово ⌛️ 15:00 за Києвом 🏟 Kaya Palazzo stadium ⏯️ Трансляція на YouTube

👍2👌1

21 Jan 2025, 17:27 UTC670 views18 reactionsread 6 August 2026
Photo

⏱ 90+5' – Матч завершено! 💪 Шалений камбек у Стамбулі. Граємо внічию з «Галатасараєм» у 7-му турі Ліги Європи ⚽️ Гол Ваната та дубль Ярмоленка приносять один бал в скарбничку!

🔥18

21 Jan 2025, 14:30 UTC572 views1 reactionsread 6 August 2026
Photo

💙 Наш склад на матч з «Галатасараєм» 👊

👍1

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

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

“ФК Динамо Київ” (@fcdynamokyiv), 681 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/fcdynamokyiv.

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.