Channel
@perekatipole_tuda
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
514subscribers
+49 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001244925330 |
|---|---|
| Type | Channel |
| Username | @perekatipole_tuda |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/perekatipole_tuda |
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 21 September 2026 and assigned it the closest of 31 fixed categories, at 58% 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 |
|---|---|---|
| 19 Sept 2026, 17:21 | 514 | +18 |
| 11 Sept 2026, 18:21 | 496 | +10 |
| 3 Sept 2026, 09:24 | 486 | +1 |
| 27 Aug 2026, 13:54 | 485 | -1 |
| 20 Aug 2026, 00:16 | 486 | +7 |
| 13 Aug 2026, 03:55 | 479 | +13 |
| 6 Aug 2026, 19:20 | 466 | +1 |
| 6 Aug 2026, 19:03 | 465 | no change |
| 6 Aug 2026, 11:05 | 465 | first reading |
18 posts held, back to 28 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 18 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
74 reactions across 12 posts, in 12 distinct kinds. The most used accounts for 27.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😁 | 20 | 27.0% | |
| 🔥 | 18 | 24.3% | |
| ❤ | 12 | 16.2% | |
| 🤡 | 5 | 6.76% | |
| 🤣 | 4 | 5.41% | |
| 🍌 | 3 | 4.05% | |
| 💘 | 3 | 4.05% | |
| 😱 | 3 | 4.05% | |
| 🍓 | 2 | 2.70% | |
| 🤔 | 2 | 2.70% | |
| 💯 | 1 | 1.35% | |
| 🥰 | 1 | 1.35% |
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 13 of the 18 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 74 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 28 July 2026 to 6 August 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.
Блогер Афанасьев - ум, честь и совесть нашей эпохи. Ему бы в депутаты. Но вообще ситуация комичная, учитывая, что написал коллега экспертиза сотрудников МВД базировалась на анализе сайта регионального Правительства, где не нашла высказываний губернатора Вячеслава Федорищева, цитируемых блогером. Однако подобные высказывания губернатора нашлись на сайте Самарской Губернской Думы. Отчего возникает много вопросов к ква…
🤔2❤1😁1
Склад Wildberries под Самарой совсем всё, говорят. Зато есть возможность в деталях посмотреть, как оно было. Жалко.
Тульским созидателям на заметку. Все средства хороши, можно тиражировать на уровень межрегиональной конкуренции и отрядить блогеров топить саратовских и татарстанских бракоделов, чтобы на их фоне выглядеть по красоте.
😁3🍌1
Блогер Афанасьев настойчиво пытается канализировать все происходящее в какие-то общепринятые аналитические рамки, что-то осмыслить и сформулировать в длиннопостах, а мог бы просто хихикать. Мне кажется, что это занятие столь же энергозатратное, сколь и бессмысленное. На серьезных щах обдумывать то, что было сказано в рандомном порядке, сиюминутно и без цели исполнить - невозможно. Достаточно напомнить про невыполненн…
🔥2💯1
Кстати, Михаил Смирнов никуда не делся с небосвода, в отличие от большинства своих коллег по тульской команде созидания. Он жив, здоров, работает. Уходя, он высказался страшно: Настоящее созидание в такой искореженной среде стало невозможным. Проблемы, стоящие перед регионом, в действительности не решаются, их лишь локально и при этом чересчур демонстративно латают заплатками. Пока это позволяют ранее накопленные бюд…
❤4
Блогер Афанасьев, ставший локальным мемом и прославившийся длиннопостами про страх и ненависть в человейниках, решил, что деньги не пахнут, и быстренько взял рекламу этих самых человейников. История про крестик и трусы как она есть.
😁5❤2
Так приходит земная слава
😁😁😁 Блогер Афанасьев превратился в мэм.
🔥7😁3
Козаренко не даст соврать! Умение делать своевременные и саркастические заявления - это фирменный стиль, а он либо есть, либо нет. И в нашем случае он есть. Врожденный.
❤2
В общем, все понятно. Переклейщиков этикеток в регион привели при прежней администрации. Просто как-то так вышло, что соглашение с ними пришлось подписывать Вячеславу Андреевичу. И потом в советники брать их главного. "Мы сейчас должны с Вами совместную работу построить более плотно. Приглашаю Вас стать моим помощником на общественных началах. Прошу Вас внимательно посмотреть на то, как в целом правительство региона…
😁6🔥5
Лучший политик Самарской области и будущий спикер Губернской думы Вячеслав Романов как и обещал провел встречу с жильцами многострадального дома 14 на пр. Масленникова. Встреча прошла в Белом доме, без опозданий. К разговору пригласили и собственников жилья, и представителей УК. Зампред Правительства без колебаний занял сторону людей в конфликте с управляющей компанией. Пообещал коммунальщикам неприятности, если они …
🤡5🤣4💘3🍓2🥰1
Это те самые, которых собирались от налогов освободить? А директор этой конторы был советником губернатора? Не фартануло, конечно.
😁2
Showing the 12 most recent of 18 posts we hold for @perekatipole_tuda. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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 2 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.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 8 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“Перекати-поле” (@perekatipole_tuda), 514 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/perekatipole_tuda.
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.