Channel
@cyberordeath
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
482subscribers
+6 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001330341577 |
|---|---|
| Type | Channel |
| Username | @cyberordeath |
| Created | 30 November 2019 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 26 September 2026 |
| On Telegram | t.me/cyberordeath |
Gaming — 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 45% 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 |
|---|---|---|
| 26 Sept 2026, 07:38 | 482 | +1 |
| 11 Sept 2026, 02:38 | 481 | +1 |
| 1 Sept 2026, 17:35 | 480 | +3 |
| 25 Aug 2026, 17:05 | 477 | -2 |
| 19 Aug 2026, 17:42 | 479 | +2 |
| 13 Aug 2026, 11:14 | 477 | +2 |
| 7 Aug 2026, 07:51 | 475 | -1 |
| 6 Aug 2026, 19:02 | 476 | no change |
| 6 Aug 2026, 17:19 | 476 | first reading |
15 posts held, back to 20 May 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 5 August 2026. An engagement rate over an empty window would be a number about nothing.
325 reactions across 15 posts, in 7 distinct kinds. The most used accounts for 44.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🍌 | 143 | 44.0% | |
| 🔥 | 101 | 31.1% | |
| ❤ | 61 | 18.8% | |
| custom 5224708023435404637 | 10 | 3.08% | |
| 🍓 | 5 | 1.54% | |
| custom 5201936428954561981 | 4 | 1.23% | |
| custom 5402227731972771532 | 1 | 0.308% |
Custom emoji. 3 of the rows above are 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 15 of the 15 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 325 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 20 May 2026 to 5 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.
Видели это прекрасное видео где спортсмен из Сьерра-Леоне дебютирует на треке на Играх Содружества? Сначала он соскальзывает с полотна, а со второй попытки бьет мировой рекорд (нет) Он просто ехал настолько высоко, что не наехал на стартовую линию. Теперь мы с ним друзья в запрещенной соцсети!
🔥9
Signed Denis Bolotov
Ничего не понятно, но очень интересно. С днем нового группсета!
🔥17🍌8🍓3
Signed Denis Bolotov
Зеленоград, 3 августа 2026 открытая тренировка в рамках подготовки в 2 и 3 этапу гонок ЦИКЛОН.ТРЕК в Пензе Программа тренировки: 19-30 Сбор 56.013663,37.145063 https://yandex.ru/maps?whatshere%5Bzoom%5D=18&whatshere%5Bpoint%5D=37.145063,56.013663&si=puehdph3ecrkedrymdpuvmb6aw 20-00 Начало разминки, далее работа на технику: старты с места При себе иметь: исправный трековый велосипед с фиксированной передачей и рулем…
🔥8custom 52247080234354046373❤1
Signed Denis Bolotov
Минутка бесполезной информации: мой напольный насос из декатлона, который служил мне верой и правдой 10 лет, стал травить по корпусу поршня. Накачать им колесо стало практически невозможно, полез внутрь - оказалось просто от времени стерлось уплотнительное кольцо. Фирменное стоит 8 евро, и конечно же достать его проблематично. Кольцо уплонительное резиновое ISO 3601-3 10 штук - 160 рублей на маркетплейсе. Всем спасиб…
❤19🔥6
Signed Denis Bolotov
Пацаны у подъезда сказали что у меня крутой велик
❤20🔥9🍌5custom 52019364289545619812
Signed Denis Bolotov
Напомните мне пожалуйста не называть никаких конкретных сроков, если есть риск их сорвать. Был очень трудный для меня гревел инстинкт, в котором я учавствовал как один из организаторов, все что могло у меня пойти не по плану именно так и пошло: сломалась машина перед выездом, хронометраж отработал сильно хуже чем хотелось. Но выводы все сделаны, работа над ошибками ведется. Нарезал резьбу на 23 коге, поеду кататься…
❤11🔥5custom 52019364289545619812
Signed Denis Bolotov
Кажется шутка зашла слишком далеко. Современные технологии позволяют нам осуществлять 3D печать не только полимерами, но уже и металлами. Завтра нарежу резьбу, чуть уберу облой и продолжаем наши веселые эксперименты.
🍌18🔥13❤5
Signed Denis Bolotov
🚩 РАЗМУСОЛКА 🚩 Велокросс на круговой лесной трассе в часе езды от Москвы. Смелые сразятся за фрейм-сет 🚲SHULZ Morning train to Vyborg и ценные призы, а другие гости мероприятия насладятся природой и хорошей компанией. 🌲 Кэмп и развлечения: 10 мин. от 🚆Красногорская 55.822167, 37.296208 • музыка, • хот-доги на гриле 🌭 • много пива 🍺 • грязный сюрпляс, • гитарка у костра, • навес от дождя, • фото прошлого года 🚵…
🔥3❤2🍌1
Signed Denis Bolotov
Давно меня не было в уличных гонках, пора возвращаться. 5 июля - велокросс Размусолка в Красногорске. Даже не придумал на чем поеду, но зарегистрировался.
🔥5
Signed Denis Bolotov
Еще немножко бананов и оно выезжает на улицу В комментариях лотерея: сколько метров-километров оно проедет пока не сломается. Победитель получит от меня банан
🍌40🍓2custom 54022277319727715321
Signed Denis Bolotov
10 бананов и я ставлю это на велосипед Как раз 65/23 это 2.82 Оно же 76” по трековому
🍌52
Signed Denis Bolotov
Астрологи объявили месяц тяжелых передач, поэтому с днем новых звезд шестерен!
🍌10custom 52247080234354046377🔥5❤1
Signed Denis Bolotov
Showing the 12 most recent of 15 posts we hold for @cyberordeath. 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.
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 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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“Роботы и велосипеды” (@cyberordeath), 482 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/cyberordeath.
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.