💋Информационный пост, если кто-то вдруг пропустил💋
❤47🎉7🔥5❤🔥4💘1

Channel
@jeffsaturworld
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
1,483subscribers
-50 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001864786613 |
|---|---|
| Type | Channel |
| Username | @jeffsaturworld |
| Created | 7 November 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 7 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/jeffsaturworld |
Music — 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 17 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 12:21 | 1,483 | -2 |
| 12 Sept 2026, 07:22 | 1,485 | -8 |
| 8 Sept 2026, 10:01 | 1,493 | -9 |
| 3 Sept 2026, 09:55 | 1,502 | -3 |
| 31 Aug 2026, 08:34 | 1,505 | -6 |
| 27 Aug 2026, 22:36 | 1,511 | -1 |
| 24 Aug 2026, 22:25 | 1,512 | -4 |
| 21 Aug 2026, 13:59 | 1,516 | -6 |
| 18 Aug 2026, 04:53 | 1,522 | -5 |
| 15 Aug 2026, 06:36 | 1,527 | -4 |
| 8 Aug 2026, 08:40 | 1,531 | -2 |
| 7 Aug 2026, 21:33 | 1,533 | no change |
| 7 Aug 2026, 19:52 | 1,533 | first reading |
11 posts held, back to 14 October 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 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 11 posts for this entry, the most recent from 17 November 2025. An engagement rate over an empty window would be a number about nothing.
Measured directly from 3 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.
620 reactions across 11 posts, in 7 distinct kinds. The most used accounts for 75.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 467 | 75.3% | |
| ❤🔥 | 74 | 11.9% | |
| 🔥 | 34 | 5.48% | |
| 🎉 | 17 | 2.74% | |
| 🍓 | 15 | 2.42% | |
| 💘 | 9 | 1.45% | |
| 🍾 | 4 | 0.645% |
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 11 of the 11 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 620 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 14 October 2025 to 17 November 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
💋Информационный пост, если кто-то вдруг пропустил💋
❤47🎉7🔥5❤🔥4💘1
На YouTube-канале Джеффа появился Passion Fruit с видеорядом https://youtu.be/S9EqYP4uUgY?si=U8amYex4aEYYTCOl И Golden Night (English Version) с видеорядом https://youtu.be/5mUX7APlxRE?si=oP9uAoAlsWP2zSt1 #jeffsatur
❤35🔥9🎉6❤🔥3
Джефф: "RED GIANT EP" #jeffsatur
❤52🔥9❤🔥8🍾4
На YouTube-канале Джеффа появился Call it over с видеорядом https://youtu.be/yxUUgJQLAm0?si=uVDBQgFfWOMaVoSP #jeffsatur
❤32🔥6❤🔥4🎉4
Red Giant EP Альбом доступен для прослушивания на всех музыкальных платформах JeffSatur.lnk.to/RedGiant_EP #jeffsatur
❤44❤🔥10🔥5
В комментарии под постом выше 💋💋💋 приложила для вас скачанный клип и аудиоверсию. Но, пожалуйста, по возможности продолжайте слушать эту прекрасную композицию на официальных площадках.
❤21❤🔥6💘3
Состоялся релиз ของขวัญปีใหม่ (Golden Night) https://youtu.be/mBECArSvaRs?si=c7BcE6Ue1QyI4nmN Аудиоверсия также уже доступна на всех музыкальных платформах http://JeffSatur.lnk.to/GoldenNight Чтобы поддержать артиста, давайте слушать трек на официальных платформах Сюда трек и клип выложу файлами примерно через сутки #jeffsatur
❤50❤🔥9💘1
17 ноября у Джеффа выйдет EP в составе которого будут: Ride Or Die PassionFruit Tell Me The Name Golden Night (English Version) Call It Over ของขวัญปีใหม่ (Golden Night) #jeffsatur
❤48❤🔥15💘1
Отвечаю на вопрос в комментариях: на прошлой неделе вышел пилот будущего сериала с участием Джеффа "My Chef In Crime". https://youtu.be/SMeX1nUIMJA?si=bdqgnXjcy1OpOnXu Насколько мне известно, съемки пройдут в начале следующего года, а выхода можно ожидать только в четвертом квартале. #jeffsatur
❤42❤🔥7🍓4
В первую очередь хочу попросить прощение за своё молчаливое отсутствие. Я конечно и раньше тут пропадала временами, но на сей раз уж явно поставила рекорд. И особенно извиняюсь перед той парой человек, кто уже начал задавать вопросы в комментариях о моей пропаже, но по-прежнему не получил ответа. Я не хотела вас игнорировать, просто пыталась сформулировать развернутый пост, но всё время что-то не сходилось. В общем,…
❤51🍓7💘3
#jeffsatur #ValentinoSS26xJeffSatur
❤45❤🔥8🍓4
Showing the 11 most recent of 11 posts we hold for @jeffsaturworld. 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.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“Life On Saturn” (@jeffsaturworld), 1,483 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/jeffsaturworld.
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.