Channel
@usadba_krakw
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
36subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003419031115 |
|---|---|
| Type | Channel |
| Username | @usadba_krakw |
| Created | Between 1 November 2025 and 17 November 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/usadba_krakw |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 22:45 | 36 | no change |
| 8 Aug 2026, 11:35 | 36 | first reading |
10 posts held, back to 17 November 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 30 July 2026 |
|---|---|
| Posts held | 10 (17 November 2025 – 30 July 2026) |
| Views total | 21 |
| Reactions total | 11 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Aug 2026, 22:45 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 10 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.
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.
154 reactions across 10 posts, in 7 distinct kinds. The most used accounts for 27.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5282943777059644742 | 42 | 27.3% | |
| custom 5215679757366089921 | 29 | 18.8% | |
| custom 5280808830421203835 | 26 | 16.9% | |
| custom 5346025469269517110 | 23 | 14.9% | |
| custom 5235835815547914930 | 12 | 7.79% | |
| custom 5386587088873331829 | 11 | 7.14% | |
| custom 5465465194056525619 | 11 | 7.14% |
Custom emoji. Every row above is a 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 10 of the 10 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 154reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 17 November 2025 to 30 July 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.
Так, а что тут у нас приехало? 😑 Наконец-то, получил своего 👨 Освободителя пустошей.) ————————————— Осталось найти свой Бойз-бэнд 😅 из команды 👨 и 👨 З.Ы. Хвоста на фотографиях нема, (но он есть)🦘, так как нужно сделать каркас⚔️ А заказывали через этого прекрасного человека))
custom 53865870888733318295custom 52808088304212038353custom 54654651940565256193
Вот и завершились 2⃣ дня ЭпикКона и пора бы уже вкратце описать свои ощущения.) Устали. Слегка запарились. Но это того стоило! Успел таки выскочить на сцену, чего не вышло на первый день) Огромное количество людей подходили и фотографировались, с некоторыми завязывался диалог про геншин и другие фандомы 👏 Всем участникам и посетителям огромное спасибо, это было действительно круто! 🔝 Друзьям и знакомым отдельный при…
custom 52156797573660899216custom 52829437770596447425custom 53460254692695171103
1⃣ день 😁😁😁😁 😁😁😊'a - успешно завершён.) Всем огромное спасибо, кто подходил, узнавал, фотографировался) А пока отдыхать - готовиться завтра ко 2⃣ дню.😭
custom 54654651940565256198custom 52358358155479149303custom 53865870888733318292
А тем временем, стартуем с моей дамой на BigFandom Night!) Решили вспомнить олдскул)) Сакура и Саске момент
custom 52829437770596447427custom 52808088304212038355custom 53460254692695171104
❗️😊😁😁😁😁❗️ Что ж, пора вернутся из паузы в косплее 👏 и сообщить Вам, что иду 4-5 июля на ЭпикКон в Дайнслейфе 🌠 #ЯидунаEpicCon #анонс
custom 52156797573660899217custom 52829437770596447425custom 52358358155479149303
❤️🤩🤩🤩🤩🤩 🤩🤩🤩 🤩 🤩🤩🤩🤩🤩🤩❤️ Посетили прекрасный #BigFandomNight в новогодних образах Сьюзи Кью и Джозефа Джостара, оттусили на славу 🤪 Было очень приятно увидеть старых знакомых, узнать новых людей и в целом пообщаться 🤪 #косплей #джоджо #джозефджостар #сьюзикью
custom 534602546926951711010custom 52808088304212038358custom 52829437770596447424
❄️🤩🤩🤩🤩🤩❄️ Уже в эту субботу буду на суперской тусе #BigFandomNight в образе Сьюзи Кью вместе со своим кавалером Джозефом 👁 Будем зажигать в предновогоднюю ночь, присоединяйся к нашему чаотик дуо 👁
custom 52358358155479149306custom 53460254692695171106custom 52829437770596447423
😁😁😁😁😊😁 Вот и настал момент делиться фотографиями со сцены.) слегка запоздало, конечно. Выглядим на фото, как модели с обложек журналов, сами не верили, что у нас такие позиционирования выходили идеальные в моменты. Огромной спасибо ещё раз всем, кто снимал, фотографировал)) Сердце было на взводе перед выходом.) P.S. этот дуэт навсегда в памяти у Zextenge и Dafnil
custom 52156797573660899214custom 52808088304212038354custom 52829437770596447424
#рофл Спасибо, Алику за этот заказ😄
custom 53865870888733318294custom 52156797573660899213custom 52829437770596447423
😁😁😁😁😁😁😁😊😁❗️ И всем приветики! Прикладываю второпях наше дефиле с Тогучи.) Немного уставшие, немного дрожащие от волнения, но мы сделали это!◻️◻️ Спасибо всем, кто пришёл поддержать, ребята) Светлячок - благодарю за репетиции, испытанные эмоции, вечера обсуждения и правок подачи заявки, запомним надолго) P.S. Ничего не взяли в победных номинациях, но не огорчились) Опыт и испытанные эмоции оказались важнее) P.S.S. Да…
custom 528294377705964474211custom 52156797573660899219custom 52808088304212038356
Showing the 10 most recent of 10 posts we hold for @usadba_krakw. 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 — 857,804 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 2 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.
Named by
Channels on the register whose posts name this channel's handle.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“Усадьба у Зекстэнджа” (@usadba_krakw), 36 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/usadba_krakw.
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.