Telegram RegisterThe public register of Telegram
Telegram profile photo for Маникюрщицы мяукают

Channel

Маникюрщицы мяукают

@manicuremeoww

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

292subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001609430658
TypeChannel
Username@manicuremeoww
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live6 September 2026
Measurements held4
Confirmed unchanged1 time, most recently 6 September 2026
On Telegramt.me/manicuremeoww

Growth

292293292.57 August 2026 — 292 subscribers8 August 2026 — 292 subscribers14 August 2026 — 293 subscribers6 September 2026 — 292 subscribers7 August 20266 September 2026
4 measurements spanning 30 days. 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 292–293 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Sept 2026, 13:37292-1
14 Aug 2026, 12:04293+1
8 Aug 2026, 08:16292no change
7 Aug 2026, 19:23292first reading

Engagement

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

Reaction mix

91 reactions across 12 posts, in 7 distinct kinds. The most used accounts for 22.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52356954173619669342022.0%
2022.0%
🔥1819.8%
custom 54450102576905061431516.5%
❤‍🔥88.79%
custom 534404892102493089366.59%
🍓44.40%

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

Measured over the 12 most recent posts we hold, published 21 June 2026 to 5 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

5 Aug 2026, 16:41 UTC55 views4 reactionsread 8 August 2026
Photo

Ксюша 🪼🌟🪐

🔥2custom 52356954173619669342

2 Aug 2026, 19:41 UTC79 views1 reactionsread 8 August 2026

Ближайшие свободные окошки Ксюша 🦈 5.08 12:00/13:00 6.08 12:00 15:00 9.08 19:00 13.08 12:00 15:00 18:00 14.07 12:00 19:00 Юля ♠️ 5.08 13:00 16:00 19:00 6.07 13:00 16:00 9.07 15:00 18:00 10.07 13:00 16:00 19:00 12.07 13:00 16:00 19:00 13.07 17:00 ОНЛАЙН ЗАПИСЬ Или Лс @yuliana_kk @erundopelka

1

1 Aug 2026, 18:57 UTC84 views6 reactionsread 8 August 2026
Forwarded from @erundopeeeelkaPhoto

Делаю нишевый дизайн на август Кому

🔥6

1 Aug 2026, 07:14 UTC97 views14 reactionsread 8 August 2026
Photo

Юля 🪷🐇🐇🦈🐇

5🍓4custom 52356954173619669343custom 54450102576905061432

26 Jul 2026, 07:26 UTC142 views11 reactionsread 8 August 2026
Photo

Ксюша 🐇🐇🐇

4custom 53440489210249308934custom 54450102576905061433

21 Jul 2026, 18:02 UTC165 views4 reactionsread 8 August 2026

Здравствуйте, я вернулась с отпуска, запишитесь на ноготочки пожалуйста 👀 Онлайн запись

4

Signed Ерундопелька

17 Jul 2026, 15:36 UTC167 views10 reactionsread 8 August 2026
Video message

Video message, posted without a caption

custom 523569541736196693443🔥3

17 Jul 2026, 07:47 UTC152 views1 reactionsread 8 August 2026
Photo

Открыли запись на август ♠️ ОНЛАЙН ЗАПИСЬ

custom 52356954173619669341

11 Jul 2026, 18:15 UTC185 views18 reactionsread 8 August 2026
Photo

Ксюша 🌸🌸🌸

❤‍🔥8custom 54450102576905061436custom 52356954173619669344

2 Jul 2026, 07:36 UTC170 views4 reactionsread 8 August 2026

На днях сфоткаю их поближе, но если что, их всегда можно посмотреть в студии, в моменте. Время на них выделено как на обычную услугу, так что всегда можно устроить ракеровочку♠️

custom 54450102576905061434

2 Jul 2026, 07:30 UTC170 views13 reactionsread 8 August 2026
Photo

Если успели расстроится из-за повышения цен - не расстраивайтесь 🐇 Мы придумали новый формат. Это особые спешл дизайны которые мы составили сетами в количестве 6 штук. Приходишь, выбираешь какой нравится ну и всё, кайф. 👀 Сеты подобраны и сделаны в определенной задумке, поэтому менять ничего нельзя, зато и сложно думать над дизайном не надо, мы уже подумали. Обновлять сетики мы будем примерно раз в месяц, но возмо

🔥7custom 52356954173619669346

21 Jun 2026, 20:19 UTC175 views5 reactionsread 8 August 2026

Ближайшие свободные окошки 🐇 Ксюша 🐇 26.06 12:00 15:00 27.06 16:00 19:00 29.06 18:00 Юля 🐇 В этом месяце окошек больше нет 🐇 ОНЛАЙН ЗАПИСЬ Или Лс @yuliana_kk @erundopelka

3custom 53440489210249308932

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

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.

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

“Маникюрщицы мяукают” (@manicuremeoww), 292 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/manicuremeoww.

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.