Channel
@Juvilo
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
5subscribers
+0 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003199309471 |
|---|---|
| Type | Channel |
| Username | @Juvilo |
| Created | Between 1 September 2025 and 29 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/Juvilo |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 01:32 | 5 | no change |
| 13 Aug 2026, 00:15 | 5 | first reading |
20 posts held, back to 29 September 2025 — 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 20 posts for this entry, the most recent from 23 April 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
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.
36 reactions across 20 posts, in 4 distinct kinds. The most used accounts for 66.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🎄 | 24 | 66.7% | |
| 🤮 | 8 | 22.2% | |
| ❤ | 3 | 8.33% | |
| 💔 | 1 | 2.78% |
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 20 of the 20 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 36reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 29 September 2025 to 23 April 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.
Впервые я увидел тебя, В возрасте подростковым. Второй раз я встретил тебя, И ты стал моим знакомым В третьи раз было неловко, А в четвертый мы стали ближе, Лишь на пятом я только понял, что ошибся слишком. Шестой и седьмой или двадцатый, Все встречи с тобой не одинаковы. Через встречи я осознал, Влюблен в тебя я так сказал. Дни , недели, месяцы и года Я понял , с тобою я навсегда, Где и куда неважно мне С тобой х…
❤1🎄1
Сегодня я хочу поделится с стихотворениями, которые я написала Прекрасная дева из моих снов, Куда идешь? Куда бежишь? И мечтою ли ты моей являлась, Что озаряла мою жизнь? Теперь не знаю быль ли это было, Наша прошлое с заря. Но одно я знаю и не понимаю Как влюбилась в беспамянства в тебя. Это история не обо мне Она о том , как девушка поздно понимает что ее счастье было рядом и осознала когда стало слишком поздно.…
❤1🎄1
Привет? Я пишу спустя 7 месяцев как вы заметили Думаю посты я буду делать редко
🎄2
завтра ҰБТ, я морально не готова
🤮2🎄1
Надо было вчера все сделать, теперь сижу и делаю. И все они устные 🫠 Еще лист потеряла с датами. А по химий еще надо тест переписать. Я думала что только историю и доп химию сделаю, но не судьба .
🤮2🎄1
хочу сделать зарисовку , на самом деле я не сильна в этом. Можно сказать мне просто интересно время от времени придумывать новые историй.Сразу предупреждаю в описании я не слишком хороша и я не знаю когда выложу
🎄1💔1🤮1
Sticker, posted without a caption
🎄1
Хотя надо перечитать с первых глав что бы увидеть какая была старая рисовка. Только теплые воспоминания на душе. И хочу посмотреть улучшилась ли она в худшую или наоборот в лучшую
🎄1🤮1
Я хочу возобновить чтение данной манхвы Рисовка 🫠 Новая тоже нормальная, старая роднее.
🎄1🤮1
Sticker, posted without a caption
🎄1
4 звездочные персонажи есть, а Е лань еще нет Очень жду ее и надеюсь на то что в конце я получу ее. Я хотела выбить Лауму в преведущем баннере и вместо неё мне выпала Кэ Цинь
🎄2🤮1
Как вы? Как день?
🎄1
Showing the 12 most recent of 20 posts we hold for @Juvilo. 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.
Citation-graph rank — 1,345,404 of 1,548,671entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“Juvilo” (@Juvilo), 5 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/Juvilo.
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.