Channel
@gulinskaya_makeup
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
104subscribers
+12 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002461466771 |
|---|---|
| Type | Channel |
| Username | @gulinskaya_makeup |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/gulinskaya_makeup |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 08:59 | 104 | +7 |
| 7 Sept 2026, 21:17 | 97 | +6 |
| 29 Aug 2026, 14:07 | 91 | -1 |
| 9 Aug 2026, 13:45 | 92 | no change |
| 7 Aug 2026, 09:32 | 92 | first reading |
7 posts held, back to 2 July 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 7 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 5 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.
79 reactions across 7 posts, in 6 distinct kinds. The most used accounts for 20.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5366346750548260124 | 16 | 20.3% | |
| custom 5465215819665394949 | 16 | 20.3% | |
| custom 5366281754808165593 | 14 | 17.7% | |
| custom 5404721299790525922 | 14 | 17.7% | |
| custom 5287681194706617853 | 13 | 16.5% | |
| custom 5237954312461642466 | 6 | 7.59% |
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 7 of the 7 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 79 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 2 July 2026 to 3 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.
Некий бьюти hall🙂↕️ Очень трудно записывать любого рода видео, понимая что в обратной связи полтора лайка и ноль комментариев…💗 Поэтому все сюда поставят лайк и напишут много хороших комментариев 🧘♂🧿
custom 54652158196653949499custom 52379543124616424666custom 52876811947066178535custom 53663467505482601244
Zendaya’s glow skin// 🤍💝🐚 Самое главное в таких сияющих и «сырых» макияжах - на каждом этапе проходиться фиксатором, чтобы через 10 минут макияж не отпечатался на телефоне или руке
custom 53663467505482601244custom 54652158196653949494custom 53662817548081655933
Blond waves// 🪮🎀🤩 В последнее время ко мне постоянно приходят с запросом на крупный локон, а я такие завитки люблю делать на стайлер, но на клиентах такую услугу не вводила, пока делаю только на горячие инструменты А на подружках люблю побаловаться, вот моя приезжала - накормила, напоила, с укладкой красивой дальше отправила👩
custom 53662817548081655934custom 52876811947066178533
Born to be a diva// 🤩🥹🖤 Не могу не показать вам шикарные фотографии, сделанные bestie! Нижний Новгород, вставайте в очередь на съемку на тот самый Canon G7x mark iii к Жанне 📸♥️
custom 53663467505482601247custom 52876811947066178533custom 54047212997905259221
Как-то я выпала из ведения тг канала, буду исправляться!🥹 Из последнего: 🤩уже окончательно обустроилась в Москве, все спрашивают, не устала ли я от суеты, но я за этим и приехала! 🌸лета в Москве практически не видно, были холода и дожди, поэтому маршрутным листом был дом-работа-дом 🙏накопила много полезного и интересного контента, все Буду рассказывать и показывать здесь!
custom 53662817548081655933custom 54047212997905259222
Самый красивый макияж летом - toasted makeup💄👠 На видео схема нанесения, обязательно используйте кремовый продукт Мне супер понравилось работать со скульптором Shik Studio в шайбе Оттенок топ и ложится красиво, в тушевку мягкую уходит🙏
custom 54047212997905259224custom 52876811947066178532
На память💙 HSE GRADUATED Prom 2026🤩
custom 54047212997905259227custom 53662817548081655934custom 54652158196653949493custom 53663467505482601241
Showing the 7 most recent of 7 posts we hold for @gulinskaya_makeup. 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.
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.
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.
“Gulinskaya mua” (@gulinskaya_makeup), 104 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/gulinskaya_makeup.
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.