можно удалить переписки, заблокировать, избегать встреч, но что ты сделаешь с воспоминаниями?

Channel
𝓛𝓸𝓻𝓸
@venerazss
On this record: Topic · Growth · Engagement · Posts · Cite this entry
553subscribers
-60 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002205612116 |
|---|---|
| Type | Channel |
| Username | @venerazss |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 2 October 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 2 October 2026 |
| On Telegram | t.me/venerazss |
Topic
Memes & entertainment — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 66% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Oct 2026, 17:19 | 553 | -14 |
| 17 Sept 2026, 08:42 | 567 | -3 |
| 10 Sept 2026, 01:00 | 570 | -3 |
| 31 Aug 2026, 03:46 | 573 | -8 |
| 24 Aug 2026, 16:03 | 581 | -17 |
| 16 Aug 2026, 03:25 | 598 | -14 |
| 8 Aug 2026, 08:36 | 612 | -1 |
| 8 Aug 2026, 03:03 | 613 | no change |
| 7 Aug 2026, 16:23 | 613 | first reading |
Engagement
20 posts held, back to 19 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
кого-то разлучает боль, а нас разлучит август
«значит так суждено» сказала я и потом долго смотрела на небо.
Если вы влюблены в Луну, перестаньте смотреть на звёзды)
все уходят, но ты не уходи.
я даже смог простить своих врагов, но почему тебя простить не смог?
Я скучаю по нашим ночным разговорам..
в конце концов я выберу того, кого волнует, почему я молчу, а не того, кто будет молчать в ответ
то, что не предназначено тебе разочарует тебя тысячу раз, пока ты не поймешь.
не знаю, написано ли тебе быть на моей судьбе или нет, но я не могу выкинуть тебя ни из головы. ни из сердца.
И тот кто вчера дарил счастье сегодня становится шрамом на душе.
скучаешь? тогда позвони мне посреди ночи, и скажи, что не можешь без меня уснуть)
Showing the 12 most recent of 20 posts we hold for @venerazss. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
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 October 2026 — this entry's latest reading, not the date you are reading this.
“𝓛𝓸𝓻𝓸” (@venerazss), 553 subscribers as measured 2 October 2026. Telegram Register, tgregister.com/channel/venerazss.
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.