Telegram RegisterThe public register of Telegram
Telegram profile photo for annailss/маникюр омск

Channel

annailss/маникюр омск

@annailss_omsk

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

212subscribers

+35 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1003531665188
TypeChannel
Username@annailss_omsk
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live16 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/annailss_omsk

Growth

177212194.58 August 2026 — 177 subscribers8 August 2026 — 177 subscribers16 August 2026 — 183 subscribers23 August 2026 — 190 subscribers30 August 2026 — 197 subscribers9 September 2026 — 205 subscribers16 September 2026 — 212 subscribers8 August 202616 September 2026
7 measurements spanning 39 days, net +35. 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 172–217 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 20:56212+7
9 Sept 2026, 15:57205+8
30 Aug 2026, 17:55197+7
23 Aug 2026, 11:33190+7
16 Aug 2026, 21:24183+6
8 Aug 2026, 14:57177no change
8 Aug 2026, 14:30177first reading

Engagement

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

What this channel posts

Video runtime
16s
Average length
16s

Measured directly from 1 video 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

43 reactions across 6 posts, in 13 distinct kinds. The most used accounts for 20.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5330243633415234637920.9%
custom 5390922798229121921818.6%
💘818.6%
custom 5305603401743107845614.0%
custom 530567687145367504924.65%
🍓24.65%
🔥24.65%
custom 530531044202385030712.33%
custom 530536979847187980112.33%
custom 530538291959696942912.33%
custom 535978559959311924912.33%
❤‍🔥12.33%
💋12.33%

Custom emoji. 8 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 6 of the 6 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 43 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 6 most recent posts we hold, published 2 August 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.

Recent posts

8 Aug 2026, 07:54 UTC90 views6 reactionsread 8 August 2026
Photo

До/после🎀 Стоимость:2100❤️

custom 53909227982291219213🍓1💋1custom 53302436334152346371

8 Aug 2026, 07:49 UTC71 views7 reactionsread 8 August 2026
Photo

⭐️⭐️До не мое/после⭐️⭐️⭐️

🔥2custom 53056034017431078452custom 53909227982291219212custom 53053697984718798011

8 Aug 2026, 07:43 UTC71 views5 reactionsread 8 August 2026
Photo

Стоимость: 2100🤩🤩

💘2custom 53053829195969694291custom 53597855995931192491custom 53909227982291219211

8 Aug 2026, 07:35 UTC73 views5 reactionsread 8 August 2026
Photo

До/после Носка 23дня🤩 Стоимость: 2000🤩🐚

custom 53302436334152346372custom 53056034017431078451custom 53056768714536750491custom 53909227982291219211

2 Aug 2026, 18:09 UTC156 views10 reactionsread 8 August 2026
Video

До, носка 22 дня 🪷

💘4custom 53302436334152346373❤‍🔥1custom 53056034017431078451custom 53909227982291219211

2 Aug 2026, 18:06 UTC143 views10 reactionsread 8 August 2026
Photo

Стоимость: 2100🐚🤩

custom 53302436334152346373💘2custom 53056034017431078452🍓1custom 53053104420238503071custom 53056768714536750491

Showing the 6 most recent of 6 posts we hold for @annailss_omsk. 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.

Mentions

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.

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

“annailss/маникюр омск” (@annailss_omsk), 212 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/annailss_omsk.

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.