Telegram RegisterThe public register of Telegram
Telegram profile photo for alicenoi

Channel

alicenoi

@oumanoe

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

356subscribers

-2 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1003259521344
TypeChannel
Username@oumanoe
CreatedBetween 1 October 2025 and 31 January 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live19 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/oumanoe

Growth

356427391.510 August 2026 — 358 subscribers11 August 2026 — 385 subscribers18 August 2026 — 427 subscribers25 August 2026 — 399 subscribers1 September 2026 — 383 subscribers10 September 2026 — 369 subscribers19 September 2026 — 356 subscribers10 August 202619 September 2026
7 measurements spanning 40 days, net -2. 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 345–438 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 10:58356-13
10 Sept 2026, 10:00369-14
1 Sept 2026, 22:25383-16
25 Aug 2026, 00:15399-28
18 Aug 2026, 05:12427+42
11 Aug 2026, 12:32385+27
10 Aug 2026, 13:32358first reading

Engagement

18 posts held, back to 2 August 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 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 18 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

165 reactions across 14 posts, in 3 distinct kinds. The most used accounts for 35.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52313084046218589315935.8%
custom 54270314945247019125432.7%
custom 52850612045265415595231.5%

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 14 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 165 reactions 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 2 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.

Recent posts

9 Aug 2026, 19:02 UTC67 views18 reactionsread 10 August 2026
Photo

скетчи и новые ос. это ВЛАД и каин. они встыр пока ВСЁ 🫰🏻

custom 52313084046218589318custom 54270314945247019126custom 52850612045265415594

9 Aug 2026, 13:58 UTC107 views24 reactionsread 10 August 2026
Photo

👾 5+5=[=]

custom 523130840462185893110custom 52850612045265415597custom 54270314945247019127

9 Aug 2026, 12:59 UTC115 views13 reactionsread 10 August 2026
Photo

блум 👾

custom 54270314945247019128custom 52850612045265415594custom 52313084046218589311

7 Aug 2026, 20:29 UTC222 views25 reactionsread 10 August 2026
Photo

камышка 👾

custom 523130840462185893110custom 54270314945247019129custom 52850612045265415596

7 Aug 2026, 16:43 UTC216 views1 reactionsread 10 August 2026

если хотите напишите @alminoi 😣

custom 52850612045265415591

7 Aug 2026, 16:40 UTC212 views1 reactionsread 10 August 2026

купите арт за 100руьлей 👾

custom 52313084046218589311

7 Aug 2026, 16:07 UTC216 views21 reactionsread 10 August 2026
Photo

пока не дома чиркаю 👾

custom 52850612045265415598custom 54270314945247019128custom 52313084046218589315

7 Aug 2026, 13:40 UTC221 views18 reactionsread 10 August 2026
Photo

сестрички сатаник и солд придумала за5мин щас 😔

custom 52850612045265415598custom 52313084046218589317custom 54270314945247019123

7 Aug 2026, 12:33 UTC204 views18 reactionsread 10 August 2026
Photo

лень

custom 54270314945247019129custom 52313084046218589315custom 52850612045265415594

5 Aug 2026, 21:53 UTC252 views6 reactionsread 10 August 2026

прайс к слову @miusfusrdz

custom 52850612045265415596

5 Aug 2026, 15:08 UTC297 views1 reactionsread 10 August 2026

нарисую вам арт за пиар в тгк. пишите в лс канала 😣

custom 54270314945247019121

5 Aug 2026, 12:16 UTC306 views14 reactionsread 10 August 2026
Photo

Photo, posted without a caption

custom 52313084046218589318custom 52850612045265415593custom 54270314945247019123

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

Mentions

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.

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

“alicenoi” (@oumanoe), 356 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/oumanoe.

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.