Русалочка (2023)

Channel
Рай Киномана Нирвана.
@mihail2000
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
1,188subscribers
+120 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002855159508 |
|---|---|
| Type | Channel |
| Username | @mihail2000 |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 27 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 27 September 2026 |
| On Telegram | t.me/mihail2000 |
Topic
Film & TV — 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 18 September 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Sept 2026, 14:36 | 1,188 | +26 |
| 18 Sept 2026, 16:17 | 1,162 | +11 |
| 14 Sept 2026, 16:17 | 1,151 | +8 |
| 11 Sept 2026, 04:40 | 1,143 | +5 |
| 6 Sept 2026, 01:57 | 1,138 | +10 |
| 1 Sept 2026, 11:38 | 1,128 | +9 |
| 29 Aug 2026, 22:18 | 1,119 | +6 |
| 26 Aug 2026, 23:11 | 1,113 | +8 |
| 23 Aug 2026, 15:12 | 1,105 | +3 |
| 19 Aug 2026, 22:28 | 1,102 | +12 |
| 16 Aug 2026, 21:33 | 1,090 | +22 |
| 13 Aug 2026, 12:27 | 1,068 | -2 |
| 10 Aug 2026, 16:26 | 1,070 | +3 |
| 7 Aug 2026, 07:16 | 1,067 | -1 |
| 6 Aug 2026, 13:49 | 1,068 | first reading |
Engagement
10 posts held, back to 5 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 10 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
Турист (2021) Перенос постов Telegram ↔ MAX
Дорожное приключение (2000)
Книга Илая (2010) Перенос постов Telegram ↔ MAX
Мы постоянно куда-то бежим. Закрываем дедлайны, строим планы на пять лет вперед, пролистываем сотни чужих историй в телефоне и пытаемся успеть всё. Нам кажется, что если мы остановимся хотя бы на день, то безнадежно отстанем.Давайте сегодня побудем немного как эта вода. Замедлим шаг. Обратим внимание на небо над головой, на тепло чашки в руках, на людей, которые рядом. Мир не рухнет, если вы уделите полчаса чистой, н…
Жених напрокат (2005) Кросспостинг Telegram ↔ Max
Охота на воров (1-2 часть)
9 рота (2005) Дублировать посты в Max
Иногда прошедший день – как книга, которую не хочется закрывать. Но и после лучшего дня нужен релакс и перезагрузка.
Автоматизация канала
Showing the 10 most recent of 10 posts we hold for @mihail2000. 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.
Mentions
Named by 12 registered channels — 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.
@LivingGadalka · 1,1317 postsSpiritus Immundus
@SpiritusImmundus · 1,2545 postsВсе о еде.
@vse_eda · 9333 postsНумеролог Антонова Валентина.МАТРИЦА СУДЬБЫ. ПРОГНОЗИРОВАНИЕ. РОДОВЫЕ ПЕРЕПЛЕТЕНИЯ.
@tvoj_matrica · 4472 postsОСОЗНАННАЯ РЕАЛЬНОСТЬ. РУНЫ.
@chaika_runi · 7891 postСчастливая дата || МАТРИЦА СУДЬБЫ с Ириной||
@Irina_TheMatrixoffate · 2081 postКулинарный Уголок
@kylinarnyiYgolok · 5391 postХалява,скидки,промокоды
@lavkapromok · 1311 postCoolinAir'ные ночи
@promoCoolinAir · 431 postПуть к Здоровью
@putzdoroviee · 5901 postSing&Speak
@sing_and_speak_eng · 9,5261 postТворческий Уголок
@tvorhesskayaMaster · 4861 post
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.
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 27 September 2026 — this entry's latest reading, not the date you are reading this.
“Рай Киномана Нирвана.” (@mihail2000), 1,188 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/mihail2000.
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.