Channel
@holyurta
On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry
1subscribers
-389 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001821074138 |
|---|---|
| Type | Channel |
| Username | @holyurta |
| Created | Between 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 26 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 26 August 2026 |
| On Telegram | t.me/holyurta |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Aug 2026, 04:02 | 1 | -396 |
| 18 Aug 2026, 07:42 | 397 | +7 |
| 10 Aug 2026, 04:45 | 390 | no change |
| 10 Aug 2026, 04:31 | 390 | first reading |
11 posts held, back to 18 July 2026 — 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 7 August 2026 |
|---|---|
| Posts held | 11 (18 July 2026 – 7 August 2026) |
| Views total | 409 |
| Reactions total | 174 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Aug 2026, 04: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.
545 reactions across 11 posts, in 4 distinct kinds. The most used accounts for 45.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5312060249417469737 | 246 | 45.1% | |
| custom 5321455597751656390 | 145 | 26.6% | |
| custom 5312253699039448519 | 103 | 18.9% | |
| custom 5319214075794708259 | 51 | 9.36% |
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 11 of the 11 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 545reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 18 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @holyurta. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 11 most recent posts we hold for this entry, published 18 July 2026 to 7 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
как то раз еще в феврале я сильно осмелела, вытащив айпад в маршрутке словила долю зевак тревожности и больше так не делала
custom 531206024941746973732custom 532145559775165639013custom 531921407579470825911
тотальный чилл
custom 531206024941746973741custom 531225369903944851916custom 532145559775165639011custom 53192140757947082594
новый виток срача вокруг «ии-художников», уместности ии в творчестве, монеточки и вот этого всего доводит меня до тиков и желания выбросить нахер телефон и больше не быть онлайн никогда чтобы не видеть и не знать о деградации общества примерно ничего буду просто рисовать на бумажке и выгуливать черепашку. возможно откачусь назад и как предки буду рисовать на скальных породах угольком
custom 531206024941746973732custom 53122536990394485198custom 53214555977516563906
я думаю о верстке скетчбуковорот зина но не представляю как это все соединять, учитывая что везде разную бумагу использовала для вклейки и оно на сканах оооочень отличается и рябит в глазах некоторые развороты на скане вообще оч сильно ломало и я их даже не выкладывала много думаю короче
custom 531206024941746973732
фаенон как бы между прочим затесался
custom 531206024941746973751custom 531225369903944851918custom 532145559775165639013custom 53192140757947082595
Видео про СКЕТЧБУКОВОРОТ уже на канале! Приятного просмотра :З 🔴 смотреть на Ютубе 🔵 смотреть в ВК
custom 531206024941746973716custom 53122536990394485198
всем смотреть и оценивать масштабы нашего челленджа в видосе наты!! ✌️ я немножко позже тоже запишу листалку чтобы вы оценили что мне рисовали другие художницы!
custom 531225369903944851924
вспомнила что не все майские скетчи постила поэтому с поутихшим хайпом оставляю тут
custom 532145559775165639038custom 531206024941746973715custom 531921407579470825911custom 53122536990394485193
Рисую тут потихоньку деток подружек. И первой появилась Черепашка Луша!💜
custom 531206024941746973714custom 532145559775165639010
фандом имени моего динозаврика как мы себя чувствуем
custom 531206024941746973713
к еще одной художнице вернулся ее бук, а это значит я могу показать свои развороты! рисовалось в марте, поэтому там тематический разворот с орлеанской девой и чудесным праздником (не о цветах). ну и аватар, куда без него
custom 532145559775165639054custom 531225369903944851926custom 531921407579470825920
Showing the 11 most recent of 11 posts we hold for @holyurta. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Citation-graph rank — 437,254 of 1,624,174entries 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 1 registered channel — 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.
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 26 August 2026 — this entry's latest reading, not the date you are reading this.
“holyurta” (@holyurta), 1 subscribers as measured 26 August 2026. Telegram Register, tgregister.com/channel/holyurta.
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.