Channel
@zapiskisosedamanyaka
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
232subscribers
+2 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002260797541 |
|---|---|
| Type | Channel |
| Username | @zapiskisosedamanyaka |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/zapiskisosedamanyaka |
Other / unclassifiable — 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 23 September 2026 and assigned it the closest of 31 fixed categories, at 71% 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 |
|---|---|---|
| 17 Sept 2026, 11:20 | 232 | +1 |
| 24 Aug 2026, 04:57 | 231 | +1 |
| 8 Aug 2026, 18:03 | 230 | no change |
| 8 Aug 2026, 14:15 | 230 | first reading |
11 posts held, back to 14 June 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 11 posts for this entry, the most recent from 27 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 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.
63 reactions across 11 posts, in 4 distinct kinds. The most used accounts for 87.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5850343174865686224 | 55 | 87.3% | |
| custom 5287278365428947395 | 6 | 9.52% | |
| custom 5197296154877907826 | 1 | 1.59% | |
| custom 5318783359294382499 | 1 | 1.59% |
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 11 of the 11 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 63 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 14 June 2026 to 27 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Дружелюбные соседи, всем привет👋🏻 В новом эпизоде мы не только делились своим мнением, но и заручились профессиональным взглядом специалиста, дабы глубже разобрать озвученные темы🩹 Поэтому ловите дополнительные материалы, где врач-психиатр Анастасия Елова - дает свои комментарии🎙️ А ответы от психолога Екатерины - здесь💡
custom 52872783654289473956custom 51972961548779078261custom 53187833592943824991
Дружелюбные соседи, всем привет👋🏻 Вот и подоспела столь ожидаемая коллаборация с подкастом «Нервотрепка»🎙️ Мы обсудили очень интересную тему, которая актуальна до сих пор!🔥 Доступно на площадках: YouTube🍿 Rutube🍿 VK🍿 Прослушать также можно - на всех актуальных площадках🎧 ТГ канал Нервотрепки🪢 ТГ канал врача-психиатра Анастасии Еловой🩹 Приятного ознакомления!🔥
custom 58503431748656862247
Дружелюбные соседи, всем привет👋🏻 Уверены, что с момента нашей последней встречи, вы соскучились также как и мы, поэтому грядущей осенью у нас вновь появится возможность увидится💫 📍Москва, 10 октября, 2026 г. Билеты🎟️ На данном мероприятии мы не только расскажем интересную лекцию, но и сделаем анонс следующего маньяка, от лица которого будет вестись повествование. И поверьте, этот сезон будет гораздо круче предыд…
custom 58503431748656862243
Дружелюбные соседи, всем привет, на связи Антон👋🏻 Спешу поделиться с вами новой работой, которую я вновь сделал с моей одногруппницей Олесей🎙️
custom 58503431748656862244
Дружелюбные соседи, всем привет👋🏻 Сервис ВК продолжает нас радовать, ведь наш проект залетел в раздел - популярные подкасты⭐️ Благодарим платформу за выбор и конечно, говорим спасибо вам, дорогие слушатели!🖤 Кто еще не подписан на сообщество в ВК - сделайте это, чтобы точно оставаться на связи📣 Двигаемся только вперед!💪🏻
custom 58503431748656862245
Дружелюбные соседи, всем привет, на связи Антон👋🏻 Хочу посоветовать интересный тру-крайм подкаст Не Все Так Просто🎙️ В нем сестры Алина и Жибек не просто пересказывают различные кейсы и дела, они буквально переживают события, делясь настоящими эмоциями, при этом не забывая про самые мелкие детали🙌🏻 Недаром подкст девушек уже дважды попадал в актуальное Яндекс Музыки🔥 Смело переходите и слушайте!🎧
custom 58503431748656862243
Дружелюбные соседи, всем привет👋🏻 Подоспели новые Разговоры на Кухне!🗣️ Отличного воскресенья и приятного прослушивания🎧
custom 58503431748656862244
File, posted without a caption
custom 58503431748656862245
Дружелюбные соседи, всем привет!🎧 Решили немного разнообразить контент и подготовили Вам небольшой «новостной» выпуск из мира трукрайма повседневности (если так можно сказать)🌭 Приятного прослушивания🎧
custom 58503431748656862247
Дружелюбные соседи, все привет👋🏻 Вот и вышел финал нашего сезона про Битцевского маньяка!🔪 Пишите в комментариях свои мнения о прослушанном, а также делитесь пожеланиями о маньяках в следующих сезонах👇🏻
custom 58503431748656862248
Дружелюбные соседи, всем привет👋🏻 Дропнулась новая часть об Александре Пичушкине🔨 Она получилась крайне насыщенной на события💣 Желаем увлекательного прослушивания и отличного воскресенья🔥
custom 58503431748656862249
Showing the 11 most recent of 11 posts we hold for @zapiskisosedamanyaka. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“Записки Соседа - Маньяка” (@zapiskisosedamanyaka), 232 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/zapiskisosedamanyaka.
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.