Technology — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 83% 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.
Growth
32 measurements spanning 41 days, net -70. 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 29,042–29,135 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 32
Measured (UTC)
Subscribers
Change
15 Sept 2026, 21:42
29,053
-5
14 Sept 2026, 05:42
29,058
-4
12 Sept 2026, 15:58
29,062
+2
10 Sept 2026, 17:18
29,060
-11
7 Sept 2026, 18:20
29,071
+6
4 Sept 2026, 15:57
29,065
+1
2 Sept 2026, 23:15
29,064
-3
1 Sept 2026, 23:28
29,067
-4
1 Sept 2026, 02:15
29,071
-5
30 Aug 2026, 05:25
29,076
-2
29 Aug 2026, 05:48
29,078
-4
28 Aug 2026, 07:55
29,082
+3
27 Aug 2026, 06:23
29,079
+2
26 Aug 2026, 08:26
29,077
+1
25 Aug 2026, 09:03
29,076
-9
22 Aug 2026, 17:25
29,085
+8
21 Aug 2026, 11:04
29,077
-1
20 Aug 2026, 11:03
29,078
-7
19 Aug 2026, 12:35
29,085
-1
18 Aug 2026, 15:53
29,086
first reading
Engagement
16 posts held, back to 16 July 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 63 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
14.0%
avg views ÷ 29,053 subscribers
Avg views / post
4,080
4 posts measured
Reaction rate
0.368%
reactions ÷ views · ER floor
Posts in window
4
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.
What these figures were computed from
Window
Rolling 30 days · latest post in window 15 September 2026
Posts held
16 (16 July 2026 – 15 September 2026)
Views total
16,300
Reactions total
60
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
20 Sept 2026, 07:34 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
77
Videos
8
Links
409
Lifetime counters from Telegram’s own channel header, read 20 September 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
1m 47s
Average length
21s
Measured directly from 5 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
295 reactions across 16 posts, in 6 distinct kinds. The most used accounts for 35.3% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
104
35.3%
❤
100
33.9%
👍
86
29.2%
⚡
2
0.678%
💯
2
0.678%
🏆
1
0.339%
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 16 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 295 reactions 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 16 July 2026 to 15 September 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
1
across the posts below
Posts paid on
1
of 16 we hold a reading for · 6%
Most on one post
1
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @gopractice. 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 16 most recent posts we hold for this entry, published 16 July 2026 to 15 September 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.
Как превратить разрозненные источники в связанную базу знаний, которую ведет агент
В AI-мастерской стартовал новый кейс — LLM wiki: ваш новый рабочий инструмент.
Вы узнаете, как с помощью кодинг-агента собрать личную вики — связанный набор страниц по вашей области, который агент пишет и поддерживает сам.
Задачи, которые вы сможете решать:
— Подготовка к обсуждению — собрать все, что коллекция знает по теме встреч…
Выходим на новый уровень работы со знаниями — собираем личную вики, которую ведет AI
Новый кейс AI-мастерской стартует уже на следующей неделе. В нем вы соберете собственную базу знаний, которая не просто хранит прочитанное, а сводит источники между собой, показывает пробелы и расхождения, и помогает принимать решения.
Несколько советов для тех, кто заводит личную LLM-вики:
— Храните вики в обычных текстовых файла…
«Самыми ценными оказываются люди, которые способны брать на себя любую работу, необходимую команде именно сейчас». Ожидания от продакта в эпоху AI: взгляд изнутри Anthropic
Команды, работающие над Claude, не только делают один из передовых AI-продуктов, которым пользуются профессионалы во всем мире, но и одни из первопроходцев новых реалий продуктовой работы в эпоху AI.
Lenny Rachitsky поговорил с Cat Wu, которая р…
Как создать видеоролик с помощью AI. Несколько рекомендаций
1️⃣ Не начинайте сразу с видео. Число неудачных попыток приведет к большим затратам.
Вместо этого превращайте простые формы в более сложные. Сперва сделайте первые кадры всех сцен, убедитесь в их консистентности и соответствии ожиданиям, а лишь после этого — анимируйте.
Собранный таким образом пайплайн даст вам гораздо больше шансов получить желаемое виде…
Выходим на новый уровень владения AI-инструментами — и-ии-ии создаем мультфильм!
Новый кейс AI-мастерской стартует уже на следующей неделе. В нем вы научитесь создавать свой собственный мультфильм — от идеи до готового видео.
Вы можете сказать, что это, конечно, очень классно и замечательно, но вопрос — зачем вам это нужно 🧐
Дело в том, что принципы работы собственной AI-видеостудии универсальны для любых форматов…
Как перенести сервис в облако для себя и для внешней аудитории
В AI-мастерской стартовал новый кейс — перенос сервиса в облако.
В предыдущих кейсах мы создали ряд сервисов, которые работают локально. Но у такого подхода есть ряд ограничений. Например, нельзя выключить компьютер, на котором запущен сервис, а также он остается недоступен другим пользователям.
Решение очевидно — разместить сервис в облаке. Это позвол…
Некоторые профессии — это просто «задачи»
Когда вы автоматизируете задачу, работа исчезает. Классический пример — лифтеры: они управляли рычагом, но когда лифты автоматизировали, профессия исчезла.
Но в большинстве профессий задача, за которую вы думаете, что вам платят, — не то, за что вам платят на самом деле.
Зачем вы нанимаете McKinsey? Чтобы получить презентацию на 75 слайдов? Claude Cowork сделает ее, но это…
От базы вайбкодинга до деплоя своего продукта на внешних пользователей. В AI-мастерской уже доступны три кейса, а четвертый на подходе
Присоединяйтесь к студентам AI-мастерской, чтобы научиться создавать новые AI-продукты, заточенные под ваши задачи — без разработчика.
Проведем вас по всему пути от самой-самой базы до опубликованного сервиса в интернете, которым могут пользоваться ваши клиенты, коллеги или друзья.
…
Ищете возможности применения AI/ML в своем продукте? 🔍
В AI/ML-симуляторе для продакт-менеджеров вы на практике пройдете путь от поиска таких возможностей до запуска AI-решений и оценки их влияния на бизнес.
Татьяна Чикалина и Антон Усов уже прошли симулятор и поделились тем, чем он оказался для них полезен. Их отзывы мы оформили в карточки — листайте выше ⬆️
Если хотите пройти AI/ML-симулятор с поддержкой опытног…
Освойте RAG, чтобы выйти за пределы ChatGPT
Обычно AI-инструменты работают на основе общих знаний модели. Если вы задаете вопрос по конкретной теме, то получите ответ на основе того, что LLM видела во время обучения. Данные могут оказаться устаревшими, неточными или придуманными.
RAG (Retrieval-Augmented Generation) решает эту проблему. Это архитектура, при которой модель не формирует ответ из памяти, а сначала пол…
Выпускница курса «Профессия: продакт-менеджер» Анна Чистякова поделилась своей историей обучения. Мы оформили ее впечатления в карточки — листайте выше ⬆️
Если вы начинающий продакт-менеджер или только задумываетесь о переходе в профессию, присоединяйтесь к студентам программы «Профессия: продакт-менеджер».
На курсе вы получите необходимые знания и практические навыки, которые помогут сделать первые шаги в професси…
Скоро в AI-мастерской: RAG на практике
Через неделю в AI-мастерской стартует новый кейс — RAG на практике: строим AI на своей базе.
Вы освоите RAG — архитектуру, на которой строятся серьезные AI-продукты: система не угадывает ответ из общих знаний модели, а сначала ищет релевантные данные в вашей базе.
Мы разберем это на примере сервиса поиск кофеен в большом городе, где для выдачи релевантного ответа пользователю…
🔥7👍6❤4
Showing the 12 most recent of 16 posts we hold for @gopractice. 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.
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 8 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.
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.
Channels Telegram recommends alongside this one
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 9 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
Epic Growth — рост продуктов @epicgrowth · 26,291 Telegram ranks this channel #1 of 97 here — alongside 96 others — read 12 September 2026
No Flame No Game @proproduct · 38,826 Telegram ranks this channel #2 of 96 here — alongside 95 others — read 31 August 2026
Hire ProProduct - Продуктовые вакансии @hireproproduct · 24,006 Telegram ranks this channel #7 of 98 here — alongside 97 others — read 17 September 2026
ProductDo: практика продакта @productdo · 24,067 Telegram ranks this channel #7 of 97 here — alongside 96 others — read 17 September 2026
Ваня Замесин @zamesin · 50,414 Telegram ranks this channel #10 of 97 here — alongside 96 others — read 25 August 2026
Продукторий Владимира Меркушева @vladimir_merkushev · 22,031 Telegram ranks this channel #11 of 96 here — alongside 95 others — read 21 September 2026
Продакты не нужны @betternotworse · 28,526 Telegram ranks this channel #11 of 96 here — alongside 95 others — read 9 September 2026
Product Management & AI @ruspm · 25,204 Telegram ranks this channel #12 of 97 here — alongside 96 others — read 14 September 2026
Kumar & Solo @solokumi · 37,644 Telegram ranks this channel #15 of 98 here — alongside 97 others — read 1 September 2026
Вправо Вверх 📈 Михаил Табунов @bossofyourboss · 27,735 Telegram ranks this channel #16 of 95 here — alongside 94 others — read 10 September 2026
Яндекс нанимает | Вакансии для PM @ya_jobs_pm · 29,772 Telegram ranks this channel #16 of 98 here — alongside 97 others — read 8 September 2026
Вакансии для продакт-менеджеров @productjobgo · 22,535 Telegram ranks this channel #18 of 96 here — alongside 95 others — read 20 September 2026
Вакансии для продактов и проджектов @product_jobs · 36,067 Telegram ranks this channel #18 of 96 here — alongside 95 others — read 2 September 2026
AgileFluent: карьера без границ @agilefluent · 45,636 Telegram ranks this channel #18 of 95 here — alongside 94 others — read 28 August 2026
Google Таблицы @google_sheets · 60,505 Telegram ranks this channel #29 of 98 here — alongside 97 others — read 22 August 2026
Стартап дня. Александр Горный. @startupoftheday · 60,449 Telegram ranks this channel #30 of 97 here — alongside 96 others — read 22 August 2026
Тёмная сторона / Темнографика @temno · 79,763 Telegram ranks this channel #34 of 99 here — alongside 98 others — read 18 August 2026
Job for Products and Projects @forproducts · 69,619 Telegram ranks this channel #35 of 98 here — alongside 97 others — read 20 August 2026
Менеджер от боженьки @pm_god · 25,223 Telegram ranks this channel #38 of 98 here — alongside 97 others — read 14 September 2026
Job for Chiefs (TOP vacancies) @forchiefs · 38,424 Telegram ranks this channel #40 of 99 here — alongside 98 others — read 31 August 2026
Дизраптор @disruptors_official · 73,061 Telegram ranks this channel #43 of 97 here — alongside 96 others — read 20 August 2026
+1 в команду Яндекс Практикума @practicum_experts · 24,135 Telegram ranks this channel #44 of 98 here — alongside 97 others — read 16 September 2026
🌎 CHOICY.WORK: Global карьера | вакансии | стартапы | удалёнка @choicy_work · 26,960 Telegram ranks this channel #45 of 95 here — alongside 94 others — read 11 September 2026
Без aspera @bezaspera · 73,225 Telegram ranks this channel #45 of 98 here — alongside 97 others — read 20 August 2026
This channel appears in 44 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 15 September 2026 — this
entry's latest reading, not the date you are reading this.
“GoPractice!” (@gopractice), 29,053 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/gopractice.
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.