Telegram RegisterThe public register of Telegram
Telegram profile photo for Сказки на ночь

Channel

Сказки на ночь

@lilskazki

On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry

1,353subscribers

-16 since we began measuring on 3 October 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001167223314
TypeChannel
Username@lilskazki
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded3 October 2026
Last confirmed live7 November 2026
Measurements held10
Confirmed unchanged1 time, most recently 7 November 2026
On Telegramt.me/lilskazki

Topic

Literature — a classification, not a measurement. An on-box language model (qwen3.6:35b-a3b, prompt version 1) read this channel’s own recent posts on 20 October 2026 and assigned it the closest of 31 fixed categories, at 91% 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.

Growth

1,3531,3691,3613 October 2026 — 1,369 subscribers3 October 2026 — 1,369 subscribers7 October 2026 — 1,365 subscribers13 October 2026 — 1,364 subscribers20 October 2026 — 1,363 subscribers23 October 2026 — 1,362 subscribers26 October 2026 — 1,361 subscribers1 November 2026 — 1,357 subscribers4 November 2026 — 1,354 subscribers7 November 2026 — 1,353 subscribers3 October 20267 November 2026
10 measurements spanning 36 days, net -16. 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 1,351–1,371 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Nov 2026, 22:561,353-1
4 Nov 2026, 11:001,354-3
1 Nov 2026, 21:051,357-4
26 Oct 2026, 15:081,361-1
23 Oct 2026, 11:481,362-1
20 Oct 2026, 05:591,363-1
13 Oct 2026, 18:571,364-1
7 Oct 2026, 20:411,365-4
3 Oct 2026, 17:071,369no change
3 Oct 2026, 05:471,369first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.

Appears in Telegram’s recommendations for other channels

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.

Бизнес Арсенал
@biznes_arsenal · 19,231
Telegram ranks this channel #81 of 84 here — alongside 83 others — read 3 October 2026

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.

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

“Сказки на ночь” (@lilskazki), 1,353 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/lilskazki.

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.