Telegram RegisterThe public register of Telegram
Telegram profile photo for Dora & FineBI Россия | FanRuan

Channel

Dora & FineBI Россия | FanRuan

@FanRuanofficialchannel

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

379subscribers

+5 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-1002191768917
TypeChannel
Username@FanRuanofficialchannel
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 8 August 2026
On Telegramt.me/FanRuanofficialchannel

Growth

374379376.57 Aug 2026, 21:06 — 374 subscribers8 Aug 2026, 06:18 — 374 subscribers8 Aug 2026, 20:11 — 379 subscribers7 Aug 2026, 21:068 Aug 2026, 20:11
3 measurements taken within a single day, net +5. 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 373–380 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 20:11379+5
8 Aug 2026, 06:18374no change
7 Aug 2026, 21:06374first reading

Engagement

20 posts held, back to 13 May 2026the 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 · 30 days
56.4%
avg views ÷ 379 subscribers
Avg views / post
214
3 posts measured
Reaction rate
3.43%
reactions ÷ views · ER floor
Posts in window
7
of 20 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
WindowRolling 30 days · latest post in window 7 August 2026
Posts held20 (13 May 20267 August 2026)
Views total641
Reactions total22
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 06:18 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

39 reactions across 8 posts, in 5 distinct kinds. The most used accounts for 33.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1333.3%
🔥1128.2%
820.5%
🥰512.8%
👏25.13%

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

Measured over the 20 most recent posts we hold, published 13 May 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, 09:00 UTC75 views6 reactionsread 8 August 2026

🚀 How did BOE cut inventory costs by 5% and boost operational efficiency by 50%? By building a business-intelligent decision chain powered by unified data, standardized KPIs, and multi-level collaboration. In this customer story, BOE shares how they: ✅ integrated fragmented data across systems ✅ unified 257 metrics ✅ built 200+ data models ✅ launched KPI dashboards for faster, data-driven decisions ✅ enabled cross-

🔥3👍21

4 Aug 2026, 08:00 UTC128 views7 reactionsread 8 August 2026
Photo

📢Знакомьтесь: Dora — ваш AI-коллега 13 августа (в следующий четверг) мы покажем 4 AI-агентов Dora, которые самостоятельно анализируют данные, создают отчёты, отправляют дайджесты и предупреждают о рисках. Дата-аналитик Исследователь отчётов Ассистент по дайджестам Офицер по рискам Бонус: возможность выиграть до 8 000 ₽ в виде токенов для больших языковых моделей, а также получить ранний доступ к Dora. 13 августа

👍7

23 Jul 2026, 07:34 UTC438 views9 reactionsread 8 August 2026
Photo

🚀 Dora: от аналитики к реальным бизнес-действиям BI помогает визуализировать данные. Dora помогает превратить их в конкретные решения и действия. Хотите узнать, как превратить проверенные данные, BI-активы и экспертизу вашей компании в AI-агентов, которые действительно помогают выполнять задачи и повышать эффективность бизнеса? 🎙 Приглашаем вас на наш онлайн-вебинар, где мы покажем, как современные AI-технологии п

🥰5👍2👏2

6 Jul 2026, 08:34 UTC227 views1 reactionsread 8 August 2026
Photo

🎉 Ребята, отличная новость! Сертификация FanRuan стала реально удобнее. Можно начать экзамен в любой момент, проверка и выдача сертификата — автоматически. От регистрации до входа в экзамен — максимум 3 минуты! Если вы уже юзаете наши продукты и хотите подтвердить свой скилл — сейчас самый момент! 👊 FCA Associate: • всего 30 минут • бесплатно 🆓 • результат — сразу после сдачи, без ожидания Три направления: Reporting

🔥1

30 Jun 2026, 13:05 UTC262 viewsread 8 August 2026
Photo

🚀 Бесплатный вебинар: Dora Data Agent — цифровые AI-сотрудники для аналитики BI-системы уже не только дашборды. Новая аналитика — это AI-агенты, которые понимают бизнес-запросы, ищут аномалии, готовят отчёты и отвечают на вопросы на естественном языке. На вебинаре покажем живое демо Dora + FineBI/FineReport: • Запросы к данным на естественном языке • AI-аналитик, исследователь отчётов, секретарь брифингов, офицер п

15 Jun 2026, 07:52 UTC280 views3 reactionsread 8 August 2026

⚡️Запись вебинара «Миграция на FineBI 7.0: опыт банка Уралсиб» 19 мая команда BI Consult провела вебинар по FineBI 7.0. Вместе с приглашённым экспертом Семёном Юниковым, Head of BI банка «Уралсиб», мы детально разобрали особенности и реальный опыт перехода крупнейшего банка на FineBI 7.0 🪭 Что обсудили на вебинаре: – Как менялась техническая инфраструктура до и после миграции. – Нюансы переноса ETL, дашбордов и рас

👍2🔥1

1 Jun 2026, 06:12 UTC819 views3 reactionsread 8 August 2026

🚀 2026 FanRuan Global Data Analytics Competition — регистрация открыта! 💰 Призовой фонд более $70,000. Два направления — Enterprise Analytics и Data Storytelling. Финал проходит вживую на Smart Data Conference. 😃Открыто для всех пользователей FanRuan, без ограничений по профилю. ⌛️Регистрация открыта до 30 июня. Подробности на официальном сайте — сроки, награды, направления.➡️ https://s.fanruan.com/s1ji4 ✍️ Реги

2🔥1

29 May 2026, 11:36 UTC241 views9 reactionsread 8 August 2026
Photo

🏆 Итоги FineGallery Insight Challenge 2026 Мы готовы объявить победителей первого конкурса визуальной аналитики FineGallery 🎉 Спасибо всем участникам — мы увидели сильные аналитические кейсы, интересные подходы к визуализации и действительно высокий уровень работ. 🧠 Лучшая бизнес-аналитика 🥇 Победитель — Дашборд: Call Center Работа получила самые высокие оценки за: — глубину аналитики — проработку данных — практ

🔥54

Showing the 12 most recent of 20 posts we hold for @FanRuanofficialchannel. 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 — 682,709 of 1,481,346entries 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

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

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

“Dora & FineBI Россия | FanRuan” (@FanRuanofficialchannel), 379 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/FanRuanofficialchannel.

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.