Channel
@spiortoe
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
50subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001479596330 |
|---|---|
| Type | Channel |
| Username | @spiortoe |
| Description | Краденное™ из твитора и других отдалённых мест |
| Created | 17 October 2020 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 10 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/spiortoe |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 11:16 | 50 | no change |
| 6 Aug 2026, 22:53 | 50 | first reading |
12 posts held, back to 28 November 2022 — 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 pageof 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 12 posts for this entry, the most recent from 20 May 2023. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 10 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 1 video 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.
The owner of this channel has been inactive for the last 5 months. If they remain inactive for the next 17 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
Смирение — это когда тебе всё равно, умирать ли на диване дома или на больничной койке. Оба варианта безотрадны, потому что крайне болезненны. Так вот, выбора у меня нет. Я почти уже лежачий больной. Скоро мне настанет совсем кранты, и я пишу это сообщение исключительно для того, чтобы уведомить немногочисленную референтную группу, что обратной связи впредь не будет. Но это — последнее разочарование, которое я вам до…
Щтобильная деградация. Открыл для себя h5.tu.qq, но это совсем другая история
Вот почему я такой злой был? Просто Grippus avium у меня не было. От иу.., пардон, индейки, конечно (то, что она — эскпортная / для ВП не исключает вирулентности). Короче, придётся вас оставить без злого, глупого, преходящего на неопределённый срок. Вакцинацию не предлагать. Повторный тромбоз чреват определённостью сроков отсутствия злого, глупого, преходящего — это будет совершенно точно навсегда
Сегодня никаких посиделок за монитором. Да и постоялок тоже. Караул устал, катехонить нечего
Уже первый день Зимы (правда, не ядерной), а я ещё не готов... К чему не готов? Дожить до Рождества, хотя бы (чöртова одышка, симптом пневмонии без всех остальных симптомов)
Я ТРИДЖЦАТЬ ЛЕТ ЖДАЛ ЭТО КИНО!!11расрас
Как много нам отрыжек гнусных дарует интернетов "дух": я-то думал, что Даша "владычица ЯМы с говном" Серенко придумана Баровским, а оне взаправду лично возмущается, будто ей нейросеть "уши спаниеля" пририсовала. Техкомментов не надыть, пожалуйста.
Даша Серенко и нейросексизм @sharanism
Ёбаные двуногие и четверорукие мрази по средам дежурно меня подавляют... ...Хотел зрявтра на кладбище поехать, а придётся, видимо, к гастроэнтерологу.
До чего приятно узнавать (по вторникам в частности), что мы, русские, живём в "стране-спонсоре терроризма", а еврогеи-подпиндосники сруться между собой до последних мегабитов интернета. Повод – тут
Не дожившие до среды просто не вписались в рынок
Showing the 12 most recent of 12 posts we hold for @spiortoe. 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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“Σπίζ)|(εννοη” (@spiortoe), 50 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/spiortoe.
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.