Telegram RegisterThe public register of Telegram

Channel

Игорь Апресов | Radio Ingvar

@radio_ingvar

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

2,325subscribers

+10 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001290955211
TypeChannel
Username@radio_ingvar
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/radio_ingvar

Growth

2,3152,3252,3206 August 2026 — 2,315 subscribers6 August 2026 — 2,315 subscribers7 August 2026 — 2,316 subscribers10 August 2026 — 2,320 subscribers13 August 2026 — 2,325 subscribers6 August 202613 August 2026
5 measurements spanning 7 days, net +10. 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 2,314–2,327 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 06:062,325+5
10 Aug 2026, 09:012,320+4
7 Aug 2026, 04:002,316+1
6 Aug 2026, 05:502,315no change
6 Aug 2026, 05:482,315first reading

Engagement

17 posts held, back to 25 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
38.7%
avg views ÷ 2,325 subscribers
Avg views / post
901
17 posts measured
Reaction rate
2.09%
reactions ÷ views · ER floor
Posts in window
17
of 17 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. It is computed over the 15 of 17 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held17 (25 July 20267 August 2026)
Views total15,311
Reactions total273
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 16:41 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

217 reactions across 12 posts, in 4 distinct kinds. The most used accounts for 40.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥8840.6%
👍8137.3%
3516.1%
🤔135.99%

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

Measured over the 17 most recent posts we hold, published 25 July 2026 to 7 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.

Recent posts

7 Aug 2026, 16:20 UTC112 views8 reactionsread 7 August 2026
File

File, posted without a caption

🔥5👍21

7 Aug 2026, 16:20 UTC112 views12 reactionsread 7 August 2026

Написал статью для Инфостарт про v8std.ru - но ее отказались публиковать. Это реклама других ресурсов. Бесплатный сайт. Бесплатный MCP. Все работает на своем железе если надо развернуть у себя. Все исходники открыты. Инфостарт, что с тобой не так?

🤔12

6 Aug 2026, 11:02 UTC453 views16 reactionsread 7 August 2026
Forwarded from @top_1cPhoto

‼️‼️‼️ Я пропустил главный хайп! Роберт Мартин — за ИИ и... не читает код! Как так? А чистый код? А чистая архитектура??? Роберт Сесил Мартин (известный как Дядя Боб или Uncle Bob) — знаменитый американский программист, консультант и автор книг по разработке программного обеспечения. Он популяризировал принципы «чистого кода» (Clean Code), гибкой разработки (Agile) и принципы проектирования SOLID. Всё просто: он и

👍7🔥54

4 Aug 2026, 18:25 UTC923 views14 reactionsread 7 August 2026
Photo

Скоро EDT перестанет работать на Mac! Mac прекращает поддержку Intel-based приложений на Apple silicon https://support.apple.com/en-au/102527 А это может касаться и не только edt а еще и всех других компонент, и платформы в том числе. И даже веб-клиент может не спасти, потому что внутри сафари и хрома плагин тоже должен быть адаптирован к эпл силикон, ну и все внешние компоненты...

👍10🔥4

3 Aug 2026, 08:54 UTC895 views19 reactionsread 7 August 2026
Forwarded from @IngvarConsultingPhoto

Завели отдельный чат в телеграм по вопросам работы unica ✈️@unica_ai Общая информация: 🏷https://ingvar.pro/products/unica 🔗https://github.com/IngvarConsulting/unica

👍12🔥43

31 Jul 2026, 13:19 UTC987 views21 reactionsread 7 August 2026
Forwarded from @kungfu_confPhoto

🐼 Публикуем первое видео с Кунг-фу митапа в Санкт-Петербурге! Алексей Корякин на Кунг-фу митапе в Санкт-Петербурге разбирает, как превратить разрозненные проектные знания в живую LLM Wiki: собирать источники, связывать сущности и понятия, задавать вопросы к базе знаний, проверять ее качество и использовать skills как воспроизводимый способ работы ИИ-агента. Доклад для тех, кто работает с большими проектами, где ТЗ,

🔥17👍4

30 Jul 2026, 10:40 UTC≈1,200 views12 reactionsread 7 August 2026
Photo

Photo, posted without a caption

6🔥5🤔1

29 Jul 2026, 06:39 UTC≈1,110 views14 reactionsread 7 August 2026
Forwarded from @OnEventsPhoto

👉 ИТ Кунг-фу Ужин 📅 Когда: 30 июля 2026 📌 Где: Нячанг ⚡️ Что тебя ждёт: ИТ Кунг-фу Ужин состоится в Нячанге 30 июля в 20:00, Red Buffalo Hub - Hon Chong. Без докладов, вход свободный, каждый платит сам за себя 🐼 Приходи! Обсудим все хайповые тренды в 1С и не только. 🔗 Информация #Нячанг

👍74🔥3

28 Jul 2026, 11:57 UTC≈1,090 views30 reactionsread 7 August 2026

https://t.me/nixel2007_thoughts/772 Поздравим Никиту и команду BSL LS! Ура!

🔥206👍4

28 Jul 2026, 06:59 UTC≈1,030 views19 reactionsread 7 August 2026

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

🔥96👍4

28 Jul 2026, 06:47 UTC965 views27 reactionsread 7 August 2026

Я использую приоритет Sol, Fable, Opus, Terra. Fable хорош для глубокого аудита, например архитектуры — он здорово ищет отклонения. Sol хорош для ревью по спеке — любое нарушение спеки сразу ахтунг, 100 раз перепроверит. Opus хорош для просто разработки, он часто отступает от правил, и для реализации фич отлично, потому что без шанса отступлений получается тест на тест тестом покрывает и много лишнего. Terra — для п

👍261

27 Jul 2026, 15:05 UTC814 views25 reactionsread 7 August 2026
Forwarded from @kungfu_confPhoto

ИТ Кунг-фу Ужин состоится в Нячанге 30 июля в 20:00, Red Buffalo Hub - Hon Chong https://maps.app.goo.gl/oErvyPkSiatrfbpZ8?g_st=ic Без докладов, вход свободный, каждый платит сам за себя 🐼 Приходи! КУНГ-ФУ: Канал / Чат 👍

🔥16👍54

Showing the 12 most recent of 17 posts we hold for @radio_ingvar. 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.

Citation-graph rank

Citation-graph rank — 58,915 of 1,169,250entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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 17 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.

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

“Игорь Апресов | Radio Ingvar” (@radio_ingvar), 2,325 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/radio_ingvar.

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.