Telegram RegisterThe public register of Telegram
Telegram profile photo for Артём Шумейко

Channel

Артём Шумейко

@artemshumeiko

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

19,975subscribers

+22 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-1001629983211
TypeChannel
Username@artemshumeiko
DescriptionSenior Backend разработчик. Рассказываю о лучших практиках разработки приложений и делюсь жизнью разработчика Курс по Backend на Python: https://clck.ru/3RHSKg По рекламе: [email protected] Для связи: t.me/artem_shumeiko_support РКН: clck.ru/3SvT2D
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 August 2026
Measurements held11
Confirmed unchanged1 time, most recently 17 August 2026
On Telegramt.me/artemshumeiko

Growth

19,95319,99019,971.57 August 2026 — 19,953 subscribers7 August 2026 — 19,953 subscribers8 August 2026 — 19,968 subscribers9 August 2026 — 19,976 subscribers10 August 2026 — 19,989 subscribers11 August 2026 — 19,972 subscribers12 August 2026 — 19,971 subscribers13 August 2026 — 19,978 subscribers15 August 2026 — 19,986 subscribers16 August 2026 — 19,990 subscribers17 August 2026 — 19,975 subscribers19,9757 August 202617 August 2026
11 measurements spanning 10 days, net +22. 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 19,947–19,996 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Aug 2026, 20:4619,975-15
16 Aug 2026, 18:0419,990+4
15 Aug 2026, 06:3819,986+8
13 Aug 2026, 23:2619,978+7
12 Aug 2026, 14:3419,971-1
11 Aug 2026, 11:5719,972-17
10 Aug 2026, 14:5319,989+13
9 Aug 2026, 12:5119,976+8
8 Aug 2026, 14:4819,968+15
7 Aug 2026, 11:3019,953no change
7 Aug 2026, 11:2719,953first reading

Engagement

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

ERR · 30 days
44.3%
avg views ÷ 19,975 subscribers
Avg views / post
8,850
6 posts measured
Reaction rate
1.64%
reactions ÷ views · ER floor
Posts in window
6
of 22 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 17 August 2026
Posts held22 (13 June 202617 August 2026)
Views total53,080
Reactions total871
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Aug 2026, 03: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
281
Videos
39
Links
307

Lifetime counters from Telegram’s own channel header, read 18 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.

Video runtime
9m 21s
Average length
3m 07s

Measured directly from 3 videos 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.

Reaction mix

1,604 reactions across 22 posts, in 7 distinct kinds. The most used accounts for 29.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥47029.3%
custom 545621030833280090440825.4%
👍36522.8%
29718.5%
custom 5415705042994870029342.12%
👏160.998%
🎉140.873%

Custom emoji. 2 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 areTelegram’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 22 of the 22 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 1,604reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 22 most recent posts we hold, published 13 June 2026 to 17 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.

Telegram Stars

Stars received
3
across the posts below
Posts paid on
3
of 22 we hold a reading for · 14%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @artemshumeiko. 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 22 most recent posts we hold for this entry, published 13 June 2026 to 17 August 2026. 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.

Recent posts

17 Aug 2026, 13:17 UTC≈2,890 views23 reactionsread 18 August 2026
Photo

⚡️ С сегодняшнего дня действует скидка 15% на курсы Школы Pytex до конца августа! Скоро осень, а значит близок сезон самого активного найма новых специалистов. Чтобы достичь новых вершин в карьере, пользуйся скидкой до конца лета и развивайся в разработке. BACKEND РАЗРАБОТКА НА PYTHON За 3 месяца ты пройдешь полный цикл продакшен разработки на Python. Напишешь API на FastAPI, научишься работать с PostgreSQL и SQLAl

custom 5456210308332800904145👍2🔥2

16 Aug 2026, 18:24 UTC≈5,290 views507 reactionsread 18 August 2026

Чего ждать от Python 3.15? Python 3.15 выйдет через полтора месяца, и новые фичи уже зафиксированы, поэтому давайте посмотрим, что интересного появится в следующей версии языка. Ленивые импорты Теперь модуль можно импортировать не сразу, а только в момент, когда он реально понадобится: lazy import aioboto3 print("приложение запустилось") session = aioboto3.Session() # только здесь загрузится код библиотеки aiobot

🔥254👍22220custom 545621030833280090411

10 Aug 2026, 19:20 UTC≈8,500 views208 reactions1 Starread 18 August 2026
Video

Лучшая разгрузка после тяжелого дня

custom 5456210308332800904120🔥58👍15👏8🎉52

6 Aug 2026, 14:01 UTC≈10,900 views33 reactionsread 18 August 2026

SQL — разбираем популярные вопросы с собеседований ➡️ Новое видео: YouTube | VK | Rutube В новом видео разбираю вопросы по SQL, которые часто встречаются на технических собеседованиях на backend-разработчиков: 🟢Чем отличается WHERE от HAVING 🟢 Что такое JOIN и какие виды существуют 🟢 Что такое UNION и UNION ALL и чем они отличаются 🟢 Что такое CTE, подзапросы и временные таблицы 🟢 Как найти дубликаты 🟢 Что такое о

23🔥7👍2🎉1

30 Jul 2026, 10:04 UTC≈12,100 views50 reactionsread 18 August 2026

Топ вопросов по HTTP с собеседований с разбором ответов ➡️ Новое видео: YouTube | VK | Rutube В новом видео я разобрал вопросы по HTTP, которые регулярно задают на собеседованиях на backend-разработчика, а именно: 🟢 POST, PUT и PATCH запросы 🟢 В чем разница между заголовками и куки 🟢 Какие есть уязвимости при работе с куки 🟢 Что такое CSRF-атака 🟢 Что такое CORS 🟢 Как HTTP связан с ограничением запросов 🟢 Какие сп

31👍10custom 54562103083328009048🔥1

22 Jul 2026, 11:16 UTC≈13,400 views50 reactionsread 18 August 2026

Middle из бигтех собеседуется на Python Backend 👉 Новое видео: YouTube | VK | Rutube В новом ролике с приглашенным разработчиком Александром, работающим в бигтехе, провели интервью на Middle Backend. За время собеседования мы успели обсудить проектирование высоконагруженных сервисов, PostgreSQL, индексы и оптимизацию запросов, Python и asyncio, архитектуру приложений, SQLAlchemy, интеграцию с внешними API, тестиро

🔥30custom 5456210308332800904119

4 Jul 2026, 11:12 UTC≈15,500 views227 reactions1 Starread 18 August 2026
Photo

Новый HTTP-метод. 0_о ЧТоОоО?? Все уже давно привыкли к GET, POST, PUT, DELETE и прочим ребятам, как вдруг решили добавить новый метод QUERY! Это не шутка если что. Вот официальный RFC двухнедельной давности. Кому лень читать, кратенько объясню проблематику и почему это классный метод стоит юзать в будущем. Очень часто в GET запросах хочется передать туеву хучу параметров, например, для фильтров, сортировки, поис

custom 5456210308332800904128👍6127🔥6👏5

29 Jun 2026, 10:28 UTC≈10,700 views19 reactionsread 18 August 2026
Photo

ПОСЛЕДНИЙ ДЕНЬ НАБОРА НА КУРС Сегодня в 23:59 по МСК закрываю набор учеников на курс по параллелизму и конкурентности в Python. Курс для тебя, если ты: — Уже работаешь Python-разработчиком, но чувствуешь, что знания по async заканчиваются на async/await и gather — Хочешь увереннее проходить собеседования на Middle/Senior позиции, где спрашивают event loop, GIL, потоки, процессы, очереди и продакшен-кейсы — Работа

custom 545621030833280090494custom 54157050429948700293🎉1👏1🔥1

28 Jun 2026, 13:28 UTC≈8,250 views23 reactionsread 18 August 2026
Photo

Похоже, места на курсе по параллелизму постепенно заканчиваются И уже в понедельник, 29 июня в 19:00 МСК, мы проводим первую онлайн-встречу с участниками курса. Познакомимся, обсудим программу, проект, домашки, формат обучения и вообще поймём, кто все эти люди, которые добровольно решили разбираться с конкурентностью, дедлоками и Kafka 😇 Кстати, на картинке почти реальный состав созвона) Если ты всё ещё в раздумь

custom 5456210308332800904117custom 54157050429948700294👍1

27 Jun 2026, 11:51 UTC≈8,240 views30 reactionsread 18 August 2026

Разбираем тестовое задание для Junior Python Backend разработчика 👉 Новое видео: YouTube | VK | Rutube В новом видео вместе спроектируем API и структуру базы данных, обсудим, как правильно хранить секретные данные, чем отличаются хеширование, шифрование и кодирование, а затем реализуем решение на Python с использованием асинхронности и PostgreSQL. Также поговорим о типичных ошибках, которые допускают начинающие ра

16custom 54562103083328009047custom 54157050429948700295👍2

26 Jun 2026, 10:36 UTC≈6,940 views19 reactionsread 18 August 2026
Photo

А хватит ли мне скилов на курс? Периодически получаю вопросы по типу "блин, а точно ли мне хватит текущих навыков? может сначала ещё подтянуть что-то?" Давай нормально разложу) Для старта тебе нужно иметь минимальный опыт работы с FastAPI, PostgeSQL и Git. Все это осваивается достаточно быстро и это единственные минимальные знания, которые нужны для курса Не нужно заранее идеально знать async, потоки, процессы ил

custom 541570504299487002976custom 54562103083328009045👍1

25 Jun 2026, 10:48 UTC≈6,680 views30 reactionsread 18 August 2026

Куда деть CPU код: костылить в текущем проекте или пилить отдельный микросервис Этим вопросом часто задаются разработчики, когда на работе прилетает таска по типу "создать код по обработке файла/созданию отчета". Сразу скажу: однозначного ответа нет, всё зависит от количества и частоты CPU нагрузки, специфики проекта, и готова ли команда потянуть еще один микросервис) Давайте рассмотрим реалистичную ситуацию, когда

👍1410custom 54562103083328009044🔥2

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

Citation-graph rank — 1,154,440 of 1,548,671entries 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

“Артём Шумейко” (@artemshumeiko), 19,975 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/artemshumeiko.

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.