Telegram RegisterThe public register of Telegram

Channel

Уральский Сектор | ФК «Урал»

@uralsektor

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

673subscribers

+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-1002357664380
TypeChannel
Username@uralsektor
DescriptionОдин город - одна команда! Фан сообщество футбольного клуба «Урал» и не только, болеем за Уральский спорт! Подписывайтесь, шмели. 🧡 Поддержать канал - https://t.me/boost/uralsektor
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/uralsektor

Growth

6737 Aug 2026, 19:19 — 673 subscribers8 Aug 2026, 02:33 — 673 subscribers7 Aug 2026, 19:198 Aug 2026, 02:33
2 measurements taken within a single day. 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 672–674 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 02:33673no change
7 Aug 2026, 19:19673first reading

Engagement

7 posts held, back to 28 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
36.0%
avg views ÷ 673 subscribers
Avg views / post
242
7 posts measured
Reaction rate
19.3%
reactions ÷ views · ER floor
Posts in window
7
of 7 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 5 August 2026
Posts held7 (28 July 20265 August 2026)
Views total1,694
Reactions total327
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 02:33 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

Photos
573
Videos
78
Links
58

Lifetime counters from Telegram’s own channel header, read 8 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
16s
Average length
16s

Measured directly from 1 video 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

327 reactions across 7 posts, in 11 distinct kinds. The most used accounts for 26.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 59970151097282124878626.3%
5918.0%
🔥4413.5%
😎3911.9%
custom 54336274175350739403611.0%
👏3310.1%
custom 5357107687484038897164.89%
🏆51.53%
😍51.53%
custom 599894511341221107030.917%
🥰10.306%

Custom emoji. 4 of the rows above are 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 counts beside them areTelegram’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 7 of the 7 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 327reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 7 most recent posts we hold, published 28 July 2026 to 5 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

5 Aug 2026, 08:09 UTC133 views37 reactionsread 8 August 2026
Photo

⚡️ Подготовка к домашнему матчу с «Уфой» идёт полным ходом. 🧡- нам нужны три очка! 📸 ФК УРАЛ

custom 5997015109728212487226😍5custom 54336274175350739404

4 Aug 2026, 09:32 UTC183 views35 reactionsread 8 August 2026
Photo

🥇 Фиксируем положение в Лиге. На данный момент имеем в своём активе семь очков, от лидера отставание пять очков. Все в наших силах!

19custom 59970151097282124878🔥5custom 54336274175350739403

2 Aug 2026, 10:51 UTC245 views53 reactionsread 8 August 2026
Video

⚡️ Обзор голов против «СКА». ↗️ Лига Pari

27🔥11👏10custom 59970151097282124873🥰1custom 54336274175350739401

2 Aug 2026, 10:07 UTC252 views52 reactionsread 8 August 2026
Photo

🇷🇺 ПОБЕДА! Скучно начали первый тайм, а во втором тайме просто задавили соперника. Дубль Мартина, Дебютная передача Берти и второй гол за «Урал» от Бокова - браво команда! МЫ - УРАЛ! 🧡

😎30custom 543362741753507394011custom 53571076874840388978custom 59970151097282124872custom 59989451134122110701

2 Aug 2026, 07:40 UTC235 views44 reactionsread 8 August 2026
Photo

🧡ДЕНЬ МАТЧА! ⚽️ Первая Лига, 4️⃣-й тур 🏟 Стадион «В.И Ленина» «СКА-Хабаровск» 🆚️ «Урал» ⏰️ Начало в 13:00 ЕКБ 🇷🇺

🔥26custom 54336274175350739409custom 53571076874840388978custom 59989451134122110701

31 Jul 2026, 12:58 UTC273 views50 reactionsread 8 August 2026
Photo

💪 Парни полностью в работе, а до следующего нашего матча остаётся всего 2️⃣ дня. Сыграем на выезде против «Ска». 🧡 - покажем как сильно мы ждём три очка. 📸 ФК УРАЛ

custom 599701510972821248732custom 543362741753507394087🔥2custom 59989451134122110701

28 Jul 2026, 13:50 UTC373 views56 reactionsread 8 August 2026
Photo

⚽️ Александр Коротков в команде недели 3-го тура Лиги Пари. 🧡 - Так держать, Саша! 📸 Советский спорт

👏23custom 599701510972821248719😎9🏆5

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

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

“Уральский Сектор | ФК «Урал»” (@uralsektor), 673 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/uralsektor.

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.