Telegram RegisterThe public register of Telegram

Channel

Склад разработчика

@devs_store

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

11,876subscribers

-12 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001679043200
TypeChannel
Username@devs_store
DescriptionПолезные шпаргалки, курсы, софт и различные инструменты для обучения программированию. Сотрудничество: @web_runner
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live12 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/devs_store

Growth

11,87611,88911,882.57 August 2026 — 11,888 subscribers7 August 2026 — 11,888 subscribers7 August 2026 — 11,889 subscribers8 August 2026 — 11,887 subscribers9 August 2026 — 11,886 subscribers10 August 2026 — 11,882 subscribers11 August 2026 — 11,880 subscribers12 August 2026 — 11,876 subscribers7 August 202612 August 2026
8 measurements spanning 5 days, net -12. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 11,874–11,891 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 17:0311,876-4
11 Aug 2026, 15:4811,880-2
10 Aug 2026, 16:0311,882-4
9 Aug 2026, 12:5111,886-1
8 Aug 2026, 16:2211,887-2
7 Aug 2026, 16:1111,889+1
7 Aug 2026, 06:1511,888no change
7 Aug 2026, 06:0711,888first reading

Engagement

21 posts held, back to 4 March 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 18 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
16.0%
avg views ÷ 11,876 subscribers
Avg views / post
1,900
8 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
8
of 21 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 10 August 2026
Posts held21 (4 March 202610 August 2026)
Views total15,204
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 04:59 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
55
Videos
1
Links
43

Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

10 Aug 2026, 12:18 UTC751 viewsread 13 August 2026
Photo

Самый прогерский канал, где за 10 минут ты научишься: / Пр0бuв по фото и номеру в ТГ // Как взломать вебку подруги /// Мануал по OSINT разведке Ссылка действительна 23 ч. 59 мин. 👇 https://t.me/+mpeDqlACsfgxODJi

10 Aug 2026, 06:13 UTC953 viewsread 13 August 2026
Photo

💻 Журнал Хакер Март 2026 #pentest #books

4 Aug 2026, 05:22 UTC≈1,710 viewsread 13 August 2026
Photo

⚡️ Python для профи. Интерпретаторы, эмуляторы, графика и машинное обучение 7 практических проектов на Python, которые прокачают вас сильнее десятков скучных уроков. Вместо бесконечной теории — реальные проекты с подробным разбором каждого этапа. По мере работы вы разберетесь с ключевыми принципами информатики, улучшите понимание Python и увидите, как все работает на практике. Отличный материал для разработчиков,

23 Jul 2026, 04:39 UTC≈2,200 viewsread 13 August 2026
Photo

🚀 Алгоритмы на Go — от базовых структур данных до распределённых систем и криптографии. Если хотите не просто писать код на Go, а понимать, как работают алгоритмы под капотом, этот материал станет отличной отправной точкой. Внутри: 💬 Основные структуры данных и идиоматичный стиль разработки на Go. 💬 Алгоритмы поиска, сортировки и сжатия данных. 💬 Принципы работы распределённых систем и способы предотвращения конфл

17 Jul 2026, 05:00 UTC≈2,470 viewsread 13 August 2026
Photo

🤖 Claude AI для начинающих В этом практическом руководстве без сложных терминов показано, как перейти от первых запросов к уверенному использованию ИИ в повседневной жизни и работе. Внутри: • Чем Claude отличается от Google и ChatGPT и в каких задачах он действительно сильнее. • Как использовать его для написания писем, планирования путешествий, разбора сложных документов и решения десятков ежедневных задач. • Как

15 Jul 2026, 05:08 UTC≈2,170 viewsread 13 August 2026
Photo

🖥 Создание сайта, его SEO-продвижение и монетизация. Самоучитель Полное руководство по созданию сайта на WordPress — от покупки домена до первых посетителей и заработка. Внутри: 🟢Выбор хостинга и регистрация домена. 🟢Установка и настройка WordPress. 🟢Работа с темами оформления и плагинами. 🟢Наполнение сайта контентом и базовая SEO-оптимизация. 🟢Подключение аналитики Яндекс Метрики и Google Analytics. 🟢Продвижение с

3 Jul 2026, 05:01 UTC≈3,010 viewsread 13 August 2026
Photo

💬 Изучаем SQL за месяц, занимаясь один час в день Практический материал поможет освоить один из самых востребованных языков для аналитики данных и работы с реляционными базами, включая PostgreSQL, SQL Server и Oracle. Внутри — 24 коротких урока, которые последовательно проведут от самых основ до уверенного написания SQL-запросов. 🟢извлечение данных из таблиц; 🟢фильтрацию, сортировку и группировку; 🟢обработку и пре

16 Jun 2026, 12:52 UTC≈2,950 viewsread 13 August 2026
Forwarded from @python2dayPhoto

😎 Парсим ЛЮБОЙ бизнес из Гугл карт и зарабатываем на данных ✅ Собираем адреса, телефоны, сайты, рейтинги, отзывы и другую полезную информацию из тысяч компаний! 💰 Тонны готовых данных можно использовать в коммерческих целях: 💬 поиска клиентов, 💬 анализа конкурентов, 💬 создания собственных баз компаний, 💬 CRM-систем, 💬 телеграм-ботов, 💬 маркетинговых исследований и других задач автоматизации бизнеса. https://youtu.

15 Jun 2026, 05:32 UTC≈3,140 viewsread 13 August 2026
Photo

🧠 Глубокое обучение и анализ данных. Практическое руководство Хотите разобраться в нейросетях на практике? Подробное руководство по глубокому обучению, которое показывает весь путь — от базовых принципов работы нейронных сетей до создания собственных AI-приложений на Python. ✅ Построение нейронных сетей с нуля. ✅ Практика на задачах компьютерного зрения и обработки текста. ✅ Работа с PyTorch, TensorFlow и Keras. ✅

8 Jun 2026, 08:43 UTC≈3,540 viewsread 13 August 2026
Photo

💻 Linux для администраторов Подробное руководство по Linux для системных администраторов и разработчиков. Материал охватывает весь путь — от первых команд в терминале до работы с облачной инфраструктурой, контейнерами и виртуализацией. Внутри: 🟢Установка Linux и работа с файловой системой. 🟢Командная строка и управление пакетами. 🟢Bash-скрипты и автоматизация рутинных задач. 🟢Настройка безопасности, прав доступа и

Showing the 12 most recent of 21 posts we hold for @devs_store. 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.

Citation-graph rank

Citation-graph rank — 1,025,412 of 1,160,990entries 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.

Forward network

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.

Mentions

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.

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.

Cite this entry

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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“Склад разработчика” (@devs_store), 11,876 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/devs_store.

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.