Telegram RegisterThe public register of Telegram
Telegram profile photo for Дмитрий Балакирев

Channel

Дмитрий Балакирев

@dimabalakirev

Verified by Telegram

On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry

877subscribers

+11 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001333345255
TypeChannel
Username@dimabalakirev
Created10 September 2018 — measured — cross-checked against a third-party dataset (TGDataset)
First recorded6 August 2026
Last confirmed live7 October 2026
Measurements held7
Confirmed unchanged1 time, most recently 7 October 2026
On Telegramt.me/dimabalakirev

Topic

Personal blog — 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 19 September 2026 and assigned it the closest of 31 fixed categories, at 78% 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

864877870.56 August 2026 — 866 subscribers7 August 2026 — 866 subscribers14 August 2026 — 867 subscribers4 September 2026 — 868 subscribers12 September 2026 — 867 subscribers26 September 2026 — 864 subscribers7 October 2026 — 877 subscribers6 August 20267 October 2026
7 measurements spanning 61 days, net +11. 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 862–879 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Oct 2026, 03:40877+13
26 Sept 2026, 11:38864-3
12 Sept 2026, 15:39867-1
4 Sept 2026, 08:02868+1
14 Aug 2026, 00:26867+1
7 Aug 2026, 19:34866no change
6 Aug 2026, 20:02866first reading

Engagement

4 posts held, back to 5 April 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 1 page 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 4 posts for this entry, the most recent from 24 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

151 reactions across 4 posts, in 6 distinct kinds. The most used accounts for 43.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤6543.0%
👍3422.5%
😁1711.3%
🔥159.93%
😢127.95%
🤔85.30%

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

Measured over the 4 most recent posts we hold, published 5 April 2026 to 24 July 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

24 Jul 2026, 14:55 UTC307 views54 reactionsread 6 August 2026
Photo

Ещё один год пролетел! ❤️

❤35🔥11👍8

25 Jun 2026, 05:12 UTC725 views18 reactionsread 6 August 2026
Photo

Во время обстрелов Ираном и кризисных настроений обдумывали оптимизацию расходов и отказ от одного из наших офисов в Дубае. Выбор пал на самый большой и дорогой, на Пальме Джумейра. Стали изучать варианты и оказалось, что мы те ещё мамкины бизнесмены: контракт не предполагает досрочного выезда. Просто нет такой опции. И как назло, новый договор подписали за неделю до начала обстрелов. Чтобы выехать, нужно погасить в…

😢12🤔6

24 Jun 2026, 15:04 UTC559 views27 reactionsread 6 August 2026

Анекдот от Аркадия Новикова: Свинья и курица решили открыть ресторан. — Назовём «Яичница с беконом»! — говорит курица. — Я буду яйца давать, а с тебя бекон. — Погоди, — отвечает свинья. — Ты просто будешь нестись каждое утро. А я закончу, когда меня всю порежут на бекон. — Ну да, — кивает курица. — В этом и есть смысл бизнес-партнёрства.

😁17👍6❤2🤔2

5 Apr 2026, 06:31 UTC≈1,040 views52 reactionsread 6 August 2026
Photo

Война войной, а жизнь продолжается. Для тех, кому интересно, как сейчас в Дубае — небольшой репортаж с моей велопрогулки по центру города. Впервые взял с собой Fujifilm X100VI, получилась очень живая и атмосферная суббота 📸

❤28👍20🔥4

Showing the 4 most recent of 4 posts we hold for @dimabalakirev. 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.

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

“Дмитрий Балакирев” (@dimabalakirev), 877 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/dimabalakirev.

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.