Telegram RegisterThe public register of Telegram

Channel

ФК «Держава»

@fcderzhava

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

331subscribers

+8 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001691338909
TypeChannel
Username@fcderzhava
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live14 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/fcderzhava

Growth

3233313277 August 2026 — 323 subscribers8 August 2026 — 323 subscribers14 August 2026 — 331 subscribers7 August 202614 August 2026
3 measurements spanning 7 days, net +8. 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 322–332 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 22:34331+8
8 Aug 2026, 07:30323no change
7 Aug 2026, 23:33323first reading

Engagement

20 posts held, back to 18 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
84.9%
avg views ÷ 331 subscribers
Avg views / post
281
8 posts measured
Reaction rate
2.24%
reactions ÷ views · ER floor
Posts in window
8
of 20 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 7 of 8 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 4 August 2026
Posts held20 (18 June 20264 August 2026)
Views total2,248
Reactions total45
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 07:30 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

Video runtime
1m 08s
Average length
1m 08s

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

89 reactions across 17 posts, in 14 distinct kinds. The most used accounts for 28.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2528.1%
custom 53435455938075216431112.4%
custom 49566562325689804781011.2%
custom 4956214478002717877910.1%
💘910.1%
🔥77.87%
❤‍🔥55.62%
custom 495630845618212175833.37%
custom 533230823707928898722.25%
custom 539559775416668296822.25%
👌22.25%
🙈22.25%
custom 545621826261222374811.12%
😍11.12%

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 17 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 89reactions 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 18 June 2026 to 4 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.

Telegram Stars

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

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @fcderzhava. 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 20 most recent posts we hold for this entry, published 18 June 2026 to 4 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.

Recent posts

4 Aug 2026, 10:58 UTC≈1,100 views10 reactions1 Starread 8 August 2026
Video

❤️❤️❤️❤️❤️ 🆕 Вы готовы? Уже через неделю мы примем участие в Х летней Универсиаде! И мы подготовили для Вас оригинальный анонс! 📆Расписание наших матчей: 9 августа 20:00 Республика Татарстан – Тамбовская область 10 августа 17:30 Республика Дагестан – Тамбовская область 11 августа 17:30 Ростовская область – Тамбовская область 12 августа Плей-офф 13 августа Матчи за места Впереди много всего интересного! Следи

custom 53435455938075216436custom 49562144780027178773custom 49566562325689804781

4 Aug 2026, 06:55 UTC113 views6 reactionsread 8 August 2026
Photo

🎁 День Рождения главного тренера - это важный праздник! Особенно, если это День Рождения Александра Викторовича Кудряшова! ☝️ Александр Викторович, спасибо за Вашу мудрость, стратегическое видение и умение раскрывать потенциал каждого игрока — благодаря Вам команда становится сильнее с каждым матчем. Желаем, чтобы тактические задумки всегда воплощались на поле, а каждый сезон приносил новые трофеи и поводы для гордо

custom 49563084561821217583custom 49566562325689804782custom 53955977541666829681

3 Aug 2026, 14:33 UTC114 views9 reactionsread 8 August 2026
Photo

🎆Вот Вы спросите - почему сегодня такой солнечный день впервые за долгое время? А все потому, что сегодня День Рождения у нашего атакующего полузащитника - Влада Конырева! 🎁 Желаем, чтобы рядом всегда были верные друзья и надёжная команда, которая поддержит и в победах, и в непростых матчах, и в жизни. Пусть здоровье будет крепким, мотивация — неугасающей, а впереди ждёт ещё множество ярких сезонов, трофеев и поводо

custom 49562144780027178775custom 49566562325689804782custom 53323082370792889872

2 Aug 2026, 17:47 UTC125 views5 reactionsread 8 August 2026
Photo

🛡 Волевая ничья в совершенно непростом матче против лидера турнирной таблицы - ФК «Токаревка» ⚽️Болей за ТГУ! 💙Бейся за «Державу»!

custom 49566562325689804783custom 53435455938075216431custom 54562182626122237481

31 Jul 2026, 06:59 UTC153 views7 reactionsread 8 August 2026
Photo

5️⃣6️⃣7️⃣8️⃣ В ЧЕМПИОНАТЕ ТАМБОВСКОЙ ОБЛАСТИ! 🌩Второй круг начинаем против самого грозного соперника в таблице - ФК «Токаревка»! 💪Будем стараться брать реванш! 😗 1 августа 14:30 ⛳️ г.Тамбов, стадион «Локомотив» ⚽️Болей за ТГУ! 💙Бейся за «Державу»!

custom 53435455938075216434custom 49562144780027178771custom 49566562325689804781custom 53955977541666829681

23 Jul 2026, 17:24 UTC193 views5 reactionsread 8 August 2026
Photo

Очень неприятное поражение в последнем матче 1 круга! Есть неделя, чтобы отдохнуть, набраться сил и продолжить свой путь в Чемпионате! ⚽️Болей за ТГУ! 💙Бейся за «Державу»!

🔥2🙈2custom 49566562325689804781

18 Jul 2026, 15:11 UTC241 viewsread 8 August 2026

▶️ ПРЯМОЙ ВИДЕОЭФИР 🖋Текстовая трансляция с онлайн-видео опасных моментов

17 Jul 2026, 07:02 UTC209 views3 reactionsread 8 August 2026
Photo

5️⃣6️⃣7️⃣8️⃣ В ЧЕМПИОНАТЕ ТАМБОВСКОЙ ОБЛАСТИ! 🥇Уже завтра битва за первое место в группе с ФК «Токаревка»! 😗 18 июля 18:30 ⛳️ г.Тамбов, стадион «Локомотив» ⚽️Болей за ТГУ! 💙Бейся за «Державу»!

🔥3

16 Jul 2026, 00:39 UTC179 views4 reactionsread 8 August 2026
Photo

Исправились за предыдущие матчи! Впереди важная игра! ⚽️Болей за ТГУ! 💙Бейся за «Державу»!

4

11 Jul 2026, 15:22 UTC218 viewsread 8 August 2026

▶️ Текстовая трансляция с онлайн-видео опасных моментов

11 Jul 2026, 09:52 UTC223 views5 reactionsread 8 August 2026
Photo

5️⃣6️⃣7️⃣8️⃣ В ЧЕМПИОНАТЕ ТАМБОВСКОЙ ОБЛАСТИ! 🌊Сегодня постараемся реабилитироваться после 2 ничьей с ФК «Маяк» 😗 11 июля 18:30 ⛳️ г.Тамбов, стадион «Локомотив» ⚽️Болей за ТГУ! 💙Бейся за «Державу»!

5

8 Jul 2026, 10:44 UTC197 views6 reactionsread 8 August 2026
Photo

3️⃣ Результат на «троечку»! Проводим работу над ошибками и готовимся к следующему матчу! ⚽️Болей за ТГУ! 💙Бейся за «Державу»!

2❤‍🔥2👌2

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

Citation-graph rank

Citation-graph rank — 580,088 of 1,480,688entries 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.

Forward network

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.

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

“ФК «Держава»” (@fcderzhava), 331 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/fcderzhava.

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.