Telegram RegisterThe public register of Telegram
Telegram profile photo for Армейский кругозор

Channel

Армейский кругозор

@armykrugozor

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

3,096subscribers

+2 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001941608764
TypeChannel
Username@armykrugozor
Created26 May 2023measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live16 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/armykrugozor

Growth

3,0943,0983,0966 August 2026 — 3,094 subscribers7 August 2026 — 3,094 subscribers10 August 2026 — 3,097 subscribers13 August 2026 — 3,098 subscribers16 August 2026 — 3,096 subscribers6 August 202616 August 2026
5 measurements spanning 10 days, net +2. 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 3,093–3,099 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 18:033,096-2
13 Aug 2026, 04:583,098+1
10 Aug 2026, 11:483,097+3
7 Aug 2026, 05:153,094no change
6 Aug 2026, 21:473,094first reading

Engagement

21 posts held, back to 27 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 3 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
30.0%
avg views ÷ 3,096 subscribers
Avg views / post
928
21 posts measured
Reaction rate
1.54%
reactions ÷ views · ER floor
Posts in window
21
of 21 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 20 of 21 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 7 August 2026
Posts held21 (27 July 20267 August 2026)
Views total19,487
Reactions total289
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 23:58 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 54s
Average length
57s

Measured directly from 2 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

289 reactions across 20 posts, in 7 distinct kinds. The most used accounts for 39.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
11439.4%
👍11038.1%
😁4114.2%
👏155.19%
🔥41.38%
👎31.04%
🤔20.692%

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

Measured over the 21 most recent posts we hold, published 27 July 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, 17:35 UTC256 views7 reactionsread 7 August 2026
Forwarded from @cskamoscowcultureVideo message

Video message, posted without a caption

7

4 Aug 2026, 20:11 UTC720 views31 reactionsread 7 August 2026
Photo

Тренерскому штабу надо поработать над концовками матчей, опять просели и соперник был заметно лучше. В остальном - тотальное преимущество ЦСКА и куча нереализованных моментов. И вместо уверенной победы в основное время получаем серию пенальти. Бориско, как по мне, сыграл очень уверенно. И мне бы хотелось его посмотреть в следующем официальном матче в РПЛ. Всё-таки с Тороп присутствует какая-то нервозность. Или нет?

👍237👎1

4 Aug 2026, 19:49 UTC702 views9 reactionsread 7 August 2026

Соперник еле живой, но мы опять сели в концовке. Есть вопросы к физике. И уже можно констатировать - замены пока тренерскому штабу не даются. Ни один из вышедших игроков не освежил или усилил игру, все тактические перестановки в молоко. Смотрим лотерею. Интересный дебют у вратаря ЦСКА. Верим!

👍9

4 Aug 2026, 18:38 UTC716 views6 reactionsread 7 August 2026

Когда игра - тягомотина без моментов, то стандарты - спасение. Не без удачи, но свой гол затолкали. Очень хочется, чтобы стандарты приносили всё больше пользы, тем более шансов в каждой игре достаточно. https://t.me/matchpremier/28871

👍6

4 Aug 2026, 16:51 UTC701 views7 reactionsread 7 August 2026
Photo

Дали игровую практику всем, кроме Бандикяна. Если тренер на него рассчитывает, то увидим его во втором тайме. По Кармо тренер уже говорил, что видит его только в качестве замены на уставшую защиту, когда он за счёт дриблинга может создать момент. Схема похожа на 4-4-2, где Алвес играет второго нападающего. Или всё-таки 4-2-3-1?

7

3 Aug 2026, 10:05 UTC764 views15 reactionsread 7 August 2026
Photo

Многие из нас заслуженно ругают нападающих за цифру 0 в графе забитые голы. Но кроме голов есть же и другие важные элементы игры, например, созданные голевые моменты. В прошедшем туре Лусиано стал лучшим по этому показателю, а значит он хорошо интегрирован в командную игру. Возможно, переход на схему в два форварда раскроет аргентинца? Когда в штрафной всё внимание будет не только на него, но и на второго нападающег

15

1 Aug 2026, 18:03 UTC990 views23 reactionsread 7 August 2026
Photo

Мы ругаем ЦСКА за реализацию моментов, но у нас хотя бы игра просматривается. Тут другая московская команда, с которой играть через несколько дней, вообще забыла в сезон войти. Так что не так уж всё и плохо у красно-синих.

😁176

1 Aug 2026, 16:03 UTC≈1,030 views11 reactionsread 7 August 2026
Photo

Да, счет не по игре и моментов было достаточно для победы. Но результат на табло, не смогли преимущество преобразоваться в три очка. Замены и перестановки не сработали, а вышедшие на поле игроки так и не попали в игру. Но главное, что сегодня увидели - центр поля без Баринова пока нравится больше. Возможно и стоило согласиться на предложение от греческого клуба... Армейский Кругозор в MAX

11

1 Aug 2026, 15:07 UTC821 views4 reactionsread 7 August 2026

Нет ощущения, что вышедшие на поле игроки какие-то вялые? Скоро игры заметно упала, много ошибок и Крылья бодрее? Но даже в таком пешеходном футболе у Мусаева был железный момент, который он благополучно запорол. Стоит признать, что такие шансы, судя по нарезкам, Жуан умудряется как-то реализовывать, так что везите его скорее. Армейский Кругозор в MAX

4

1 Aug 2026, 14:40 UTC782 views9 reactionsread 7 August 2026

Не успел с заменами Игдисамов, напрашивались они чуть раньше. Всё тяжелее выходили со своей половины поля, Крылья всё больше поддавливали. Меняют вингеров. В центре поля образуется тройка Баринов-Кисляк-Обляков. Козлов поднимается выше в атаку. Вот сейчас и сравним какое сочетание более эффективное. Армейский Кругозор в MAX

9

1 Aug 2026, 14:18 UTC758 views4 reactionsread 7 August 2026
Photo

Итоги первой половины игры. По статистике на свой гол наиграли точно. По ощущениям - так на два. Нравится, что много атак доводим до удара, чуть бы прицел ещё наладить. Соперник даёт играть, так что надо спокойно доводить игру до победы. Армейский Кругозор в MAX

4

1 Aug 2026, 14:08 UTC725 views11 reactionsread 7 August 2026

Правый фланг ЦСКА выделяется. Что Круговой, что Попович показывают отличный футбол в первых турах и записывают на свой счёт голевые действия. А вот на противоположном фланге откровенно выпадает Мойзес. И есть хотим увидеть Гайича на поле, то скорее вместо бразильца. Лусиано страшно не везёт. Вроде и делает всё правильно, но не идёт мяч в ворота. Так и в психологическую яму упасть можно, где уже давно обитает Мусаев.

11

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

Citation-graph rank — 858,870 of 1,548,671entries 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

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

Named by 3 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

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

“Армейский кругозор” (@armykrugozor), 3,096 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/armykrugozor.

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.