Telegram RegisterThe public register of Telegram

Channel

🍪 ࣪⊹ⲇⲟⲙυⲕ ⲥⲗⲁⲇⲟⲥⲧⲉύ ⊹ ࣪ 🍪

@oi_aeri

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

19subscribers

+0 since we began measuring on 12 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003940645457
TypeChannel
Username@oi_aeri
CreatedBetween 1 April 2026 and 1 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live12 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/oi_aeri

Growth

1912 Aug 2026, 06:31 — 19 subscribers12 Aug 2026, 22:13 — 19 subscribers12 Aug 2026, 06:3112 Aug 2026, 22:13
2 measurements taken within a single day. 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 18–20 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 22:1319no change
12 Aug 2026, 06:3119first reading

Engagement

18 posts held, back to 1 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 18 posts for this entry, the most recent from 24 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
6m 40s
Average length
2m 13s

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

18 reactions across 4 posts, in 4 distinct kinds. The most used accounts for 33.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💘633.3%
🦄633.3%
🍓527.8%
🆒15.56%

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 4 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 18reactions 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 1 June 2026 to 24 June 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.

Recent posts

24 Jun 2026, 07:11 UTC299 views8 reactionsread 12 August 2026
Photo

⋆⌯⌲݁⊹ ࣪ 𝕴nterview [ ֍ ] #interview ─── ⋆.๋ ˖۶ৎ⋆ ──────⋆۶ৎ˖ .๋⋆ ─── ᗩεրί [ ℑ٥นր ] | ݁˖ 𝓸𝓾𝓻 𝓫𝓸𝓸𝓼𝓽 ๋ 🍪 ꀤ оҕязᴀтᴇльно! ᴨоддᴇᴩжиᴛᴇ ʍоᴇ ʙидᴇо ᴧᴀйᴋоʍ и ᴋоʍʍᴇнᴛᴀᴩиᴇʍ!ʍне будᴇᴛ очᴇнь ᴨᴩияᴛно ʙидᴇᴛь ʙᴀɯу ᴀᴋᴛиʙноᴄᴛь нᴀ ᴋᴀнᴀᴧᴇ ─── ⋆.๋ ˖۶ৎ⋆ ──────⋆۶ৎ˖ .๋⋆ ─── 𝑻𝑻: @aeri_oi 𝑻𝑮 𝐍𝐚𝐢𝐫𝐢𝐧: @Nairin_off

💘3🦄3🍓2

23 Jun 2026, 14:49 UTC32 viewsread 12 August 2026

🐰: Как у вас делишки? Что делаете?

23 Jun 2026, 13:56 UTC29 viewsread 12 August 2026

🐰: Всем приветиик. Я наконец то домонтировала видео-интервью! Завтра выйдет

10 Jun 2026, 14:39 UTC61 viewsread 12 August 2026

🐰:: Кстати, друзьяшки, я уезжаю в лагерь.Меня этим летом много куда будут отправлять, так что, к сожелению, я наверное не смогу активничать

10 Jun 2026, 14:37 UTC58 viewsread 12 August 2026

🐰:: Вот кстати тут моё первое интервью с 2024 годаа

10 Jun 2026, 14:36 UTC54 viewsread 12 August 2026
Video

Интервью от Ami из группы Mireu ∆°•°∆°•°∆°•°∆°•°∆°•°∆°•°∆°•°∆°•°∆°•°∆ Что означает ваше название группы «Mireu»? •Почему ты поменяла псевдоним? И т.д мы сейчасти узнаем! ∆°•°∆°•°∆°•°∆°•°∆°•°∆°•°∆°•°∆°•°∆°•°∆ #leeteahee #leedaegyeong #интервью #ot1

3 Jun 2026, 08:35 UTC61 viewsread 12 August 2026

🐰:: Вообще ни одной анкеты на текстовое интервью. Не дело, надо исправлять💗

2 Jun 2026, 14:37 UTC55 viewsread 12 August 2026
Forwarded from @F1SH_SOLPhoto

ˎˊ˗ (🥹) 𝗫𝘪𝚊𝗻 𝘗𝗿𝚘∂.🍪 缝 ׁ 🎀🎀𝐀υׁ∂𝗶𝘁𝗂𑄜𝕟 🎀 ➿ 🌟 ➿ 𓏲𝆬 ➿ ִׄ 𝅄 ִ ℕ𝟏𝓿 ᵖᵉʳᶠᵉᶜᵗ ➿ 𝕆❸ 𝗃𐐫𝘂𝕣 🥹🥹𝐎𝟚 ა𑄜𝗹𝗈🎀🥹 🥹 👾ꪮꪮкιɛ...[🐾&🍪] 0⑵ 𝗀𝗋𑄜𝘂ρ🎀๏3͟͟͟͞͞͞ 𝗽ⱺ𝕣tׁ ִ🎀σ3͟͟͟͞͞͞ ꪮ𝒕hꫀ𝗿 ➿🎀➿🎀🌟🌟🎀➿🎀➿ 🥹. `ankɘta n rulɘs ın inʄɔ ᵎ 𝗕ꪮ𝕥 : @aud_xian_prodbot

Showing the 12 most recent of 18 posts we hold for @oi_aeri. 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

Citation-graph rank — 881,574 of 1,345,403entries 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.

Forward network

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.

Mentions

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.

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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“🍪 ࣪⊹ⲇⲟⲙυⲕ ⲥⲗⲁⲇⲟⲥⲧⲉύ ⊹ ࣪ 🍪” (@oi_aeri), 19 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/oi_aeri.

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.