28 measurements spanning 30 days, net +1,296. 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 12,449–14,133 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 28
Measured (UTC)
Subscribers
Change
6 Sept 2026, 00:58
13,939
+86
3 Sept 2026, 23:42
13,853
+67
2 Sept 2026, 17:14
13,786
+41
1 Sept 2026, 13:17
13,745
+48
31 Aug 2026, 11:57
13,697
+36
30 Aug 2026, 14:47
13,661
+41
29 Aug 2026, 16:46
13,620
+33
28 Aug 2026, 18:55
13,587
+45
27 Aug 2026, 20:08
13,542
+69
26 Aug 2026, 23:23
13,473
+69
25 Aug 2026, 23:35
13,404
+18
25 Aug 2026, 03:04
13,386
+77
23 Aug 2026, 20:55
13,309
+49
22 Aug 2026, 06:47
13,260
+86
20 Aug 2026, 22:56
13,174
+74
19 Aug 2026, 20:12
13,100
+55
18 Aug 2026, 19:37
13,045
+54
17 Aug 2026, 18:24
12,991
+24
16 Aug 2026, 15:57
12,967
+50
15 Aug 2026, 02:53
12,917
first reading
Engagement
37 posts held, back to 27 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 48 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
27.4%
avg views ÷ 13,939 subscribers
Avg views / post
3,820
26 posts measured
Reaction rate
1.42%
reactions ÷ views · ER floor
Posts in window
26
of 37 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 2 September 2026
Posts held
37 (27 July 2026 – 2 September 2026)
Views total
99,320
Reactions total
1,413
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
2 Sept 2026, 19:47 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.
Reaction mix
1,819 reactions across 37 posts, in 31 distinct kinds. The most used accounts for 31.4% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
572
31.4%
❤
375
20.6%
👍
349
19.2%
🌚
176
9.68%
🤓
107
5.88%
✍
49
2.69%
🎉
49
2.69%
🏆
19
1.04%
🤝
18
0.99%
👀
15
0.825%
⚡
12
0.66%
🐳
11
0.605%
👨💻
11
0.605%
🌭
8
0.44%
🆒
6
0.33%
💯
6
0.33%
😭
6
0.33%
🎃
4
0.22%
👏
3
0.165%
👻
3
0.165%
11 further kinds
20
1.10%
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 37 of the 37 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,819 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 37 most recent posts we hold, published 27 July 2026 to 2 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.
Го прокачивать резюме!
Я договорился с Юрой из "Классный кандидат!" провести совместный стрим, где мы будем смотреть все резюме, которые вы отправите в комментариях под этим постом 👇
Прошлый стрим длился 3 часа, и мы успели посмотреть 35 резюме. А также делились опытом и нюансами, которые помогали выбить больше собеседований.
За лето в комьюнити мы собрали 700+ собеседований, и если получится добиться хотя-бы небо…
Не знаю завидовать или нет тем кто идет сейчас в универы, потому что у нас летом на рынке был пожар 🔥
Как мы провели лето
Июнь: 219 собеседований, 20 офферов, 18 в рублях и 2 в долларах
Июль: 230 собеседований, 15 офферов, 14 в рублях и 1 в евро
Август: 262 собеседования, 16 офферов, 13 в рублях и 3 в долларах
Количество собеседований по сравнению в весной сильно выросло, но конверсия в прохождение упала. Поэтому е…
Удивляетесь с задач выше? Мы тоже 😁
Поэтому сегодня мы проведем livecoding стрим, где соберем самые ядреные, но при этом реальные задачи которые встречались на собеседованиях.
В них мало кода, но много проблем. И они прокачивают знание языка похлеще больших кодовых баз, заставляют прочитать и вспомнить много нюансов.
Сегодня в 20:00 мы прорешаем их вместе с вами, и вместе разберемся в каждом нюансе, который может …
Вот и исполнилось мне 28 🎂
Мои 27 были бесконечной гонкой, мы провели больше 100 стримов(я считал), забрали 166 офферов, разобрали сотни резюме и задач,
и пока я топил за результат и достижение целей, по пути собралось еще и самое классное, талантливое и по-настоящему амбициозное комьюнити.
Я уже сбился со счету, сколько раз мы встречались в Питере и Москве в сумме, но я каждый раз кайфую от общения, и решения зад…
Аж 11 человек принимают оффер за один месяц ✊
И еще есть целая неделя впереди
На 90% удаленка, только один оффер в офис в регионе, и по иронии судьбы это единственный оффер от которого мы отказались в августе 🌚
220 -> Fullstack в офис, в регионе
255 -> Удаленка по РФ
2500$ -> Вроде удаленка
371к + премии, бигтех e-commerce, удаленка
250к на Vue удаленка
200к на Angular удаленка
160к на React удаленка
240к на Vue, у…
Город засыпает, Белорусская мафия просыпается 👻
Когда живешь в РБ, иногда вообще непонятно где искать работу, на месте, в России, или в Европе
Именно с этой проблемы мы и начали работу с Аней, и решили искать везде 😅
И подводя итоги недели по собеседованиям и офферам, заметил что статистически наша стратегия оказалась самой эффективной 😶🌫️ Просто искать везде
Какие-то собесы были с rabota.by, какие то по реферал…
Добрались до договора Алабуги 🗿
То есть женатым можно крутить романы на работе, а одиноким нет?)
Ред флаг? 🚩Или база?
🌚39🤓12👀10🌭5🎃3🤗3🐳2💅2
Showing the 12 most recent of 37 posts we hold for @frontend_punks. 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 3 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.
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 37 most recent posts we hold, published 27 July 2026 to 2 September 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.
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 7 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.
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 6 September 2026 — this
entry's latest reading, not the date you are reading this.
“Тихон | Помогаю разработчикам устроиться в BigTech” (@frontend_punks), 13,939 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/frontend_punks.
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.
