Telegram RegisterThe public register of Telegram
Telegram profile photo for Уголок Ситха

Channel

Уголок Ситха

@Ugolok_Sitha

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Referenced elsewhere · Cite this entry

49,748subscribers

-138 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001459051914
TypeChannel
Username@Ugolok_Sitha
Created12 February 2021measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live16 August 2026
Measurements held12
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/Ugolok_Sitha

Growth

49,74849,88649,8176 August 2026 — 49,886 subscribers6 August 2026 — 49,886 subscribers6 August 2026 — 49,877 subscribers7 August 2026 — 49,856 subscribers8 August 2026 — 49,841 subscribers9 August 2026 — 49,828 subscribers10 August 2026 — 49,817 subscribers11 August 2026 — 49,790 subscribers12 August 2026 — 49,775 subscribers13 August 2026 — 49,772 subscribers14 August 2026 — 49,764 subscribers16 August 2026 — 49,748 subscribers6 August 202616 August 2026
12 measurements spanning 10 days, net -138. 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 49,727–49,907 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 08:5349,748-16
14 Aug 2026, 18:1549,764-8
13 Aug 2026, 11:1649,772-3
12 Aug 2026, 13:3349,775-15
11 Aug 2026, 13:3649,790-27
10 Aug 2026, 10:0249,817-11
9 Aug 2026, 13:1149,828-13
8 Aug 2026, 14:2149,841-15
7 Aug 2026, 11:2049,856-21
6 Aug 2026, 11:2149,877-9
6 Aug 2026, 01:4649,886no change
6 Aug 2026, 01:1449,886first reading

Engagement

17 posts held, back to 2 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 23 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
11.4%
avg views ÷ 49,748 subscribers
Avg views / post
5,660
17 posts measured
Reaction rate
1.90%
reactions ÷ views · ER floor
Posts in window
17
of 17 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 14 August 2026
Posts held17 (2 August 202614 August 2026)
Views total96,267
Reactions total1,831
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Aug 2026, 02:32 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
5m 28s
Average length
47s

Measured directly from 7 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,831 reactions across 17 posts, in 8 distinct kinds. The most used accounts for 37.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍68337.3%
56230.7%
🔥30516.7%
👏1367.43%
🫡1226.66%
😱90.492%
👎80.437%
😢60.328%

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

Measured over the 17 most recent posts we hold, published 2 August 2026 to 14 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

14 Aug 2026, 17:25 UTC≈2,420 views118 reactionsread 16 August 2026
Forwarded from @ImpNavigatorPhoto

Иранский КСИР сообщил, что их комплекс ПВО сбил сегодня еще один американский разведывательно-ударный БПЛА MQ-9A Reaper вторгнувшийся в воздушной пространство над иранской провинцией Хормозган (находится у Ормузского пролива). На фото обломки сбитого MQ-9A. Получается это уже 46-й потерянный США в войне с Ираном Reaper, с учетом вчерашних данных.

👏69👍34🔥141

13 Aug 2026, 17:49 UTC≈3,210 views86 reactionsread 16 August 2026
Forwarded from @uac_ruVideo

✈️Делимся кадрами перелета МС-21 из Иркутска в Жуковский ▶️

👍5625🔥5

13 Aug 2026, 09:05 UTC≈3,160 views122 reactionsread 16 August 2026
Forwarded from @ChDambievVideo

Проход пары штурмовиков Су-25 эскадрильи "Монгольский арат" ВКС России на предельно малых высотах на учениях "Селенга-2026" в Монголии.

🔥7135👍16

13 Aug 2026, 06:01 UTC≈11,600 views125 reactionsread 16 August 2026
Photo

Доброе утро

60👍42🔥13🫡8👏2

12 Aug 2026, 15:17 UTC≈11,300 views149 reactionsread 16 August 2026
Photo

Z - в зоне проведения Специальной Военной Операции #z_сво

👍7042🫡25🔥11👎1

12 Aug 2026, 13:40 UTC≈3,460 views96 reactionsread 16 August 2026
Forwarded from @AviaCTVideo

🇹🇷 Турецкий F-16 потерпел крушение во время тренировочного полёта Истребитель F-16 ВВС Турции потерпел крушение в провинции Ялова во время тренировочного полёта. По данным Министерства национальной обороны Турции, пилот успел катапультироваться и выжил. «Один из наших самолетов F-16 потерпел крушение во время учебного полета в Ялова, и наш пилот катапультировался и выжил. Причины аварии пока неизвестны. В ведомст

👍69🔥22😱32

12 Aug 2026, 07:50 UTC≈3,670 views123 reactionsread 16 August 2026
Photo

Хроники СВО. #сво

58🔥36👍18🫡11

12 Aug 2026, 05:42 UTC827 views42 reactionsread 12 August 2026
Photo

Фронтовое везение #хроники_сво #дроны

👍20🔥9🫡8😱41

11 Aug 2026, 07:16 UTC≈2,200 views72 reactionsread 12 August 2026
Forwarded from @stormdronPhoto

Наземные роботы «Курьер» на учениях в Таджикистане Военнослужащие войск беспилотных систем 201-й российской военной базы приступили к отработке тактики применения наземных робототехнических комплексов (НРТК) «Курьер» на горном полигоне «Ляур». Операторы осваивают дистанционное управление НРТК «Курьер» в условиях сложного рельефа. В зависимости от задачи на НРТК «Курьер» монтируют пулеметы ПКТ, «Утес» или гранатомет

33🔥19👍11👏6👎3

7 Aug 2026, 10:05 UTC≈4,380 views108 reactionsread 12 August 2026
Forwarded from @The_Wrong_SideVideo

🔥 Поражение железнодорожного эшелона с боевой техникой ВСУ с применением ОТРК "Искандер" и БпЛА "Герань" в районе н.п. Вишневое Днепропетровской области. ©️ Наш канал 🗣 Наш чат 🔝 Проголосовать за канал

🔥60👍33👏112👎2

6 Aug 2026, 10:30 UTC≈4,950 views88 reactionsread 12 August 2026
Forwarded from @AviaCTPhoto

🇺🇸 XQ-58 Valkyrie разбился в Юте во время испытательного полёта Испытания одного из самых перспективных американских боевых беспилотников закончились аварией. XQ-58 Valkyrie компании Kratos разбился вскоре после взлёта на полигоне Dugway Proving Ground в штате Юта. Никто не пострадал, но лётные испытания временно приостановлены до завершения расследования. По неподтвержденным данным разбившийся XQ-58 был беспилотни

👏48👍304🔥4😱2

Showing the 12 most recent of 17 posts we hold for @Ugolok_Sitha. 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 — 8,896 of 1,481,217entries 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 16 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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Воин DV
@voin_dv · 147,278
Telegram ranks this channel #47 of 79 here — alongside 78 others — read 13 August 2026
Работайте, братья!
@btr80 · 146,785
Telegram ranks this channel #60 of 77 here — alongside 76 others — read 13 August 2026

This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

Referenced elsewhere

This handle named by sources this register does not control and did not measure — each shown exactly as found, attributed by name, dated to when it was read.

Hacker News

This handle was named once in a Hacker News comment or story, via the public Algolia search API. HN comment and story text has no confirmed reuse licence, so nothing quoted from either is reproduced here — only that a mention exists, when, and by whom, with a link to read it at the source.

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.

“Уголок Ситха” (@Ugolok_Sitha), 49,748 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/Ugolok_Sitha.

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.