Telegram RegisterThe public register of Telegram

Channel

IT-школа Skillfactory

@skillfactory

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cross-platform identity · Cite this entry

13,890subscribers

-35 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001113820748
TypeChannel
Username@skillfactory
DescriptionКанал онлайн-школы цифровых профессий. Рассказываем, как выбрать IT-направление и начать карьеру. Делимся советами экспертов и историями студентов. Мы в Max: https://max.ru/skillfactory_bot Ресурс включён в перечень Роскомнадзора
Created12 January 2018measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live14 August 2026
Measurements held10
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/skillfactory

Growth

13,89013,92513,907.56 August 2026 — 13,925 subscribers6 August 2026 — 13,925 subscribers6 August 2026 — 13,923 subscribers8 August 2026 — 13,916 subscribers8 August 2026 — 13,912 subscribers10 August 2026 — 13,906 subscribers11 August 2026 — 13,903 subscribers12 August 2026 — 13,902 subscribers13 August 2026 — 13,900 subscribers14 August 2026 — 13,890 subscribers6 August 202614 August 2026
10 measurements spanning 9 days, net -35. 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 13,885–13,930 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 16:2413,890-10
13 Aug 2026, 07:1513,900-2
12 Aug 2026, 04:0213,902-1
11 Aug 2026, 02:2413,903-3
10 Aug 2026, 00:0113,906-6
8 Aug 2026, 23:1413,912-4
8 Aug 2026, 02:2513,916-7
6 Aug 2026, 23:5713,923-2
6 Aug 2026, 02:3013,925no change
6 Aug 2026, 01:5913,925first reading

Engagement

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

ERR · 30 days
5.48%
avg views ÷ 13,890 subscribers
Avg views / post
762
16 posts measured
Reaction rate
1.13%
reactions ÷ views · ER floor
Posts in window
16
of 16 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. It is computed over the 14 of 16 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 15 August 2026
Posts held16 (17 July 202615 August 2026)
Views total12,186
Reactions total114
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Aug 2026, 11:03 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
3,830
Videos
59
Links
1,420

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

Reaction mix

114 reactions across 13 posts, in 8 distinct kinds. The most used accounts for 32.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3732.5%
🔥2723.7%
😁2421.1%
👍1815.8%
🤔43.51%
🤓21.75%
👏10.877%
👾10.877%

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 14 of the 16 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 114reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 16 most recent posts we hold, published 17 July 2026 to 15 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.

Recent posts

15 Aug 2026, 09:50 UTC124 views6 reactionsread 15 August 2026
Photo

А вы говорите, что нейросети нас заменят...

🤔3😁3

14 Aug 2026, 07:29 UTC345 views2 reactionsread 15 August 2026
Photo

Кто владеет Python, тот владеет миром. И вот почему. ➡️ Простой синтаксис Код легко читать и писать, это ускоряет разработку и делает язык идеальным для новичков. ➡️ ИИ и Data Science На Python написаны популярные библиотеки для работы с нейросетями и данными, например Pandas. Поэтому он монополизировал эту сферу. ➡️ Готовые решения Множество библиотек и фреймворков вроде Django и FastAPI позволяют не писать станд

👍1🔥1

12 Aug 2026, 08:17 UTC500 views10 reactionsread 15 August 2026
Photo

Звучит как хруст чипсиков, но нет. Кранч — это неприятное время, когда вы с коллегами работаете по 60–80 часов, потому что таков дедлайн. Для руководства ситуация может быть ок, но для вашей психики — вряд ли. Кранчи становятся причиной выгораний и высокой текучки кадров. Хотя есть и те, кому нравится с головой уходить в проект. Если вы не из их числа, переходите к третьему абзацу. Кранчи чаще всего случаются из-з

👍5🔥21👏1👾1

10 Aug 2026, 11:33 UTC605 views6 reactionsread 15 August 2026
Photo

#важное_напоминание

5👍1

8 Aug 2026, 11:41 UTC723 views29 reactionsread 15 August 2026
Photo

Кто работал дома у родителей подскажите, это правда?

12😁11👍4🤓2

7 Aug 2026, 09:36 UTC783 views11 reactionsread 15 August 2026
Photo

За несколько недель до конца лета новую профессию не освоить. А вот понемногу «вкатываться» в нее очень даже можно. Сделали подборку из пяти книг, которые стоит прочитать на старте IT-карьеры программиста. Особенно интересны будут джунам и тем, кто только собирается им быть. Но опытным тоже понравится. Рекомендуем. Если интересуетесь программированием, приходите учиться, а заодно и опыт сразу получать. #почитать

👍5🔥51

5 Aug 2026, 08:35 UTC757 views11 reactionsread 15 August 2026
Photo

У нас пополнение. Еще один сильный проект сделали студенты Skillfactory на хакатоне. (Тут напомним, что они проходят регулярно — так учащиеся получают настоящий опыт работы.) Заказчики из компании Neoflex принесли задачу: сделать MVP ИИ-сервиса для автоматической проверки тестовых заданий. Какое решение предложили наши студенты, как работали над сервисом и что в итоге сказал заказчик, — об этом кратко рассказали в

6🔥3👍2

3 Aug 2026, 08:01 UTC737 views7 reactionsread 15 August 2026
Photo

#важное_напоминание

🔥7

31 Jul 2026, 06:45 UTC895 views4 reactionsread 15 August 2026
Photo

Если на рабочем столе вы обнаружили шаманский бубен или банку с кофе, значит, вы системный администратор и сегодня ваш день. С праздником! Для тех, кто не в курсе, рассказываем: традиция поздравлять сисадминов появилась в июле 2000 года. Тогда американец Тед Кекатос впервые устроил пикник для коллег, чтобы поблагодарить за работу. История повторилась через год уже в нескольких компаниях, а позже выбралась за предел

2😁2

29 Jul 2026, 09:02 UTC771 views10 reactionsread 15 August 2026
Photo

Более 83 миллионов пользователей и 200 миллионов проектов — GitHub давно стал главным инструментом для хранения кода и совместной разработки. Почему же он так популярен? GitHub — облачная платформа, где разработчики хранят проекты, работают над ними вместе и делятся своими решениями. По сути, это аналог Google Docs, только вместо текста — программный код. GitHub позволяет изучать открытый код, участвовать в чужих

9🔥1

24 Jul 2026, 09:41 UTC970 views12 reactionsread 13 August 2026
Photo

Рассказывайте в комментариях о самом необычном месте для рабочих созвонов 📲 Читайте нас в Max

😁8🔥3🤔1

Showing the 12 most recent of 16 posts we hold for @skillfactory. 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 — 253,544 of 1,478,351entries 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 4 registered channels — 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.

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.

Cross-platform identity — Wikidata

A Wikidata item names this Telegram handle as belonging to the entity it describes. This is Wikidata’s claim, not a verification made by this register — nobody here confirmed that the account is genuinely operated by the entity named. Wikidata content is CC0; every fact below is dated to when it was read from Wikidata, not to when the association was first made there.

Q6130280 on Wikidata, read 9 August 2026
LabelSkillfactory
DescriptionRussian online education company
X / Twitter@skillfactoryru
YouTubeUClOTq6XN8g7-16QLGnZ6_EA
Official sitehttps://www.skillfactory.ru/

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

“IT-школа Skillfactory” (@skillfactory), 13,890 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/skillfactory.

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.