Channel
@fkr_39
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
4,019subscribers
+10 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001380695081 |
|---|---|
| Type | Channel |
| Username | @fkr_39 |
| Created | 4 August 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 7 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/fkr_39 |
Local community — 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 14 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 13:17 | 4,019 | +8 |
| 12 Sept 2026, 14:01 | 4,011 | +4 |
| 8 Sept 2026, 08:35 | 4,007 | +2 |
| 2 Sept 2026, 18:29 | 4,005 | -4 |
| 30 Aug 2026, 18:24 | 4,009 | -1 |
| 27 Aug 2026, 11:33 | 4,010 | -2 |
| 24 Aug 2026, 01:52 | 4,012 | -1 |
| 17 Aug 2026, 12:33 | 4,013 | +4 |
| 14 Aug 2026, 13:36 | 4,009 | -1 |
| 10 Aug 2026, 19:32 | 4,010 | +1 |
| 7 Aug 2026, 06:30 | 4,009 | no change |
| 7 Aug 2026, 06:24 | 4,009 | first reading |
5 posts held, back to 30 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 4 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 7 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
230 reactions across 5 posts, in 8 distinct kinds. The most used accounts for 60.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 138 | 60.0% | |
| 🔥 | 46 | 20.0% | |
| 👍 | 26 | 11.3% | |
| 👏 | 11 | 4.78% | |
| ❤🔥 | 3 | 1.30% | |
| 😐 | 3 | 1.30% | |
| 🆒 | 2 | 0.87% | |
| 🏆 | 1 | 0.435% |
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 230 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 30 July 2026 to 7 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.
Обеспечиваем безбарьерную среду Установили пандусы для маломобильных жителей на Московском проспекте, 116 и 120 в Калининграде. Они выполнены в соответствии с современными нормативами: имеют необходимую ширину, безопасный уклон и оборудованы поручнями. Пандус удобен для самостоятельного передвижения. 🛠️ Работы по капитальному ремонту фасадов этих домов выходят на финишную прямую. В течение августа завершим ремонт …
❤12👍8👏3🔥2🏆1
🎉 Установили первые дверные ручки нового типа Первые новые ручки появились в домах на Театральной, 14А и 14Б в Черняховске. Их изготовили по найденному историческому образцу. Двери здесь мы выполнили очень выразительными, с богатым декором, поэтому латунная ручка должна была не перетягивать внимание, а стать естественным продолжением архитектуры. Именно поэтому эти двери стали первыми обладателями новой историческо…
❤30🔥12👏8👍4😐3
#ходработ по капремонту фасадов в Калининграде 📍Киевская, 121-123 — фасад уже практически готов. Оштукатурили стены, восстановили обрамления окон, облицевали цоколь плиткой и установили новые двери. Сейчас оформляем откосы на входных порталах. 📍Киевская, 147-151 — монтируем основания под новые балконные плиты, штукатурим стены и восстанавливаем рустовку на углах здания. 📍К. Маркса, 51 — продолжаем штукатурные рабо…
❤25🔥8👍4🆒2
Приступили к капремонту фасада исторического дома на Красной, 3-5 в Калининграде Про #ходработ смотрите в видео 📹 ❤️ Подписывайтесь на ФКР
❤42🔥13👍5
👀 Вам кажется, что за вами наблюдают? Возможно, так и есть... На фасадах старинных домов нередко можно встретить каменные лица, которые внимательно следят за жизнью города. Эти каменные «наблюдатели» называются маскаронами. Ни один маскарон не создавался случайно. Архитекторы тщательно подбирали его форму и выражение лица, чтобы подчеркнуть назначение здания, статус владельца или особенности архитектурного стиля. …
❤29🔥11👍5❤🔥3
Showing the 5 most recent of 5 posts we hold for @fkr_39. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 13 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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.
“Фонд капремонта КО” (@fkr_39), 4,019 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/fkr_39.
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.