Channel
@juliajuli13
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Telegram's recommendations · Cite this entry
612subscribers
-3 since we began measuring on 4 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001292223490 |
|---|---|
| Type | Channel |
| Username | @juliajuli13 |
| Created | Between 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 4 September 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/juliajuli13 |
Personal blog — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 24 September 2026 and assigned it the closest of 31 fixed categories, at 77% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Nov 2026, 20:50 | 612 | -1 |
| 27 Oct 2026, 23:48 | 613 | -1 |
| 21 Oct 2026, 13:39 | 614 | -1 |
| 14 Oct 2026, 08:29 | 615 | -3 |
| 6 Oct 2026, 07:16 | 618 | -6 |
| 24 Sept 2026, 20:38 | 624 | +4 |
| 12 Sept 2026, 16:14 | 620 | +2 |
| 5 Sept 2026, 10:58 | 618 | +3 |
| 4 Sept 2026, 05:22 | 615 | no change |
| 4 Sept 2026, 04:47 | 615 | first reading |
3 posts held, back to 2 September 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 3 posts for this entry, the most recent from 3 September 2026. An engagement rate over an empty window would be a number about nothing.
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.
114 reactions across 3 posts, in 7 distinct kinds. The most used accounts for 36.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5440851861764602056 | 41 | 36.0% | |
| custom 5370955177442428415 | 36 | 31.6% | |
| 💘 | 22 | 19.3% | |
| ❤ | 7 | 6.14% | |
| 🔥 | 5 | 4.39% | |
| 🥰 | 2 | 1.75% | |
| 👍 | 1 | 0.877% |
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 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 3 of the 3 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 114 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 3 most recent posts we hold, published 2 September 2026 to 3 September 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.
💍 Я буду любить тебя каждый момент Клянусь, буду рядом, когда нелегко. Когда-то мы просто сказали «привет» И в это мгновение забыли обо всём🤍
custom 537095517744242841523💘9custom 54408518617646020566👍1
это было утро, когда я точно знала, что надеть🕊️💍
custom 544085186176460205615❤7custom 53709551774424284155🥰2
немного фоточек с банкета🤩🥂 был очень вкусный торт, внутри начинка сникерс и оооочень вкусный крем😍 ждём ещё фото на фотоаппарат, так как они дольше по обработке но спасибо нашему рилсмейкеру за оперативность и у нас уже есть такие прекрасные кадры и фото и видео🥹🩷 я люблю прожить в моменте все события, поэтому очень рада, что уже можно всё снова пересмотреть
custom 544085186176460205620💘13custom 53709551774424284158🔥5
Showing the 3 most recent of 3 posts we hold for @juliajuli13. 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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“Julia Juli //жизнь в Москве и путешествия❤️” (@juliajuli13), 612 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/juliajuli13.
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.