Telegram RegisterThe public register of Telegram
Telegram profile photo for Плетение Воронова Людмила

Channel

Плетение Воронова Людмила

@lyudmilasaw63

Has discussion group

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

854subscribers

+3 since we began measuring on 17 September 2026

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

Register entry

Telegram ID-1001695204822
TypeChannel
Username@lyudmilasaw63
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 October 2026
Last confirmed live2 November 2026
Measurements held6
Confirmed unchanged2 times, most recently 2 November 2026
On Telegramt.me/lyudmilasaw63

Topic

Art & design — 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 10 October 2026 and assigned it the closest of 31 fixed categories, at 90% 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

85085485217 September 2026 — 851 subscribers19 September 2026 — 850 subscribers3 October 2026 — 852 subscribers9 October 2026 — 852 subscribers13 October 2026 — 853 subscribers27 October 2026 — 854 subscribers17 September 202627 October 2026
6 measurements spanning 40 days, net +3. 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 849–855 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Oct 2026, 13:27854+1
13 Oct 2026, 02:31853+1
9 Oct 2026, 19:20852no change
3 Oct 2026, 15:19852+2
19 Sept 2026, 15:41850-1
17 Sept 2026, 11:47851first 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.

Полина Майорова. Плетение из бумажной лозы
@hm_by_polina_mayorova · 41,406
Telegram ranks this channel #4 of 72 here — alongside 71 others — read 17 September 2026
Лозамастер| Плетение мебели
@magic_sunduchek · 31,187
Telegram ranks this channel #7 of 64 here — alongside 63 others — read 17 September 2026

This channel appears in 2 seed channels' Telegram-generated recommendation lists 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 27 October 2026 — this entry's latest reading, not the date you are reading this.

“Плетение Воронова Людмила” (@lyudmilasaw63), 854 subscribers as measured 27 October 2026. Telegram Register, tgregister.com/channel/lyudmilasaw63.

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.