Channel
@finebi_ru
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
948subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001695149099 |
|---|---|
| Type | Channel |
| Username | @finebi_ru |
| Description | Всем привет! Это канал о китайской системе бизнес-аналитики FineBI Чат: @FineBIChat По всем вопросам: @it_larin Made in @GlowByte |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/finebi_ru |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 10:03 | 948 | no change |
| 7 Aug 2026, 09:58 | 948 | first reading |
18 posts held, back to 22 June 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 pageof Telegram’s post history, 20 posts per page.
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 3 of 7 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 5 August 2026 |
|---|---|
| Posts held | 18 (22 June 2026 – 5 August 2026) |
| Views total | 1,970 |
| Reactions total | 5 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 10:03 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.
Lifetime counters from Telegram’s own channel header, read 7 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.
16 reactions across 8 posts, in 3 distinct kinds. The most used accounts for 56.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 9 | 56.3% | |
| 🔥 | 6 | 37.5% | |
| ❤ | 1 | 6.25% |
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 9 of the 18 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 16reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 22 June 2026 to 5 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.
🌚 Вопрос: Добрый день. Подскажите, пожалуйста. Сейчас переходим с PowerBI на FineBI и голова едет как реализовать те же фишки, что были в PBI. В общем был дашборд (первые 2 скрина), в котором при нажатии кнопок день/неделя/месяц/год менялась гранулярность и раскладка графика, в PowerBI я это делал через закладки, то есть делал 4 графика с разной осью X и своей группировкой и привязывал переходы между закладками к кно…
❤1
Редакция рекомендует послушать подкаст Ленни Рачитски с Элизабет Стоун, Chief Product and Technology Officer Netflix. Обсуждают, как ИИ меняет техническую команду и организацию изнутри, не с точки зрения хайпа, а с точки зрения человека, который реально управляет продуктом и инженерией в компании такого масштаба. Что понравилось. Про фазу шторма. Каждый раз, когда приходит новая технология, тем более настолько тран…
Парные оси: как FineBI решает боль Таблошников Коллеги, привет! 🙌 Сегодня разберём, что такое парные оси и почему этот приём так важен для визуализации данных. Если вы когда-то строили дашборды в Tableau, то наверняка сталкивались с ограничением Dual Axis - невозможностью удобно накладывать разные типы графиков друг на друга. Идея парных осей проста: у графика есть 4 стороны и 2 оси, а что если использовать ось с к…
GlowByte и «Дикси»🛒: миграция на Sigla Vision ускорила аналитику в 2 раза 📈 В РБК рассказали, как федеральная сеть «Дикси» при поддержке GlowByte провела миграцию бизнес-отчетности с Power BI на российскую платформу Sigla Vision. Результат – сокращение цикла разработки дашбордов с 210 до 112 дней (ускорение на 47%). 🧮 Что было: 🟠558 активных пользователей в месяц; 🟠155 дашбордов; 🟠средний TTM (time‑to‑market) – 210…
👍1
Что, если бы на вопрос «почему просел показатель» отвечал не аналитик, а сам BI? FanRuan представляет Dora: платформу, где поиск причины, сверку данных, сборку отчёта и рассылку берут на себя ИИ-агенты. Работают они поверх ваших BI-активов — готовых моделей данных, метрик и прав доступа, а не по сырым таблицам. На вебинаре четыре агента пройдут полный цикл вживую: 🔹 Дата-аналитик: отвечает на запросы к данным и ище…
👍3
🌚 Вопрос: Для чего нужна association view в FineBI и как она работает? 🌝 Ответ: Association view в FineBI используется для объединения данных из двух справочников с двумя таблицами фактов, что особенно актуально при наличии двух иерархических фильтров, общих для визуализаций по обеим таблицам. Такая связка позволяет создать общий справочник для обеих таблиц фактов. В версиях модели данных 6.0/6.1 напрямую связать дв…
#дайджест Всем привет! Сегодня в выпуске: 📰 Интервью с АО «Полиэкс» и GlowByte о внедрении PIX BI Анонсированный кейс совместного проекта по построению аналитической платформы теперь в формате живого разговора - перевели с делового языка на человеческий. Читайте полное интервью с участниками проекта. 🔗 Читать на Хабр 📝 Где искать обучающие материалы по FineBI: разбираем источники «А где почитать или посмотре…
Posted without readable text
🌚 Вопрос: Как задать условное форматирование для столбца с датой в detail table, чтобы ячейка была красной, если дата в прошлом? 🌝 Ответ: Напишите условие if([поле]<today(), "старое", "новое") и поместите его в цвет меры. Чтобы выделить всю строку при условии, поставьте флажок «на всю строку», иначе - только ячейку с датой. 🔗 Обсуждение #FineBI #вопрос_ответ
Photo, posted without a caption
#дайджест 📰 Системные дашборды для Sigla Vision В блоге Газпромбанка вышла новая статья из серии про адаптивное администрирование Sigla Vision — на этот раз про системные дашборды для мониторинга самой BI-системы. 🔗 Читать на Хабр 💡 Неочевидные возможности: 3 кнопки в FineBI, которые ты мог не заметить (часть 1) Казалось бы, работаешь с FineBI не первый месяц, но вдруг находишь в интерфейсе новые фишки и удивляешьс…
👍2🔥1
Всем привет! Подготовили на хабре небольшой обзор по обучающим материалам FineBI https://habr.com/ru/companies/glowbyte/articles/1054608/
👍2
Showing the 12 most recent of 18 posts we hold for @finebi_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.
Citation-graph rank — 490,515 of 1,345,403entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 1 registered channel — 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.
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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“FineBI в России” (@finebi_ru), 948 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/finebi_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.