Channel
@uc0ni
On this record: Topic · Previous handles · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
681subscribers
+539 since we began measuring on 26 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004368117520 |
|---|---|
| Type | Channel |
| Username | @uc0ni |
| Description | основная тема: гача правила — https://telegra.ph/pravila-gchkf-10-27 |
| Created | Between 1 June 2026 and 26 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 26 August 2026 |
| Last confirmed live | 9 November 2026 |
| Measurements held | 7 |
| On Telegram | t.me/uc0ni |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 22 September 2026 and assigned it the closest of 31 fixed categories, at 84% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
@uc0ni 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 |
|---|---|---|
| 9 Nov 2026, 12:22 | 681 | no change |
| 9 Nov 2026, 11:47 | 681 | +224 |
| 26 Sept 2026, 14:39 | 457 | +116 |
| 14 Sept 2026, 00:38 | 341 | +39 |
| 5 Sept 2026, 07:21 | 302 | +156 |
| 27 Aug 2026, 10:23 | 146 | +4 |
| 26 Aug 2026, 21:30 | 142 | first reading |
35 posts held, back to 26 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 pages of 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 11 of 16 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 November 2026 |
|---|---|
| Posts held | 35 (26 August 2026 – 7 November 2026) |
| Views total | 1,153 |
| Reactions total | 20 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Nov 2026, 12:22 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 9 November 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.
71 reactions across 25 posts, in 9 distinct kinds. The most used accounts for 26.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👻 | 19 | 26.8% | |
| custom 5289657438008525371 | 17 | 23.9% | |
| custom 5289721063654048010 | 11 | 15.5% | |
| ❤ | 10 | 14.1% | |
| custom 5244712379077394849 | 5 | 7.04% | |
| 🍓 | 4 | 5.63% | |
| 💋 | 3 | 4.23% | |
| custom 5463175967897844557 | 1 | 1.41% | |
| 💘 | 1 | 1.41% |
Custom emoji. 4 of the rows above are 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 25 of the 35 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 71 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 35 most recent posts we hold, published 26 August 2026 to 7 November 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.
Telegram’s own ‘edited’ marker: 0 of 16 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
❤️Блин!! Я так люблю Тугостей,но когда я хочу о них высказаться мне тычут в другие шипы..😣 ❤️Я нарисовал арт по ним,но негде поделиться!! ❤️Хочу дейлик по тугостям.. Знакомо??..тогда..❤️ [non-daily] ✨✨✨✨✨✨✨✨✨ ✨ ( @DailyTwoGuest ) ✨✨✨✨✨✨✨
👻1
Posted without readable text
👻1
ㅤㅤ𝅄︵꯭۫⏜۫ 𓏲࣪ ⟡ ♡ ⟡ 𓏲࣪ ⏜꯭۫︵𝅄 「 Welcome to... ୨ °^Азур & 1x1х1х1 blog ⌝• ୨ৎ ༄ ───────── ❈ ˚₊‧୨ — Хотите понаблюдать за персонажами в икее, но не можете найти блог? Тогда тебе к нам! — ˚₊‧୨ৎ‧₊˚Azure voice ✓• ~ αρⲅχχ.... 1χ1χ1χ1 ⲅ∂е мы чеρτ вσзьмυ?! ───────────────── ˚₊‧୨ৎ‧₊˚1x1 voice —𑀐α ησмσλчμ τы!𑀐αύ понять я что это ӡα mεsτσ. ───────❈───────── ༄ ᯾navigation !! Идея взята у блога @noobguest3008 !!
👻1
Рт пост ➿➿➿➿➿ 🌟 🌟 ➿➿➿➿➿➿➿➿➿ — Я тут нарисовал... Ту-тайма и Мерфир спавна вместе, но меня закидают помидорами за это!! 🌟 ➿친절🫧 ⟡ ˚🫧 ໒꒰ྀི´ ˘ ` ꒱ྀིა 🫧 !! . ୨୧➿ — Я такой крутой косплей сделал на Скитллза, негде показать 🤩 ➿૮꒰ ៸៸ ꒱১ 💖 ° 💖𓂃ㅤ꒰ ので ꒱🍓ㅤ ⊹➿ — Я записал прикольный момент с ними, хочу поделиться этим ➿ཐི ִִ۫𝆬 🦢 ׄ ׁ 𔔁 ֪ ૮꒰ྀི ៸៸ ꒱ 𝂅ׄ . ۫ 𔘘꯭͡ 👡 𝆬 ִׄ𝆹𝅥 𝅄 ִ➿ Были такие проблемы? То…
👻1
💚💚😀😀😀😀😀😀😀😀 🌟 - Блин( не могу найти бота с любимым персонажем.. 🗝➿➿➿➿➿➿➿➿➿ 🌟 - Почему везде только английские боты? ㅤㅤ🌟🌟🌟🌟🌟🌟🌟🌟🌟 🔠накомо? 🤩🤩Добро пожаловать в... 🤩🤩 ·Forsaken C. Ai· 🤩🤩 ︎︎ㅤㅤㅤ🤩.🤩.🤩.🤩.🤩.🤩.🤩 У нас вы можете найти ботов с любимыми персонажами на русском!! Ждём вас! #РтПост
👻1
какте самые НАГЛЫЕ гачеры были вообще в фд? Или каких помните выыы неанон other34 #тейк ≧≦ @uc0ni
👻1
Sticker, posted without a caption
Как развить канал с нуля? Ии как поднять актив? Был бы очень рад годным советам #тейк ≧≦ @uc0ni
👻5💋1
к слову ваши нелюбимые гачеры в тт #тейк ≧≦ @uc0ni
👻1
продам тгк, цену обговорим. пока никто не купит, буду вести.
условно, у меня плохо ловит впн ❤❤
как вы относитесь к гачерам, которые специально навязываются к популярным #тейк ≧≦ @uc0ni
Showing the 12 most recent of 35 posts we hold for @uc0ni. 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.
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.
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.
@uc0ni named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 9 November 2026 — this entry's latest reading, not the date you are reading this.
“xsetter: ㅤㅤ” (@uc0ni), 681 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/uc0ni.
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.