Channel
@dev_rush
On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry
707subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001334524522 |
|---|---|
| Type | Channel |
| Username | @dev_rush |
| Created | Between 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 21 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 21 August 2026 |
| On Telegram | t.me/dev_rush |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 21 Aug 2026, 02:47 | 707 | +1 |
| 15 Aug 2026, 02:54 | 706 | -1 |
| 8 Aug 2026, 02:17 | 707 | no change |
| 7 Aug 2026, 11:16 | 707 | first reading |
20 posts held, back to 26 September 2024 — 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 20 posts for this entry, the most recent from 28 June 2025. An engagement rate over an empty window would be a number about nothing.
130 reactions across 9 posts, in 9 distinct kinds. The most used accounts for 31.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 41 | 31.5% | |
| 🔥 | 37 | 28.5% | |
| 👍 | 28 | 21.5% | |
| 👏 | 14 | 10.8% | |
| 💔 | 4 | 3.08% | |
| ⚡ | 2 | 1.54% | |
| 🥰 | 2 | 1.54% | |
| 🏆 | 1 | 0.769% | |
| 🙏 | 1 | 0.769% |
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 9 of the 20 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 130reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 26 September 2024 to 28 June 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @dev_rush. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 20 most recent posts we hold for this entry, published 26 September 2024 to 28 June 2025. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
🎉 Результаты розыгрыша: 1-3 место - проход на Swift Marathon 4-6 место - телеграмм премиум 🏆 Победители: 1. Danil (@stimorol_gum) 2. ælina (@cabelun) 3. Aнастасия (@AnnikaDarkness) 4. Danylchenko (@danylchenko_ma) 5. Anatoly (@AnaTolik21) 6. Николай (@Npielie) ✔️Проверить результаты Победителям напишем в ЛС, если у вас ЛС закрыты - просьба написать в поддержку @devrushschool 🙌
❤6👍5👏2🏆1
Друзья, всем привет! 🙌 Уже завтра (29.06) в 14:00 по МСК пройдёт наш первый общий созвон с участниками марафона в закрытом Telegram-чате, на котором мы познакомимся, ответим на все вопросы и начнётся первый спринт. 👨💻 За 3 месяца марафона вас ждёт: - 7 спринтов обучения - 7 индивидуальных челленджей - 3 командных проекта - 15 мини-приложений для оттачивания навыков - 12 общих созвонов и более 20 докладов по т…
🔥3👍2❤1
Разыгрываем 3 билета на финальный Swift Marathon + Telegram Premium Если давно откладывал — сейчас самое время решиться! Призы: - 3 места на участие в SWIFT MARATHON 15 (тариф Swift Basic) - 3 подписки Telegram Premium на 3 месяца 1-3 место - проход на Swift Marathon 4-6 место - телеграмм премиум Как участвовать в розыгрыше: - Подписаться на @coffeeCodeEverywhere и @dev_rush - Нажать кнопку «Участвовать» 🏁 Ито…
👍9🔥5❤4🙏1
Devrush - марафоны программирования. pinned a photo
Друзья, всем привет! 👋 🔥 Мы запускаем наш 15 поток марафона, он будет ПОСЛЕДНИМ и это не шутка! Так что, если вы еще сомневаетесь, то больше шанса поучаствовать не будет) Пора принимать решение! 📆 Длительность: 3 месяца На марафоне ты сможешь учиться и работать в команде, решая задачи, максимально приближенные к реальным. Что тебя ждет: ✅ Еженедельные спринты, где ты будешь учиться новому и сразу применять это …
❤8💔4🔥3⚡2👍2
Live stream finished (1 hour)
Live stream started
Live stream scheduled for Apr 14, 2025 at 17:00
Друзья, всем привет! 👋 Давно нас тут не было, но мы никуда не пропали, участники Swift Marathon 14 проходили свой путь в 3 месяца. 👨💻 Прокачали свои знания и навыки, а так же сделали несколько проектов в команде. 👥 Последние две недели участники писали проект "Movie App" - это приложение "аналог кинопоиска". В котором можно находить фильмы и просматривать трейлеры. В этот раз до финала дошли 6 команд, и уже сего…
🔥9❤4👏4👍1
📱Какие проекты пишут участники? Часто нас спрашивают: какие командные проекты мы будем создавать во время марафона ❓ Ответ: почти всегда это разные проекты, но их объединяют технологии которым участники научились во время изучения базового курса. Например, первый командный челлендж рассчитан всего на 7 дней. За это время команда из 4–6 человек должна: - Научиться работать с Git, - Освоить таск-трекер, - Научиться…
🔥6👏3❤2👍1
Devrush - марафоны программирования. pinned a photo
НОВЫЙ ГОД, НОВЫЕ ЧЕЛЛЕНДЖИ! 🥳 Друзья, всем привет! 👋 🔥 Рады сообщить, что мы запускаем продажи на 14й поток марафона по Swift(UIKit & SwiftUI) 📆 Длительность: 3 месяца На марафоне ты сможешь учиться и работать в команде, решая задачи, максимально приближенные к реальным. Что тебя ждет: ✅ Еженедельные спринты, где ты будешь учиться новому и сразу применять это на практике. 👥 Командные проекты, как на настоящей …
🔥7❤6👍4🥰2
Showing the 12 most recent of 20 posts we hold for @dev_rush. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Citation-graph rank — 917,643 of 1,599,580entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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 21 August 2026 — this entry's latest reading, not the date you are reading this.
“Devrush - марафоны программирования.” (@dev_rush), 707 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/dev_rush.
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.