Channel
@oniks0vv
On this record: Previous handles · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,051subscribers
+43 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1004423777943 |
|---|---|
| Type | Channel |
| Username | @oniksovv0 |
| Created | Between 1 June 2026 and 7 August 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/oniks0vv |
@oniks0vv was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 13:58 | 1,051 | +29 |
| 9 Aug 2026, 18:46 | 1,022 | +14 |
| 8 Aug 2026, 00:33 | 1,008 | no change |
| 7 Aug 2026, 21:48 | 1,008 | first reading |
26 posts held, back to 7 August 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 2 pagesof 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. It is computed over the 23 of 26 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 9 August 2026 |
|---|---|
| Posts held | 26 (7 August 2026 – 9 August 2026) |
| Views total | 1,360 |
| Reactions total | 215 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 18:46 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.
215 reactions across 23 posts, in 7 distinct kinds. The most used accounts for 23.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5445036259422540713 | 50 | 23.3% | |
| custom 5319152172431064681 | 47 | 21.9% | |
| custom 5389049470933558167 | 43 | 20.0% | |
| custom 5452099766932493325 | 32 | 14.9% | |
| custom 5445175884514368752 | 22 | 10.2% | |
| custom 5442965544019994851 | 17 | 7.91% | |
| custom 5454392274446209617 | 4 | 1.86% |
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 23 of the 26 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 215reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 26 most recent posts we hold, published 7 August 2026 to 9 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.
✦ Фоны Элли Автор: @sefi_ksss
custom 53191521724310646812custom 53890494709335581671custom 54450362594225407131custom 54451758845143687521custom 54520997669324933251
Signed 𝚂𝚎𝚏𝚒#чортфанаткафаворитки🩵
🔹🔹🔹🔹 🔹🔹🔹🔹 #пустые #сп #фон автор: @fanlovecbb
custom 53890494709335581675custom 54520997669324933254custom 54450362594225407133custom 53191521724310646812custom 54451758845143687521
Signed ~𝕕𝕠𝕟𝕒𝕥𝕖𝕣𝕤𝕙𝕜𝕒 ℂ𝔹𝔹/♡~
Попрошу реакции
custom 53890494709335581671
Signed Сырник #imhiv #фанфанаткиуу #фанатди
🌟🌟🌟🌟🌟🌟🌟 🌟🌟 ⚪️⚪️⚪️💜 1. 100⭐️ 2. 50⭐️ 3. 25⭐️ подписки сюда: @CherStra3 @nayashka_chBB @fan_princessa @XLL_ass резы:120
custom 54451758845143687521custom 54520997669324933251
Signed ониксов #imhiv
конкурс на 50 зв @kedovka резы:????
custom 54450362594225407131
Signed ониксов #imhiv
за 4-5 дней сможете добить 2 конкурса?
custom 53191521724310646811
Signed ониксов #imhiv
Эффи܁ ── ⋆⋅☆⋅⋆ ── ╰➤ #эффи #домзалесом #фоны #фоныотсырника ── ⋆⋅☆⋅⋆ ── если берете материал, отмечайте источник!
custom 53890494709335581676custom 54451758845143687523custom 53191521724310646812custom 54450362594225407132custom 54520997669324933252
Signed Сырник #imhiv #фанфанаткиуу #фанатди
🩵🌸🌸🌸🌸 🩵🌸🌸🌸🌸 🩵🌸🌸🌸🌸 🩵🌸🌸🌸🌸 🩵🌸🌸🌸🌸 🩵🌸🌸🌸🌸🌸 🩵🌸🌸🌸🌸 🩵🌸🌸🌸🌸 #парочки #дзл #тр автор: @fanlovecbb
custom 53191521724310646815custom 54450362594225407134custom 54451758845143687523custom 53890494709335581672custom 54520997669324933252
Signed ~𝕕𝕠𝕟𝕒𝕥𝕖𝕣𝕤𝕙𝕜𝕒 ℂ𝔹𝔹/♡~
тут фонобатл
custom 53191521724310646811
Signed ониксов #imhiv
🤩🤩🤩 🤩😀😀😀🥰🤩🤩 ➖➖➖➖➖➖➖ 🤩🤩🤩 автор: @fanlovecbb
custom 54429655440199948516custom 53890494709335581674custom 54451758845143687522custom 54520997669324933252custom 53191521724310646811custom 54543922744462096171
Signed ~𝕕𝕠𝕟𝕒𝕥𝕖𝕣𝕤𝕙𝕜𝕒 ℂ𝔹𝔹/♡~
Элли . ܁₊ ⊹ . ܁ ⟡ ܁ . ⊹ ₊ ܁ ── ⋆⋅☆⋅⋆ ── ╰➤ #элли #темноерождество #фоны #фоныотсырника ── ⋆⋅☆⋅⋆ ── если берете материал, отмечайте источник!
custom 53191521724310646814custom 53890494709335581673custom 54543922744462096173custom 54429655440199948512custom 54451758845143687522custom 54450362594225407131custom 54520997669324933251
Signed Сырник #imhiv #фанфанаткиуу #фанатди
люблю вас ,ониксинки я сегодня утром поеду на дачу шашлыки жарить и тд ,поэтому хз когда приеду но перед тем как буду уезжать ,напишу🤩
custom 53890494709335581671
Signed ониксов #imhiv
Showing the 12 most recent of 26 posts we hold for @oniks0vv. 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 — 272,482 of 1,176,251entries 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.
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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“ониксов” (@oniks0vv), 1,051 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/oniks0vv.
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.