«я тебя в обиду не дам, я тебя сам обижу»

Channel
малиновый закат
@zakaaaaat
On this record: Topic · Growth · Engagement · Posts · Cite this entry
84subscribers
-4 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001254265813 |
|---|---|
| Type | Channel |
| Username | @zakaaaaat |
| Created | 5 July 2019 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 9 August 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 2 times, most recently 7 October 2026 |
| On Telegram | t.me/zakaaaaat |
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 27 September 2026 and assigned it the closest of 31 fixed categories, at 48% 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 |
|---|---|---|
| 26 Sept 2026, 13:19 | 84 | -2 |
| 13 Sept 2026, 10:39 | 86 | -1 |
| 14 Aug 2026, 21:14 | 87 | -1 |
| 9 Aug 2026, 15:31 | 88 | no change |
| 6 Aug 2026, 17:41 | 88 | first reading |
Engagement
20 posts held, back to 21 February 2024 — 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 22 May 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
давай я дам тебе 2 шанс и ты снова сломаешь меня
иллюзии рушатся, когда осознаешь, что люди прекрасно понимают последствия своих поступков
говорила мне что-то щемящее о любви, ну а я стоял, неприступен, холоден, как скала, хотя сердце внутри кричало, ревело, ухало, а потом она замолчала, и как-то незаметно вдруг от меня ушла. а удержать её мне, наверное, не хватило духу.
способный чувствовать - этим и наказан
«я горела, а ты пришел и обвинил меня в запахе пепла»
насмотрелась сериалы, где он ради нее сжигает весь мир. и надо возвращаться в реальность, где «ну я не писал, потому что ты не писала»
хочу, чтобы каждая моя слёза ломала тебе кости
тянешь руку помощи человеку, а он ее, сука, грызет
я готов поджигать за тобой окурки, чтобы чувствовать вкус твоих губ
"я тебя любил, а ты меня не очень"
раздаешь советы, как быть счастливым, а сам плачешь по ночам.
Showing the 12 most recent of 20 posts we hold for @zakaaaaat. 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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“малиновый закат” (@zakaaaaat), 84 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/zakaaaaat.
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.