Channel
@velikalientropiya
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
1,790subscribers
-35 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001611781285 |
|---|---|
| Type | Channel |
| Username | @velikalientropiya |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/velikalientropiya |
Personal blog — 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 16 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 03:18 | 1,790 | -4 |
| 14 Sept 2026, 02:36 | 1,794 | +1 |
| 10 Sept 2026, 11:57 | 1,793 | -8 |
| 5 Sept 2026, 13:18 | 1,801 | -1 |
| 1 Sept 2026, 05:56 | 1,802 | -4 |
| 29 Aug 2026, 14:39 | 1,806 | -3 |
| 26 Aug 2026, 19:33 | 1,809 | -9 |
| 24 Aug 2026, 02:13 | 1,818 | -19 |
| 20 Aug 2026, 19:06 | 1,837 | -9 |
| 18 Aug 2026, 04:43 | 1,846 | +2 |
| 14 Aug 2026, 23:14 | 1,844 | +19 |
| 13 Aug 2026, 20:49 | 1,825 | first reading |
15 posts held, back to 4 August 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 15 posts for this entry, the most recent from 12 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 9 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Забрал себе любимого старого козла. Сегодня есть, кому меня убаюкивать перед сном 🎐 „Кое-кто и до сих пор считает, что ваши стихи — трата времени. — А что не трата времени? Некоторые собирают марки или бабушек своих убивают. Мы все просто ждём, занимаемся мелочами и ждём смерти.“
📰 утро приятного абсурда: Приходит неожиданный перевод на карту от неизвестного отправителя из Сербии. Я удивлен и спрашиваю, кто он. Получаю исчерпывающий ответ
🤩❤️ и мои пацаны
Один из самых гениальных диалогов в истории кино ☕️🚬
Скрябин плохого не посоветует
О трагедии
И конечно, культовая сцена из Miami Vice на репите 💗
🌴 Сегодняшний день — на летних вайбах 80-х. Подарите мне толстовку Малибу — я буду любить вас вечно и больше никогда не стану раздеваться
🌙
Ведь мир обманул нас обоих
Дочитал «Наоборот» Гюисманса. Сцена «черного ужина» — лучшее, что есть в этом романе 🖤 :
В столовой стены затянули чёрным, дверь распахнули в сад, по этому случаю также преображённый: аллеи были посыпаны углём, небольшой водоём окаймлён базальтом и наполнен чёрными чернилами, цветник уставлен туей и хвоей. Ужин подали на чёрной скатерти, на столе стояли корзины с тёмными фиалками и скабиозами, горели зелёным огнём канделябры, мерцали свечи в подсвечниках. Невидимый оркестр играл траурные марши, а блюда р…
Showing the 12 most recent of 15 posts we hold for @velikalientropiya. 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.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“Ivan Novikov” (@velikalientropiya), 1,790 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/velikalientropiya.
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.