Telegram RegisterThe public register of Telegram
Telegram profile photo for You and? ⸸‌

Channel

You and? ⸸‌

@vaslaty

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

480subscribers

-429 since we began measuring on 23 August 2026

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

Register entry

Telegram ID-1001813330488
TypeChannel
Username@vaslaty
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 October 2026
Last confirmed live13 October 2026
Measurements held8
Confirmed unchanged1 time, most recently 13 October 2026
On Telegramt.me/vaslaty

Topic

Music — 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 13 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 why it has no browse page of its own yet.

Growth

480909694.523 August 2026 — 909 subscribers24 August 2026 — 908 subscribers31 August 2026 — 897 subscribers9 September 2026 — 833 subscribers18 September 2026 — 715 subscribers4 October 2026 — 534 subscribers11 October 2026 — 534 subscribers13 October 2026 — 480 subscribers23 August 202613 October 2026
8 measurements spanning 51 days, net -429. 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 416–973 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Oct 2026, 07:17480-54
11 Oct 2026, 19:53534no change
4 Oct 2026, 01:38534-181
18 Sept 2026, 07:22715-118
9 Sept 2026, 18:17833-64
31 Aug 2026, 21:58897-11
24 Aug 2026, 10:17908-1
23 Aug 2026, 09:00909first 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.

فال روز دعا طلسم
@fale_rooz_ost · 118,695
Telegram ranks this channel #27 of 41 here — alongside 40 others — read 1 September 2026
[ استوری ] +
@stoooryfake · 54,728
Telegram ranks this channel #58 of 61 here — alongside 60 others — read 23 August 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 13 October 2026 — this entry's latest reading, not the date you are reading this.

“You and? ⸸‌” (@vaslaty), 480 subscribers as measured 13 October 2026. Telegram Register, tgregister.com/channel/vaslaty.

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.