Channel
@huishuliya
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
140subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002019841023 |
|---|---|
| Type | Channel |
| Username | @huishuliya |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/huishuliya |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 04:23 | 140 | -1 |
| 8 Aug 2026, 22:02 | 141 | no change |
| 7 Aug 2026, 14:20 | 141 | first reading |
9 posts held, back to 4 June 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 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 9 posts for this entry, the most recent from 4 July 2026. An engagement rate over an empty window would be a number about nothing.
113 reactions across 9 posts, in 10 distinct kinds. The most used accounts for 31.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 36 | 31.9% | |
| ❤ | 31 | 27.4% | |
| 🍾 | 12 | 10.6% | |
| custom 5197330377177310500 | 10 | 8.85% | |
| ❤🔥 | 10 | 8.85% | |
| custom 5197233933686677714 | 4 | 3.54% | |
| 💯 | 4 | 3.54% | |
| 😁 | 4 | 3.54% | |
| 👍 | 1 | 0.885% | |
| 🥰 | 1 | 0.885% |
Custom emoji. 2 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 areTelegram’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 9 of the 9 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 113reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 4 June 2026 to 4 July 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.
🔥Сегодня с Настасьей Самбурской мы подписали договор. Теперь я получается официально еще и поэт-песенник. 50 выпущенных ИИ-шных треков мой самозванец игнорирует, а тут можно сказать у меня настоящие «титры»! Ну и бонусом к договору - прекрасный вечер, замечательный концерт и сведенная от смеха правая скула, потому что это было потрясающе весело, музыкально и очень красиво! 🪄шалость удалась! ✨
❤🔥9🍾8🔥6
Если я ничего не пишу тут это не значит что я женщина или балерина…
😁4
Ура! Мы пережили жару! Я с трудом. Коту было еще труднее. Еще бы, в такой то шубе попробуй покайфуй в +35. Мой головной мозг вообще временно покинул чат. Несколько дней я существовала на лютом автопилоте. Теперь температура упала, кот распусшился, а мозг впервые за неделю может связно составить предложение длиннее трёх слов. Поздравляю всех выживших, с трудом переносящих жару, как мы. И моего кота. Мы сделали это 🍾…
❤6custom 51973303771773105001
03:30 я пью кофе на балконе и слушаю как под окошком пернатые орут свои «питюти». На рабочем столе док с посерийником, а в соседней вкладке вагон правок 😍 пол дня разгоняли с ребятами сюжет, а утром созвон с редакторами и правки по второму кругу. Мазохизм - скажете вы. Кайф - скажу я.
custom 51973303771773105007💯4❤3
Стартовали съемки проекта над которым мы трудились с моими сценарицами в 1-2-3 production 👏🏻👏🏻 Приятно приложить лапу к большому проекту. Пусть и совсем с краешку. Жду премьеры!
🔥7🍾4
Стартовали съемки новой комедии «УЧАСТКОВЫЕ ИЗ СИТИ» ⚡️ Основной локацией 20-серийного проекта стал район Москва-Сити. Здесь развернется история о двух полицейских: один живет по строгим правилам и уставу, второй — молодой мажор, которому все сходит с рук. Возрастной участковый Федор Кулаков (Александр Робак) — принципиальный службист старой закалки, привыкший работать в одиночку и никому не доверять. Его размеренн…
❤6🔥2
Сценарист. Уровень «Мелодрама на России-1» done ☑️
🔥11❤5custom 51972339336866777143custom 51973303771773105002❤🔥1👍1
В параллель сценарной работе безумно хочется заняться какой- нибудь хренатенью… вписаться в марафон денежный ходьбы, отучиться гадать на таро, пойти на курс по бенто тортам (ненавижу готовить!) Подобный позыв у меня был в декабре и я обучилась нейронкам. Как итог: блог на 17к подписчиков в инсте за 4 месяца, контракт с музыкальным лйблом, 50+ написанных «по приколу» треков, работа в команде Саши Комович и финалочка…
🔥7❤4🥰1
В Москву опять пришло лето. Я опять подписалась на мультик (я не люблю анимацию, но почему то она любит меня). Почти сутки писала разработку. Пальцы знатно охренели. Опять некогда гулять. Зато опять не скучно 😉
❤7🔥3custom 51972339336866777141
Showing the 9 most recent of 9 posts we hold for @huishuliya. 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.
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.
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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“Ху из Хулия” (@huishuliya), 140 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/huishuliya.
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.