✔️ Дата аналітик/серчер у технічний відділ (віддалено) 💲 ЗАРПЛАТА: 23 000 - 45 000 грн. / за місяць ♾ ОПИС ВАКАНСІЇ: Шукаємо уважного спеціаліста для роботи з даними та внутрішніми базами.Без дзвінків, продажів і спілкування з клієнтами — лише чіткі завдання, аналіз інформації та фіксація результатів.Досвід не обов’язковий — навчаємо з нуля та надаємо технічну підтримкуРобота з Ноутбуку/ПКЩо потрібно робити: - Шука…

Channel
Data Analyst Робота віддалено | Вакансії Аналітик Даних
@data_analyst_robota
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
20subscribers
+0 since we began measuring on 12 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002170710257 |
|---|---|
| Type | Channel |
| Username | @data_analyst_robota |
| Description | Реклама - @emilycollins324 |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 September 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/data_analyst_robota |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Sept 2026, 07:23 | 20 | no change |
| 12 Sept 2026, 18:47 | 20 | first reading |
Engagement
20 posts held, back to 10 September 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.
- ERR · 30 days
- 7.25%
- avg views ÷ 20 subscribers
- Avg views / post
- 1.4
- 20 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 20
- 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.
| Window | Rolling 30 days · latest post in window 13 September 2026 |
|---|---|
| Posts held | 20 (10 September 2026 – 13 September 2026) |
| Views total | 29 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Sept 2026, 07:23 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.
What this channel posts
- Links
- ≈3,050
Lifetime counters from Telegram’s own channel header, read 13 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Recent posts
✔️ Senior Software Engineer — Data Catalog / Ingestion 💲 ЗАРПЛАТА: до $5000 ♾ ОПИС ВАКАНСІЇ: About Our Client Our client is a leading enterprise data platform company building an open, high-performance data lakehouse for AI and analytical workloads. The platform combines an intelligent SQL query engine, an AI-ready semantic layer, and an open catalog built on Apache Iceberg — enabling Fortune 500 companies across f…
✔️ Middle SDET — Data Platform / Query Engine 💲 ЗАРПЛАТА: до $4000 ♾ ОПИС ВАКАНСІЇ: Level: Middle Engagement: Long-term contract Location: Europe (EU / EEA / UK), remote Working hours: EU business hours, shifted 2–3 hours later to ensure daily overlap with US West Coast (PST/PDT) mornings About the Client Our client is a leading enterprise data platform company building an open, high-performance data lakehouse for …
✔️ Senior SDET — Data Platform / Query Engine 💲 ЗАРПЛАТА: до $4500 ♾ ОПИС ВАКАНСІЇ: Level: Senior Engagement: Long-term contract Location: Europe (EU / EEA / UK), remote Working hours: EU business hours, shifted 2–3 hours later to ensure daily overlap with US West Coast (PST/PDT) mornings About the Client Our client is a leading enterprise data platform company building an open, high-performance data lakehouse for …
✔️ Senior Software Engineer (Java/C++) — Query Engine / Data Platform 💲 ЗАРПЛАТА: до $5000 ♾ ОПИС ВАКАНСІЇ: Level: Senior Engagement: Long-term contract Location: Europe (EU / EEA / UK), remote Working hours: EU business hours, shifted 2–3 hours later to ensure daily overlap with US West Coast (PST/PDT) mornings About the Client Our client is a leading enterprise data platform company building an open, high-perform…
✔️ Middle Software Engineer (Java/C++) — Query Engine / Data Platform 💲 ЗАРПЛАТА: до $3500 ♾ ОПИС ВАКАНСІЇ: Level: Middle Engagement: Long-term contract Location: Europe (EU / EEA / UK), remote Working hours: EU business hours, shifted 2–3 hours later to ensure daily overlap with US West Coast (PST/PDT) mornings About the Client Our client is a leading enterprise data platform company building an open, high-perform…
✔️ Компанію не вказано 💲 ЗАРПЛАТА: За результатами співбесіди 🪙 ВСІ ВАКАНСІЇ | DATA ANALYST 🪙
✔️ Data analyst 💲 ЗАРПЛАТА: За результатами співбесіди ♾ ОПИС ВАКАНСІЇ: Технологічна компанія, що працює в сфері робототехніки та є об’єктом критичної інфраструктури стрімко розвивається і шукає Data-analyst. Вимоги: 1.Досвід роботи аналітиком даних у сфері IT, фінансів, виробництва, телекомунікацій або e‑commerce. 2. Досвід роботи з бізнес‑системами (ERP, CRM, BI‑платформи). 3. 2–3 роки практичного досвіду роботи …
✔️ Аналітик 💲 ЗАРПЛАТА: до $1200 ♾ ОПИС ВАКАНСІЇ: Вимоги: - Досвід роботи в аналітиці від 1 року бажано у фінансовій сфері). - Вміння працювати з великими обсягами даних та аналітичними інструментами. - Володіння SQL та Excel на вискокому рівні - Орієнтація на результат, увага до деталей і відповідальність. - Готовність вчитися та розвиватися разом з компанією. - Відсутність жорстких вимог до освіти — для нас важли…
✔️ Компанію не вказано 💲 ЗАРПЛАТА: За результатами співбесіди 🪙 ВСІ ВАКАНСІЇ | DATA ANALYST 🪙
✔️ Компанію не вказано 💲 ЗАРПЛАТА: За результатами співбесіди 🪙 ВСІ ВАКАНСІЇ | DATA ANALYST 🪙
✔️ Компанію не вказано 💲 ЗАРПЛАТА: За результатами співбесіди 🪙 ВСІ ВАКАНСІЇ | DATA ANALYST 🪙
Showing the 12 most recent of 20 posts we hold for @data_analyst_robota. 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.
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.
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 13 September 2026 — this entry's latest reading, not the date you are reading this.
“Data Analyst Робота віддалено | Вакансії Аналітик Даних” (@data_analyst_robota), 20 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/data_analyst_robota.
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.