Telegram RegisterThe public register of Telegram
Telegram profile photo for JULIS 🧡

Channel

JULIS 🧡

@juliashpilevaya

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

94subscribers

-1 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-1002174671240
TypeChannel
Username@juliashpilevaya
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live7 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 7 September 2026
On Telegramt.me/juliashpilevaya

Growth

939694.57 August 2026 — 95 subscribers9 August 2026 — 95 subscribers14 August 2026 — 93 subscribers21 August 2026 — 94 subscribers29 August 2026 — 96 subscribers7 September 2026 — 94 subscribers947 August 20267 September 2026
6 measurements spanning 31 days, net -1. 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 93–96 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Sept 2026, 20:4194-2
29 Aug 2026, 02:2596+2
21 Aug 2026, 10:0594+1
14 Aug 2026, 20:4693-2
9 Aug 2026, 12:3295no change
7 Aug 2026, 13:5895first reading

Engagement

14 posts held, back to 18 May 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 14 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
33s
Average length
17s

Measured directly from 2 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.

Reaction mix

25 reactions across 10 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 533022371335689418225100.0%

Custom emoji. One 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 count beside it is 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 10 of the 14 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 25 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 14 most recent posts we hold, published 18 May 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, 15:40 UTC31 views1 reactionsread 9 August 2026
Photo

Позанималась фортепиано и пришла за любимым десертиком и кофе 🤍 Веранды в городе и сервис на уровне, всегда приятно посещать места, где персонал приветлив и доброжелателен 🫂 * Как не странно, но именно в таких заведениях меньше всего людей.

custom 53302237133568941821

16 Jul 2026, 13:55 UTC123 views2 reactionsread 9 August 2026
Photo

If you got it, you know it ❤️

custom 53302237133568941822

15 Jul 2026, 18:25 UTC113 views4 reactionsread 9 August 2026
Video

Засыпать с жаждой и предвкушением следующего дня, чувствуя, что ты на верном пути. 💝 best feeling:) Сильная любовь к себе как к субъекту и такая же любовь к объекту под названием жизнь дают энергию просыпаться изо дня в день. Силы приходят в движении от трения с пространством, только так и никак иначе. Делай, что должен, там, где ты есть.

custom 53302237133568941824

7 Jul 2026, 14:48 UTC129 views3 reactionsread 9 August 2026
Photo

Шла домой, но свернула на Арбат и дошла до Тверской😍 Воздух летнего вечера так и манит, не хочет отпускать, а я его. Гуляя в одиночестве, я его совсем не чувствую: вокруг столько людей, зданий с историей, улиц и красоты Москвы. Успеть бы насытиться этим мгновением - два часа пролетают за минуты. Здесь и сейчас 🕊️

custom 53302237133568941823

7 Jul 2026, 14:07 UTC104 views1 reactionsread 9 August 2026
Photo

Обед, который тебя насытит и даст жизненные силы на день! Белок (куриная грудка, печень трески, пармезан) — для сытости, восстановления организма и поддержания мышц. Полезные жиры (авокадо, печень трески) — для работы мозга, гормональной системы, сердца и усвоения витаминов. Сложные углеводы (гречка) — для стабильной энергии без резких скачков сахара. Овощи и клетчатка (редис) — для пищеварения, витаминов и антио

custom 53302237133568941821

19 Jun 2026, 08:59 UTC167 views4 reactionsread 9 August 2026
Photo

Свежо, чисто, красиво и солнечно — такими наречиями хочу описать сегодняшнее утро! В квартире на 10 дней отключали горячую воду и это как-никак сказывалось на моем состоянии. Я могу подолгу стоять под душем, делать свой многоступенчатый уход, и когда эту возможность забирают, ощущаешь огромный дискомфорт: голову не помыть, особенно нынешний блонд; кремом не обмазаться - как все смывать потом? В свой обычный день, я

custom 53302237133568941824

12 Jun 2026, 03:38 UTC181 views1 reactionsread 9 August 2026
Video message

Video message, posted without a caption

custom 53302237133568941821

11 Jun 2026, 18:21 UTC173 views2 reactionsread 9 August 2026

https://youtu.be/leTruMnXVA4?si=pcTlATgg5Dpxv6YV

custom 53302237133568941822

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

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

“JULIS 🧡” (@juliashpilevaya), 94 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/juliashpilevaya.

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.