Telegram RegisterThe public register of Telegram
Telegram profile photo for 𓆩Sky: children of the light 𓆪

Channel

𓆩Sky: children of the light 𓆪

@ll_sky_ll

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

146subscribers

-1 since we began measuring on 9 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002064264310
TypeChannel
Username@ll_sky_ll
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live1 September 2026
Measurements held3
Confirmed unchanged2 times, most recently 1 September 2026
On Telegramt.me/ll_sky_ll

Growth

146147146.59 August 2026 — 147 subscribers10 August 2026 — 147 subscribers25 August 2026 — 146 subscribers9 August 202625 August 2026
3 measurements spanning 15 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 146–147 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Aug 2026, 02:36146-1
10 Aug 2026, 07:11147no change
9 Aug 2026, 17:30147first reading

Engagement

9 posts held, back to 24 July 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 9 posts for this entry, the most recent from 2 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
43s
Average length
43s

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.

Reaction mix

126 reactions across 9 posts, in 7 distinct kinds. The most used accounts for 27.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53394628752053589683527.8%
custom 54498758929961804183124.6%
custom 53368410338943533863023.8%
custom 54046101073822066741511.9%
custom 527407558442146439475.56%
custom 533707330572572273975.56%
custom 533730108072633237210.794%

Custom emoji. Every 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 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 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 126 reactions 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 24 July 2026 to 2 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

2 Aug 2026, 17:19 UTC60 views14 reactionsread 9 August 2026

Все ваши картины такие прекрасные и волшебные. Каждая картина неповторима, интересна и удивительна по своему. Спасибо всем кто принял участие в этом чудесном конкурсе! 🤗

custom 54498758929961804189custom 52740755844214643945

2 Aug 2026, 17:18 UTC61 views13 reactionsread 9 August 2026
Photo

Картины остальных участников: Oduvanchik, "Девочка в лесу" Дар, "Альпий, горный пейзаж близ Сан-Реми" Бика, "Звездная ночь" Cracker, "Луг в горах: ферма Сен-Поль" Фикус, "Звездная ночь" Nera Saygdhy, "Звездная ночь над Роной" Плов, "Пшеничное поле с воронами" Vivi, "Звездная ночь", "Цветущий миндаль" Rara, "Шесть воронов" Чаёк,"Пшеничное поле"

custom 544987589299618041813

2 Aug 2026, 17:00 UTC75 views15 reactionsread 9 August 2026
Photo

⌑˙∘✧ А вот и наши победители со своими картинами! ✧∘˙⌑ 1 место @DeerRexx Получает: пропуск с сезона 2 место @Nuner_Fastu Получает: любой Донат на 500₽ 3 место @Artnarkoman Получает: 20 ♡

custom 533946287520535896814custom 54046101073822066741

1 Aug 2026, 05:46 UTC68 views9 reactionsread 9 August 2026
Photo

Напоминание о шоу фейерверков! 🎆 Каждый месяц, 1-го числа, в Птичьей Деревне доступно красочное шоу фейерверков, на которое может попасть каждый желающий, который выполнил 8 квест сезона Возрождения! Как попасть: ✧слева от порталов в Птичьей Деревне будет посох, у которого нужно сесть в круг медитации Расписание представлений (по МСК): ✧10:00 - 10:15 ✧14:00 - 14:15 ✧18:00 - 18:15 ✧22:00 - 22:15 ✧02:00 - 02:15 ✧06

custom 54498758929961804186custom 52740755844214643942custom 53373010807263323721

30 Jul 2026, 21:10 UTC87 views10 reactionsread 9 August 2026

Сегодня последний день приема работ, в 23:59 по МСК работы перестанут приниматься

custom 53368410338943533868custom 53370733057257227392

30 Jul 2026, 19:37 UTC99 views13 reactionsread 9 August 2026
Photo

⌑ ˙ 𖤓 Дни солнечного света 𖤓 ˙ ⌑ Во время ивента вы сможете скатиться с горки прямо в воду, прыгнуть с вышки эффектной бомбочкой, исследовать дно водоёма, расположенного рядом с Бабушкой, а также принять участие в гонке на досках для сёрфинга. Ивент продлится с 31 июля по 20 августа Желаем вам весело провести время!

custom 540461010738220667412custom 53394628752053589681

29 Jul 2026, 19:53 UTC100 views17 reactionsread 9 August 2026
Photo

К нам спешит дух-путник Конфетти-кузен из сезона Сопричастности! 🎉 Пробудет он в доме с 30.07 по 03.08 10:00 по МСК. Все вещи и цены духа указаны на фото. Готовы пускать конфетти?

custom 53368410338943533867custom 53394628752053589686custom 54498758929961804183custom 53370733057257227391

25 Jul 2026, 17:31 UTC141 views15 reactionsread 9 August 2026
Video

☀ Разработчики выложили трейлер дней Солнечного света ☀ Ивент продлится с 31 июля по 21 августа (в 10:00 по МСК).

custom 533946287520535896813custom 54046101073822066742

24 Jul 2026, 18:14 UTC144 views20 reactionsread 9 August 2026

До конца конкурса остается ровно неделя!

custom 533684103389435338615custom 53370733057257227394custom 53394628752053589681

Showing the 9 most recent of 9 posts we hold for @ll_sky_ll. 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

Mentions

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.

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

“𓆩Sky: children of the light 𓆪” (@ll_sky_ll), 146 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/ll_sky_ll.

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.