Telegram RegisterThe public register of Telegram
Telegram profile photo for Крылья над Волгой

Channel

Крылья над Волгой

@fcks_smr

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

1,001subscribers

+78 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001866244413
TypeChannel
Username@fcks_smr
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live16 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/fcks_smr

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 19 September 2026 and assigned it the closest of 31 fixed categories, at 38% 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

9231,0019627 August 2026 — 923 subscribers7 August 2026 — 923 subscribers8 August 2026 — 930 subscribers16 August 2026 — 934 subscribers24 August 2026 — 973 subscribers1 September 2026 — 982 subscribers9 September 2026 — 989 subscribers16 September 2026 — 1,001 subscribers7 August 202616 September 2026
8 measurements spanning 40 days, net +78. 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 911–1,013 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 21:211,001+12
9 Sept 2026, 21:42989+7
1 Sept 2026, 11:02982+9
24 Aug 2026, 17:06973+39
16 Aug 2026, 08:05934+4
8 Aug 2026, 00:53930+7
7 Aug 2026, 10:32923no change
7 Aug 2026, 10:25923first reading

Engagement

17 posts held, back to 6 August 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 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 17 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

24 reactions across 9 posts, in 5 distinct kinds. The most used accounts for 70.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1770.8%
🔥28.33%
😁28.33%
🥰28.33%
👏14.17%

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

Measured over the 17 most recent posts we hold, published 6 August 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.

Recent posts

7 Aug 2026, 08:43 UTC77 viewsread 7 August 2026
Photo

💥 сегодня [первая пятница августа] Международный день пива (англ. International Beer Day)

Signed Даниил

7 Aug 2026, 08:02 UTC101 views3 reactionsread 7 August 2026

🎙️Никита Кокарев обратился к 🇹🇳Хазему Мастури [«Динамо» Махачкала]: — Хазем вставай! Дома VAR посмотришь! Попу простудишь — солнце зашло!

3

Signed Даниил

7 Aug 2026, 07:41 UTC65 views4 reactionsread 7 August 2026
Forwarded from @ArtKS_Samara

Posted without readable text

🔥21👏1

Signed Даниил

7 Aug 2026, 07:36 UTC105 views1 reactionsread 7 August 2026
Photo

📰 вот какие программки были на матчи «Крыльев Советов» на первых двух турах РПЛ в Москве

1

Signed Даниил

7 Aug 2026, 07:21 UTC108 viewsread 7 August 2026
Photo

🔝 «Спорт-Экспресс» опубликовал лидеров [оценка — топ10] РПЛ по позициям на поле: 6,25 Песьяков | Вр. 6,25 Чернов | ЦЗ 6,00 Бабкин | ЦЗ 6,00 Витюгов | ПЗащ 6,00 Костанца | Защ. 6,00 Рассказов | ПЗащ 5,75 Печенин | Защ.

Signed Даниил

7 Aug 2026, 05:59 UTC125 viewsread 7 August 2026
Photo

💥 а что за состав будет завтра? Попробуем угадать!

Signed Даниил

7 Aug 2026, 04:54 UTC141 views2 reactionsread 7 August 2026
Photo

💥 из года в год стартовый состав «Балтики» в Самаре повторяется

🥰2

Signed Даниил

7 Aug 2026, 04:48 UTC142 views1 reactionsread 7 August 2026
Photo

💥 Артём Чистяков — главный судья матча «Крылья Советов» — «Балтика» ⬇️ судейство в РПЛ 78 матчей в РПЛ 44 победы хозяев 16 ничьих 18 побед гостей 🇸🇱 Крылья Советов всего: +0 =1 –6 дома: +0 =1 –1 3 пенальти нам 1 удаление у нас 🍺 Балтику в РПЛ не судил ‼️ Чистяков судил «Крылья» также в ФНЛ (второй дивизион) и кубке России: 6 матчей и 6 побед Самары ‼️ В качестве главного судьи Артём обслуживал 11 матчей [не РПЛ]

1

Signed Даниил

7 Aug 2026, 02:44 UTC149 viewsread 7 August 2026
Photo

1️⃣ поражение потерпели «Крылья Советов» в десяти домашних матчах в 2026 году (+5=4–1, мячи 19–12). Огорчить волжан при самарской публике удалось только ЦСКА в Кубке России (5:2). ‼️ Кстати, в прошлом чемпионате «Крылья» уступили дома лишь два раза (+7=6–2, мячи 24–17), выступив на уровне «Краснодара» (+12=1–2, мячи 36–13), «Спартака» (+10=3–2, мячи 26–17) и «Рубина» (+7=6–2, мячи 17–12), но не дотянув до «Зенита» (+

Signed Даниил

7 Aug 2026, 02:23 UTC151 viewsread 7 August 2026
Photo

7️⃣ августа #день_в_истории ⬇️ Родился игрок команды: ➡️ Ненад Джорджевич 1989 — провёл 54 матча и забил 5 мячей ⬇️ в эту дату сыграны матчи: ❌0️⃣:2️⃣ Динамо Москва 2022 ❌1️⃣:2️⃣ Арсенал Тула 2021 ☑️0️⃣:0️⃣ Локомотив Москва 2011 ☑️0️⃣:0️⃣ Локомотив Москва 2010 ✅4️⃣:1️⃣ Олимпия Волгоград 2004 ☑️1️⃣:1️⃣ Локомотив Москва 1996 ✅3️⃣:1️⃣ Дружба Йошкар-Ола 1983 ☑️1️⃣:1️⃣ КАМАЗ 1993 ☑️1️⃣:0️⃣ Заря Луганск 1967 ☑️1️⃣:1️⃣ Ст

Signed Даниил

6 Aug 2026, 14:51 UTC185 viewsread 7 August 2026
Photo

📈 ждём прорыв 🇸🇱 в 🔝8️⃣ для начала… от Павла Сещенко — директора по коммуникациям ПФК «Крылья Советов»

Signed Даниил

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

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.

Mentions

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.

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.

ПФК «Крылья Советов»
@fckssamara_official · 37,727
Telegram ranks this channel #20 of 97 here — alongside 96 others — read 31 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list 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.

“Крылья над Волгой” (@fcks_smr), 1,001 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/fcks_smr.

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.