Telegram RegisterThe public register of Telegram
Telegram profile photo for L.eto_vdushe

Channel

L.eto_vdushe

@leto_vdushe

Has discussion group

On this record: Topic · Growth · Engagement · Cite this entry

1,130subscribers

-13 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001785497985
TypeChannel
Username@leto_vdushe
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 October 2026
Last confirmed live5 November 2026
Measurements held17
Confirmed unchanged1 time, most recently 5 November 2026
On Telegramt.me/leto_vdushe

Topic

Travel — 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 6 October 2026 and assigned it the closest of 31 fixed categories, at 100% 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,1301,1431,136.57 August 2026 — 1,143 subscribers14 August 2026 — 1,142 subscribers17 August 2026 — 1,140 subscribers24 August 2026 — 1,139 subscribers27 August 2026 — 1,137 subscribers30 August 2026 — 1,139 subscribers11 September 2026 — 1,137 subscribers28 September 2026 — 1,136 subscribers5 October 2026 — 1,135 subscribers6 October 2026 — 1,135 subscribers12 October 2026 — 1,133 subscribers15 October 2026 — 1,132 subscribers18 October 2026 — 1,137 subscribers21 October 2026 — 1,135 subscribers26 October 2026 — 1,134 subscribers30 October 2026 — 1,132 subscribers5 November 2026 — 1,130 subscribers7 August 20265 November 2026
17 measurements spanning 90 days, net -13. 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,128–1,145 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Nov 2026, 09:351,130-2
30 Oct 2026, 04:281,132-2
26 Oct 2026, 18:471,134-1
21 Oct 2026, 08:051,135-2
18 Oct 2026, 13:141,137+5
15 Oct 2026, 05:201,132-1
12 Oct 2026, 12:301,133-2
6 Oct 2026, 03:341,135no change
5 Oct 2026, 16:571,135-1
28 Sept 2026, 01:581,136-1
11 Sept 2026, 18:011,137-2
30 Aug 2026, 08:241,139+2
27 Aug 2026, 02:161,137-2
24 Aug 2026, 10:231,139-1
17 Aug 2026, 18:561,140-2
14 Aug 2026, 21:351,142-1
7 Aug 2026, 16:491,143first 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.

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

“L.eto_vdushe” (@leto_vdushe), 1,130 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/leto_vdushe.

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.