аоаоа го пж✋✋
custom 52153671395815238661custom 54088747951587759631custom 54228267215419141331

Channel
@CENUAYUiNFO
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
380subscribers
+212 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003885322816 |
|---|---|
| Type | Channel |
| Username | @CENUAYUiNFO |
| Created | 11 February 2026 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/CENUAYUiNFO |
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 52% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 04:20 | 380 | +41 |
| 9 Sept 2026, 06:54 | 339 | +2 |
| 30 Aug 2026, 18:53 | 337 | +78 |
| 23 Aug 2026, 19:58 | 259 | +30 |
| 15 Aug 2026, 16:35 | 229 | +51 |
| 9 Aug 2026, 03:51 | 178 | +10 |
| 8 Aug 2026, 17:15 | 168 | first reading |
14 posts held, back to 11 February 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 14 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
1,015 reactions across 13 posts, in 8 distinct kinds. The most used accounts for 14.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5422826721541914133 | 150 | 14.8% | |
| custom 5424656828581574566 | 144 | 14.2% | |
| custom 5215367139581523866 | 139 | 13.7% | |
| custom 5215185479644770001 | 133 | 13.1% | |
| custom 5422694848866061927 | 122 | 12.0% | |
| custom 5422873888872758210 | 121 | 11.9% | |
| custom 5408874795158775963 | 114 | 11.2% | |
| custom 5422631674192101311 | 92 | 9.06% |
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 13 of the 14 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 1,015 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 11 February 2026 to 8 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.
аоаоа го пж✋✋
custom 52153671395815238661custom 54088747951587759631custom 54228267215419141331
(меня никто не знает и всем на меня похуй)
custom 54228267215419141332
Posted without readable text
custom 54228267215419141331
Sticker, posted without a caption
custom 54228267215419141333
резы тут https://t.me/rezeeCenyoyoy 🌞🌞
custom 54226316741921013119custom 54088747951587759631custom 54226948488660619271
ㅤ 🥹🥹😻🗝нтерактив от сени🤩🤩࿁𓈒 🤩🤩 ㅤкакая вы песня тнб ? 👍 условия ⬅️ 1. быть подписаным на @CENUAYUiNFO 2. рт в свой тгк / инфо 3. доки о рт ( сс на рт ) и свой юз моно шрифтом 15 / 15 🤩🤩 🍭ОТКРЫТО | закрытО
custom 54088747951587759639custom 54226948488660619277custom 54228267215419141335custom 52151854796447700014custom 54226316741921013113custom 54246568285815745663
04.08 🔠𝗽𝗮к между сеней & тишой з𝗮𝗸люч𝗲н 🥹 п𝗼здравля𝗲м молод𝗼жен𝗼в 💘
custom 542465682858157456620custom 521536713958152386615custom 521518547964477000112custom 54226948488660619279custom 54226316741921013118custom 54228267215419141338custom 54088747951587759636custom 54228738888727582106
😻😻🥹 мью / АН МЬЮ🍭 ࣪ 𔓕 папка
custom 521518547964477000122custom 521536713958152386616custom 542269484886606192716custom 540887479515877596313custom 542282672154191413312custom 542465682858157456611custom 54228738888727582105
пишите кого добавить😛😛
custom 542282672154191413329custom 542465682858157456621custom 521536713958152386620custom 542287388887275821015custom 521518547964477000114custom 540887479515877596314custom 542263167419210131114custom 542269484886606192714
ㅤ ㅤ ㅤ 𓈒 ۫ 🔠 𝗼𝘃𝗲 𝘭𝘪𝘴𝘵 ❤️𓈒ֺ𓂂 🌟порядок не имеет значения, всех люблю одинаково( ・ω・) чижик,псина,Ларисочка,мочи чан❤дайсуке,самурай,дверка,коп…
custom 542287388887275821029custom 542263167419210131123custom 542282672154191413321custom 521536713958152386617custom 521518547964477000115custom 540887479515877596315custom 542269484886606192715custom 542465682858157456615
ᩧ░𓈒۪۪۫𝘆𝗼𝘂𝗿 𝗼𝗽𝗶𝗻𝗶𝗼𝗻 𝗮𝗯𝗼𝘂𝘁 𝗺𝗲 😆𓈒 ֺ۪𓈒ֵ۫
custom 542282672154191413331custom 542269484886606192723custom 542287388887275821022custom 521518547964477000119custom 542465682858157456619custom 521536713958152386618custom 540887479515877596318custom 542263167419210131118
Posted without readable text
custom 542465682858157456629custom 542287388887275821025custom 521518547964477000124custom 521536713958152386619custom 542269484886606192719custom 540887479515877596318custom 542282672154191413318custom 542263167419210131117
Showing the 12 most recent of 14 posts we hold for @CENUAYUiNFO. 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 2 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.
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.
@CENUAYUiNFO named 1 handle 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“🎊🌈𓈒꫶ 𓏲𑪊υⲏⲫ𝗼 𝗰𝗲ⲏ︫︫︫︪υ(>⩊<) ! ⬦𑪆֑🍬✨” (@CENUAYUiNFO), 380 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/CENUAYUiNFO.
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.