Channel
@simakina1p
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
30subscribers
+0 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002013423691 |
|---|---|
| Type | Channel |
| Username | @simakina1p |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/simakina1p |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 19:01 | 30 | no change |
| 11 Aug 2026, 18:46 | 30 | first reading |
20 posts held, back to 10 August 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 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 28 July 2026 |
|---|---|
| Posts held | 20 (10 August 2025 – 28 July 2026) |
| Views total | 39 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Aug 2026, 19:01 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.
Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Euros have just kicked off, and we've won two out of our three group-stage matches with England, only losing to Spain. Today, we'll face my former national team in the Round of 16 — the team that developed me and helped shape my career. I wish them the best of luck! But England are the stronger side... 😉🏴
Signed ASS31
First trophy with the club, and the first in the FTKL league. Played a commanding match, recording 6 tackles and earning a rating of 8.2. Forza Santex 🇺🇸
Signed ASS31
Вырываем победу в матче с сложным соперником - Тяпом. На счету у меня победный гол на 84 минуте, и 6 отборов (4 отбора + 2 перехвата). Хорошая игра получилась, помогло интервью до матча! Hala Santex 🇺🇸
Signed ASS31
Стартовал 6 сезон ФТКЛ, прошли в Лигу Европы, но проиграли Неонстарсу. 1 тур так же начался, но Сантекс проиграл 2:1, я сделал в матче 4 отбора. За четыре матча - 9 отборов. Не густо. Надеюсь, в дальнейшем времени я и команда подправим статистику.
Signed ASS31
WORLD CUP 🔜🔜🔜
Signed ASS31
Кутаиси выиграл Салют 2:1 в 21 туре ФТКЛ. Отметился 6 отборами. Оценка 8.1, третья в команде. После сезона будет кое какая новость.
Signed Simakin
Выиграли Веену в 10 туре ФТКЛ со счётом 2:1. Я отметился 6 отборами, и получил оценку 8.5. Второй по оценке. МВП матча стал напарник по ЦЗ Зорик с оценкой 9.0. Чуть чуть не хватило (
Signed Simakin
Сегодня играем в плей-офф за 3 место против Вайперса. Желаем им удачи, борьба будет сложной, победит сильнейший! Forza Kutaisi
Signed Simakin
Недавно перешёл в Кутаиси из Дайсбурга. В 1/8 плей-офф отметился двумя отборами, на 1/4 не был выпущен. На 1/2 скорее тоже не буду выпущен, но я надеюсь что команда выйдет в финал!
Signed Simakin
Возможно, это мой последний сезон в Дайсбурге.
Signed Simakin
Моя статистика за 1 половину сезона в 4 сезоне ФТКЛ: 24 матча 78 отборов (88) 2 гола 0 ассистов 4 жк Скоро грядет к нам Чемпеонат мира в России, за сборную Италии. Смогу ли там показать лидерские качества?
Signed Simakin
Match day 🔜🔜🔜 Сегодня играем с Дримпулем. Надеемся на хороший результат, вчерашний результат нас не устроил!
Signed Simakin
Showing the 12 most recent of 20 posts we hold for @simakina1p. 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.
Citation-graph rank — 945,521 of 1,176,251entries 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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“Мнение и карьера Симакина” (@simakina1p), 30 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/simakina1p.
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.