Channel
Ещё только рассвет
@leyleyd
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
8,926subscribers
-442 since we began measuring on 10 September 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001816315622 |
|---|---|
| Type | Channel |
| Username | @leyleyd |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 September 2026 |
| Last confirmed live | 2 November 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 2 November 2026 |
| On Telegram | t.me/leyleyd |
Topic
Other / unclassifiable — 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 28 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Nov 2026, 04:27 | 8,926 | -35 |
| 30 Oct 2026, 11:06 | 8,961 | -36 |
| 27 Oct 2026, 17:50 | 8,997 | -9 |
| 24 Oct 2026, 23:16 | 9,006 | -27 |
| 21 Oct 2026, 22:28 | 9,033 | -15 |
| 18 Oct 2026, 12:37 | 9,048 | -24 |
| 15 Oct 2026, 08:08 | 9,072 | -22 |
| 12 Oct 2026, 16:21 | 9,094 | -36 |
| 5 Oct 2026, 16:38 | 9,130 | -53 |
| 28 Sept 2026, 01:41 | 9,183 | -133 |
| 15 Sept 2026, 22:02 | 9,316 | -34 |
| 12 Sept 2026, 15:59 | 9,350 | -18 |
| 10 Sept 2026, 20:21 | 9,368 | first 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.
@mangaaaaaaaaaaaaaaaaaaaaaa · 16,978
Telegram ranks this channel #1 of 37 here — alongside 36 others — read 14 September 2026
@Tearsonwitheredfllowers · 25,211
Telegram ranks this channel #2 of 40 here — alongside 39 others — read 13 September 2026
@onnllmw · 17
Telegram ranks this channel #2 of 48 here — alongside 47 others — read 10 September 2026
@manhwa_news19 · 29,820
Telegram ranks this channel #6 of 32 here — alongside 31 others — read 10 September 2026
@lnmanga · 113,993
Telegram ranks this channel #13 of 56 here — alongside 55 others — read 10 September 2026
@mangabuff · 103,793
Telegram ranks this channel #21 of 54 here — alongside 53 others — read 10 September 2026
This channel appears in 6 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 2 November 2026 — this entry's latest reading, not the date you are reading this.
“Ещё только рассвет” (@leyleyd), 8,926 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/leyleyd.
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.