Telegram RegisterThe public register of Telegram
Telegram profile photo for Абстрактный программист (анонсы стримкастов)

Channel

Абстрактный программист (анонсы стримкастов)

@aproger_ru

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

33subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002062776926
TypeChannel
Username@aproger_ru
DescriptionВ этом канале новости и анонсы. Стримкасты по программированию и темам, связанным с программированием. #Backend, #Frontend, #DBA, ...
Created14 February 2024measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live16 August 2026
Measurements held2
On Telegramt.me/aproger_ru

Growth

337 August 2026 — 33 subscribers11 August 2026 — 33 subscribers7 August 202611 August 2026
2 measurements spanning 3 days. 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 32–34 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 01:0233no change
7 Aug 2026, 15:4933first reading

Engagement

13 posts held, back to 14 February 2024the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 13 posts for this entry, the most recent from 25 April 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
4
Links
8

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

Reaction mix

3 reactions across 2 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍3100.0%

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

Measured over the 13 most recent posts we hold, published 14 February 2024 to 25 April 2025, 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

25 Apr 2025, 15:50 UTC295 viewsread 11 August 2026

Через примерно 10 минут начинаем Ссылка на стрим: https://www.youtube.com/watch?v=Zg8d7Rwr7MA

24 Apr 2025, 07:06 UTC965 viewsread 11 August 2026

Всем привет! Сегодня в 19:00 мск - Разбираем, почему isActive = true — это не всегда просто про «активен» и как Enum в PHP может спасти от запутанных условий и магических чисел. Участники: Алексей М., Станислав Ракчаев, Эдуард Сухарев. В программе: Что скрывается за простыми булевыми флагами? Enum в PHP 8.1+: как, зачем и когда использовать. Жизненный цикл статусов: заказов, пользователей, тикетов. Примеры, анти-п

7 Mar 2025, 16:10 UTC105 viewsread 11 August 2026

Всем привет! Ссылка на PHP стрим по дженерикам и типам данных https://www.youtube.com/watch?v=l5caVAcOQhA

22 Aug 2024, 13:53 UTC≈1,530 views2 reactionsread 11 August 2026
Photo

Всем привет! #Hate #3 Стримхэйт. Будем обсуждать начало DDD. Ну и ещё - что пришлёте - то и обсудим, в лайве, хотите код-ревью, а не, так не). Мы найдём, что обсудить.... Участники: Дмитрий Елисеев, Станислав Ракчаев и может кто-нибудь ещё. Трансляция будет здесь. Дата: 22 августа 2024 Время: 20:00 мск

👍2

14 Aug 2024, 16:34 UTC134 viewsread 11 August 2026
Poll

Нужен завтра (15.08) StreamHate?

  1. Да67%
  2. Нет11%
  3. На следующей неделе - норм22%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

8 Aug 2024, 14:46 UTC143 viewsread 11 August 2026

Всем привет! Продолжаем наши стримкасты, в этот раз новая тестовая серия - хэйт на код. К прошлым ещё вернёмся. #Hate #2 Стримхэйт. Что пришлёте - то и обсудим, в лайве, хотите код-ревью, а не, так не). Мы найдём, что обсудить.... Участники: Кирилл Несмеянов, Дмитрий Елисеев, Станислав Ракчаев. Трансляция будет здесь. Дата: 08 августа 2024 Время: 20:00 мск

24 Jul 2024, 09:41 UTC702 views1 reactionsread 11 August 2026
Photo

Всем привет! Продолжаем наши стримкасты, в этот раз новая тестовая серия - хэйт на код. К прошлым ещё вернёмся. #Hate #1 Стримхэйт. Что пришлёте - то и обсудим, в лайве, хотите код-ревью, а не, так не). Мы найдём, что обсудить.... Участники: Кирилл Несмеянов, Дмитрий Елисеев, Станислав Ракчаев. Трансляция будет здесь. Дата: 26 июля 2024 Время: 20:00 мск

👍1

11 Jun 2024, 07:19 UTC170 views0 reactionsread 11 August 2026
Photo

Всем привет! Продолжаем наши стримкасты, в этот раз попробуем разобраться с типизацией. #1.1 Стримкаст. Типы и типизирование. ООП. Часть I. Обсудим типизацию, что это такое, какая бывает, зачем нужна. Типы данных в PHP, встроенные типы. Поговорим о том, для чего нужны кастомные типы. Как всё это мешает или помогает при разработке. Конечно, затронем Typhoon. Ответим на вопросы зрителей. Участники: Алексей, Валентин

29 May 2024, 09:08 UTCviews —

Channel name was changed to «Абстрактный программист (анонсы стримкастов)»

29 May 2024, 07:43 UTC149 viewsread 11 August 2026
Photo

Всем привет) Итак, мы начинаем серию стримкастов по программированю. #0.1 Стримкаст. Тесты и тестирование. Часть I. Обсудим тестирование при разработке програмного обеспечения. Какое оно бывает, чем может помочь backend-разработчику, и нужно ли оно ему. Ответим на вопросы зрителей. Участники: Алексей, Юлия, Дмитрий Елисеев, Станислав Ракчаев. Трансляция будет здесь. Дата: 30 мая 2024 Время: 20:00 мск

28 May 2024, 19:23 UTCviews —

Channel name was changed to «Абстрактный программист (анонсы)»

Showing the 12 most recent of 13 posts we hold for @aproger_ru. 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 poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

14 Aug 2024, 16:34 UTCAnonymous Poll9 voters

Нужен завтра (15.08) StreamHate?

  1. Да67%
  2. Нет11%
  3. На следующей неделе - норм22%

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 13 most recent posts we hold, published 14 February 2024 to 25 April 2025. 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.

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

“Абстрактный программист (анонсы стримкастов)” (@aproger_ru), 33 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/aproger_ru.

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.