7 measurements spanning 38 days, net +14. 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 19–37 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
16 Sept 2026, 10:42
35
+1
12 Sept 2026, 09:24
34
no change
9 Sept 2026, 00:58
34
+3
31 Aug 2026, 09:54
31
+7
25 Aug 2026, 04:17
24
+2
17 Aug 2026, 11:03
22
+1
9 Aug 2026, 20:32
21
first reading
Engagement
11 posts held, back to 1 September 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
154.3%
avg views ÷ 35 subscribers
Avg views / post
54.0
11 posts measured
Reaction rate
29.5%
reactions ÷ views · ER floor
Posts in window
11
of 11 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
Window
Rolling 30 days · latest post in window 11 September 2026
Posts held
11 (1 September 2026 – 11 September 2026)
Views total
594
Reactions total
175
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
12 Sept 2026, 09:24 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 57s
Average length
20s
Measured directly from 6 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
175 reactions across 11 posts, in 9 distinct kinds. The most used accounts for 28.0% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
custom 5238247263590957272
49
28.0%
custom 5248977105508647053
45
25.7%
custom 5312225949255741936
32
18.3%
custom 5445157648083199367
18
10.3%
custom 5242342974469191196
9
5.14%
custom 5350360328221782422
8
4.57%
custom 5471905858294134101
8
4.57%
custom 5238098180981147076
5
2.86%
custom 5467774507777277411
1
0.571%
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 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 175 reactions 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 1 September 2026 to 11 September 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.
Скучали? 😈
Шлем вам пламенный поцелуй с коротким видео с прошедшей
🍧 🌟🌟🌟🌟 🌟🌟🌟🌟🌟 🍧
Спасибо каждому, кто был с нами и сделал эту ночь незабываемой! 👍
И огромная благодарность нашему видеографу @white_moray!🍧
Твоя работа - это искусство!👍
Смотрим, вспоминаем и ставим реакции, если узнали себя! 🍧
инструкция, как сделать меня счастливой: переходим в тики ток, смотрим, лайкаем, комментируем, ссылочку копируем)))
а, ну и подписаться можно, так как совсем скоро будет много нового и интересного~
бойтесь... к октябрю будет не только Панти, но и Ада Вонг) а пока только закос из подручных материалов
(я забыла сдвинуть свои чëрные плинтусы, поэтому они режут низ фото, и композиция не та... но мне уже лень переделывать)
Showing the 11 most recent of 11 posts we hold for @barbariskkkkka. 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
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 September 2026 — this
entry's latest reading, not the date you are reading this.
“⋆ ˚｡⋆୨୧˚Barbari˚୨୧⋆｡˚ ⋆” (@barbariskkkkka), 35 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/barbariskkkkka.
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.
