Education — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 86% 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 51 days, net -93. 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 10,784–10,907 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 32
Measured (UTC)
Subscribers
Change
26 Sept 2026, 17:41
10,798
-16
19 Sept 2026, 15:19
10,814
+1
17 Sept 2026, 02:38
10,813
-9
15 Sept 2026, 00:18
10,822
-3
13 Sept 2026, 11:00
10,825
-6
11 Sept 2026, 15:38
10,831
-1
8 Sept 2026, 21:57
10,832
-4
5 Sept 2026, 17:58
10,836
-1
3 Sept 2026, 20:59
10,837
-4
2 Sept 2026, 09:36
10,841
-4
1 Sept 2026, 08:56
10,845
-2
31 Aug 2026, 08:57
10,847
-1
30 Aug 2026, 12:26
10,848
-2
29 Aug 2026, 10:06
10,850
-3
28 Aug 2026, 10:47
10,853
+2
27 Aug 2026, 08:25
10,851
-1
26 Aug 2026, 07:56
10,852
-11
25 Aug 2026, 10:34
10,863
-1
24 Aug 2026, 11:25
10,864
-4
22 Aug 2026, 22:34
10,868
first reading
Engagement
24 posts held, back to 7 January 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 41 pages of 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 24 posts for this entry, the most recent from 25 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
45 reactions across 9 posts, in 10 distinct kinds. The most used accounts for 31.1% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
14
31.1%
❤
8
17.8%
💩
5
11.1%
🤔
5
11.1%
👏
3
6.67%
🔥
3
6.67%
🎉
2
4.44%
👎
2
4.44%
🖕
2
4.44%
👾
1
2.22%
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 10 of the 24 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 45 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 24 most recent posts we hold, published 7 January 2026 to 25 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.
Advertising
Ad load
8.33%
2 of 24 posts carry an ad marker
Regulatory tokens
2
posts carrying an erid · 2 distinct tokens
Median views · ads
504
over 2 measured posts
Median views · rest
1,260
over 22 measured posts
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
Advertising tokens recorded on this entry
erid
Posts
First seen
Last seen
2Vtzqvo3AL3
1
25 August 2026
25 August 2026
2W5zFJhHV7P
1
15 July 2026
15 July 2026
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 24 most recent posts we hold, published 7 January 2026 to 25 August 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Статья дня. Функция any() в Python
Часто в программах на Python требуется проверить, является ли хотя бы один элемент структуры данных истинным. Да, можно написать цикл для перебора итерируемого объекта и проверки того, является ли каждый элемент истинным или ложным. Но функция any() – более эффективный и питонический способ достижения того же результата.
Читать статью
#читать
🔍Тестовое собеседование на Middle Python с разработчиком из Яндекса завтра вечером
Уже завтра вечером в 19:00 по мск приходи онлайн на открытое собеседование, чтобы посмотреть на настоящее интервью на Middle Python-разработчика.
Как это будет:
📂 Хачатур, старший разработчик в Яндексе, будет задавать реальные вопросы и задачи разработчику-добровольцу
📂 Хачатур будет комментировать каждый ответ респондента, чтобы дат…
Как найти все четные числа в списке за одну строку кода?
evens = [x for x in [1, 2, 3, 4, 5, 6] if x % 2 == 0]
print(evens) # [2, 4, 6]
Какой ваш вариант решения?
One Day Offer для Python-разработчиков!💚
15 августа открываем двери в команду Agent Execution Framework ⚡️
Коллеги создают платформу для GenAI‑агентов в банке — делают так, чтобы ИИ реально работал в серьёзных финпроцессах: с безопасностью, нагрузкой и пользой.
Чем предстоит заниматься:
✔️ развивать backend на Python
✔️ подключать LLM, инструменты, базы знаний и RAG
✔️ строить пайплайны оценки качества агентов
✔️…
Showing the 12 most recent of 24 posts we hold for @pythonboost. 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.
Polls
The 6 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
Ошибка, здесь больше одного оператора return в одном блоке try-finally20%
Посмотреть ответ10%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 24 most recent posts we hold, published 7 January 2026 to 25 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Mentions
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.
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.
Pythonist.ru - образование по питону @pythonist_ru · 24,046 Telegram ranks this channel #3 of 82 here — alongside 81 others — read 17 September 2026
Python Academy @python_academy · 44,284 Telegram ranks this channel #9 of 87 here — alongside 86 others — read 28 August 2026
Python обучающий @pythonist24 · 55,872 Telegram ranks this channel #39 of 88 here — alongside 87 others — read 23 August 2026
Однажды в трендах @trendo · 67,788 Telegram ranks this channel #42 of 90 here — alongside 89 others — read 20 August 2026
Senior Python Developer @seniorpy · 39,864 Telegram ranks this channel #56 of 92 here — alongside 91 others — read 30 August 2026
КЛУБ | ENGLISH GALAXY | АНГЛИЙСКИЙ ЯЗЫК ПО ПЛЕЙЛИСТАМ @englishgalaxy_school · 76,835 Telegram ranks this channel #65 of 83 here — alongside 82 others — read 19 August 2026
This channel appears in 6 seed channels' Telegram-generated recommendation lists in total. 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 26 September 2026 — this
entry's latest reading, not the date you are reading this.
“PythonBoost - сообщество питонистов” (@pythonboost), 10,798 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/pythonboost.
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.