6 measurements spanning 22 days, net +8. 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 184–194 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
30 Aug 2026, 20:04
193
+3
23 Aug 2026, 13:09
190
+1
15 Aug 2026, 08:58
189
+3
8 Aug 2026, 20:53
186
+1
8 Aug 2026, 12:17
185
no change
8 Aug 2026, 10:02
185
first reading
Engagement
18 posts held, back to 13 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 page of Telegram’s post history, 20 posts per page.
ERR · 30 days
41.3%
avg views ÷ 193 subscribers
Avg views / post
79.8
4 posts measured
Reaction rate
7.85%
reactions ÷ views · ER floor
Posts in window
4
of 18 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 3 of 4 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 7 August 2026
Posts held
18 (13 July 2026 – 7 August 2026)
Views total
319
Reactions total
19
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
8 Aug 2026, 12:17 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 26s
Average length
29s
Measured directly from 3 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
109 reactions across 15 posts, in 4 distinct kinds. The most used accounts for 49.5% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
custom 5438415752019345406
54
49.5%
custom 5440896323266053996
26
23.9%
custom 5440646308924789288
23
21.1%
custom 5440373741710246593
6
5.50%
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 are Telegram’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 15 of the 18 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 109 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 13 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.
"just clips with cc and textures"
Я настолько хорошо закомпозил в последнем эдите, что типок на овнере фьюжена подумал, что это просто клипы с дертикамом.
Очко сгорело конкретно, но я теперь понимаю, что даже опытные эдиторы в глаза долбятся. А что говорить про простых людей, Ярик рэйдж эсс говорит правду, надо делать слайды.
Мне жоска нравится эдиты с картой глубины (Depth Map, я дословно перевел тип), думаю, что надо тоже что-нибудь сделать. Естественно, это не будет настолько простая работа, накидаю своих приколов, чтобы не выглядело скучно. 🤭
Меня еще забавляет как типы выделили это как отдельный стиль. Хз, но на кинуть эффект на дефолт нарезку - это не стиль имхо.
23:35 edited: Еще у меня состояние какое-то странное, физически хочу…
KETAMINA ✦ HYSILENS
ib: Samiya, Iluxha.aep
Tik Tok - https://vt.tiktok.com/ZS4yAyMTs/
YouTube - https://youtu.be/bIi0I8Dgep0
Insta* - https://www.instagram.com/p/DblEW4FsyFa/
✦ Проект данной работы ✦
потом
По всем вопросам: @sunixed
SNXD | #HonkaiStarRail #Hysilens #HSR #GMV
✦ Завтра эдит доделаю по-любому
Я вроде выздоровел, не до конца, но все же, так что надо доделывать, а потом сразу за следующий.
✦ А еще мой опинион по последним не особо приятным событиям, может кому интересно:
В кратце, это не обошло меня стороной, отлетело около пяти эдитов, но слайдов, так что не велика беда, от меня не убудет. Обидно только за правку с Нефер. Способами залива и какими-либо патчерами я впредь …
Как репостить эдиты в истории? Я такой шедевр увидел.
custom 54408963232660539961
Showing the 12 most recent of 18 posts we hold for @sunixedits. 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.
Forward network
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.
Mentions
Named by 7 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.
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.
Declared links
One URL this entry has put in its own public description, shown exactly as written there. A declaration, not a verified association — we measured that the description contained this text, and nothing more. It is not a claim that this entry owns, runs or is connected to whatever the link resolves to; a description is text anyone controls, and anyone can put anyone else’s URL into it. How this is measured.
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 30 August 2026 — this
entry's latest reading, not the date you are reading this.
“Nah, I am sunixed” (@sunixedits), 193 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/sunixedits.
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.