Telegram RegisterThe public register of Telegram
Telegram profile photo for ️ФК Финсистемс

Channel

️ФК Финсистемс

@finsystems1

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

332subscribers

+0 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-1001878090497
TypeChannel
Username@finsystems1
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 live6 September 2026
Measurements held5
Confirmed unchanged2 times, most recently 6 September 2026
On Telegramt.me/finsystems1

Growth

331334332.57 August 2026 — 332 subscribers7 August 2026 — 332 subscribers13 August 2026 — 334 subscribers21 August 2026 — 331 subscribers29 August 2026 — 332 subscribers3327 August 202629 August 2026
5 measurements spanning 22 days. 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 331–334 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 01:15332+1
21 Aug 2026, 19:34331-3
13 Aug 2026, 23:28334+2
7 Aug 2026, 18:01332no change
7 Aug 2026, 08:02332first reading

Engagement

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

Reaction mix

213 reactions across 17 posts, in 15 distinct kinds. The most used accounts for 48.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
10448.8%
🔥3014.1%
👍104.69%
😢94.23%
👏83.76%
😁83.76%
73.29%
❤‍🔥73.29%
🤗73.29%
🤣73.29%
🏆62.82%
👎52.35%
😇31.41%
custom 538212049897916623510.469%
👀10.469%

Custom emoji. One row above is a 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 count beside it is Telegram’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 213 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 16 July 2026 to 6 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
27
across the posts below
Posts paid on
11
of 20 we hold a reading for · 55%
Most on one post
8
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @finsystems1. 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 16 July 2026 to 6 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

6 Aug 2026, 07:03 UTC100 views7 reactionsread 7 August 2026
Forwarded from @pfcupVideo

Мы не могли обойти этого парня стороной. Иван Ломашев в пятёрке предварительных кандидатов на «Золотой мяч PFC 2026» 🌕 Минувший сезон выдался по-настоящему особенным для Ивана, ведь он стал настоящим лидером «Финсистемс»👌 Личная статистика: • 13 матчей • 15 голов • 8 ассистов Если Ваня приведёт свой клуб к долгожданному триумфу осенью, у него будут все шансы на победу в розыгрыше «Золотого мяча».

3👍3custom 53821204989791662351

5 Aug 2026, 07:33 UTC134 views5 reactions1 Starread 7 August 2026
Video

Что только не приходится терпеть ради встреч с хорошими людьми…

😁3👍2

4 Aug 2026, 18:39 UTC149 viewsread 7 August 2026
Video

Отключились на пару минут, и этого оказалось достаточно! Заканчиваем за счётом 2:2

4 Aug 2026, 17:17 UTC148 viewsread 7 August 2026

Первый тайм закончили со счётом 1:1 📱 Выходим на второй

4 Aug 2026, 17:09 UTC146 views10 reactionsread 7 August 2026
Photo

Лом и Тара обновили имидж в отпуске🤭 Как оценим?

7👍2👀1

4 Aug 2026, 16:58 UTC144 views1 reactionsread 7 August 2026
Video

Открываем счёт в матче🤩

1

4 Aug 2026, 16:46 UTC145 views4 reactions1 Starread 7 August 2026
Video

Если хотим в ноябре покупаться в черном море, то надо побеждать🤌 📱 Смотрим матч в прямом эфире

4

4 Aug 2026, 10:22 UTC155 views9 reactions8 Starsread 7 August 2026
Photo

Пауза окончена🥳 Ноги отдохнули, а родственники и близкие игроков уже начали думать, что теперь по выходным они всегда свободны🤭 Но нет! Успели соскучиться по футбольным полям, по эмоциональным качелям, по мячу, друг по другу (но это неточно) И сегодня начинаем свой футбольный марафон матчем на Чемпионате города✅ Увидимся в 19:45! Накидайте реакций, если вы тоже скучали по команде🫰🏽

❤‍🔥6🔥21

2 Aug 2026, 13:12 UTC165 views7 reactions1 Starread 7 August 2026
Photo

Сегодня поздравляем с Днём рождения Георгия Усачева! Желаем, чтобы в жизни всё складывалось так же легко, как любимое аниме смотрится за один вечер🤭 Пусть будет крепкое здоровье, побольше ярких побед, классных эмоций и поводов улыбаться! С твоим Днём , Жора!

🏆4🤣3

31 Jul 2026, 10:01 UTC214 views16 reactions1 Starread 7 August 2026
Video

Для нашего сегодняшнего именинника есть что-то получше, чем просто картинка А именно его победный гол в финале CFL🥳 Лёша, поздравляем тебя с Днём рождения! Желаем, чтобы прическа всегда стояла, мячи забивались только в чужие ворота и чтобы всегда был на позитиве! С др, кароч🍻

8🔥4👏2🏆1👎1

30 Jul 2026, 17:26 UTC230 views10 reactions1 Starread 7 August 2026
Photo

Совсем скоро мы возвращаемся на футбольные поля и снова будем пилить много контента А пока, если вдруг вы пропустили, пересмотрите снова одно из самых ярких событий этого лета - наша победа на CFL🏆 📱 Тем более, что мы подгрузили все выпуски в ВК Выпуск с группового этапа Выпуск с плей-офф и финала Неизданное

8👍1👏1

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

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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

“️ФК Финсистемс” (@finsystems1), 332 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/finsystems1.

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.