Telegram RegisterThe public register of Telegram
Telegram profile photo for Шведа Кругового

Channel

Шведа Кругового

@krivoyudar

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

2subscribers

+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-1002818688966
TypeChannel
Username@krivoyudar
DescriptionНовости Российского футбола и немного юмора
CreatedBetween 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live16 August 2026
Measurements held2
On Telegramt.me/krivoyudar

Growth

27 August 2026 — 2 subscribers14 August 2026 — 2 subscribers7 August 202614 August 2026
2 measurements spanning 6 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 1–3 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 01:352no change
7 Aug 2026, 18:222first reading

Engagement

20 posts held, back to 13 October 2025the 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.

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 8 November 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
4
Videos
3
Links
2

Lifetime counters from Telegram’s own channel header, read 14 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.

Video runtime
1m 16s
Average length
25s

Measured directly from 3 videos 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

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁1100.0%

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 1 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 1reactions 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 13 October 2025 to 8 November 2025, 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

8 Nov 2025, 12:22 UTC168 viewsread 14 August 2026

3-4-2-1 без мяча превращается в 5-4-1: Гайич и Круговой садятся в линию к трем ЦЗ, закрывая ширину против навесов «Динамо», тогда как Обляков опускается к опорным, чтобы перекрывать центральные коридоры. Состав выстроен под прагматичный контроль центральной зоны с быстрым выходом в контратаки через фланги и рывки Мусаева/Аллеррандро; главный ключ — мобильно закрыть переходные фазы и дать Облякову свободу в первой и

8 Nov 2025, 12:18 UTC165 viewsread 14 August 2026
Photo

Стартовый состав на матч против Махачкалинского Динамо

5 Nov 2025, 18:48 UTC101 viewsread 14 August 2026
Forwarded from @pfccskamoscowPhoto

Уступаем махачкалинскому «Динамо» в первом матче 1/4 Пути РПЛ. #ДинамоМхЦСКА ⚽️⚽️

31 Oct 2025, 20:38 UTC80 viewsread 14 August 2026

Ответы главного тренера ЦСКА на вопросы журналистов после матча – Чего не хватает Тамерлану Мусаеву для реализации своих моментов? – Ему нужно быть более спокойным и играть с уверенностью. Мусаев – отличный профессионал, он много работает, но в ментальном плане ему необходимо научиться успокаиваться, чтобы с хладнокровием забивать. Всю злость, которая может накопиться, нужно выплескивать на поле в позитивном ключе.

31 Oct 2025, 19:30 UTC49 viewsread 14 August 2026

https://t.me/poizaCSKA/62 Если вам не хватает хорошей музыки, welcome

31 Oct 2025, 18:03 UTC31 viewsread 14 August 2026
Photo

И так ЦСКА одержал спокойную победу забив по голу в обеих матчах. Ну а Кисляк и Круговым поставили меня на место своим голом. Шведа, срезка, вратарь даже дернуться не успел, шикарно! Из грустного это травмы Мойзеса и Алерандро. Завтра Зенит- Локомотив, а дальше в воскресенье Краснодар-Спартак. Хотелось бы две ничьи и тогда будет у нас, Локо и Краснодара по 30 очков. Ожидаем, хотелось бы пожелать всем хороших выходных

31 Oct 2025, 17:54 UTC22 viewsread 14 August 2026
Forwarded from @matchpremierVideo

ШВЕДА КРУГОВОГО – ЭТО НЕЧТО!! КАК ВЫРЕЗАЛ НА КИСЛЯКА!! @matchpremier

31 Oct 2025, 17:27 UTC34 viewsread 14 August 2026

https://t.me/udar_ejuke/6183 Абсолютно согласен, просто грустно. Хороший парень, но пора принимать решение Fired

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

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.

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.

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.

“Шведа Кругового” (@krivoyudar), 2 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/krivoyudar.

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.