Telegram RegisterThe public register of Telegram

Channel

На вчора

@navchera

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

40subscribers

+0 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-1001152388849
TypeChannel
Username@navchera
DescriptionПро бізнес-процеси, автоматизацію, BI, CRM, ШІ, маркетинг, продажі, проекти та інш. Збираємо краще та пишемо своє. — Якщо щось - пишіть сюди https://t.me/Serhii_Sydorenko
CreatedBetween 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live10 August 2026
Measurements held2
On Telegramt.me/navchera

Growth

407 August 2026 — 40 subscribers10 August 2026 — 40 subscribers7 August 202610 August 2026
2 measurements spanning 3 days. 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 39–41 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 19:3140no change
7 Aug 2026, 22:3440first reading

Engagement

19 posts held, back to 5 September 2025the 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
40.0%
avg views ÷ 40 subscribers
Avg views / post
16.0
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 19 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 3 August 2026
Posts held19 (5 September 20253 August 2026)
Views total16
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Aug 2026, 19:31 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

Photos
1
Videos
2
Links
140

Lifetime counters from Telegram’s own channel header, read 10 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.

Video runtime
9s
Average length
9s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

9 reactions across 6 posts, in 2 distinct kinds. The most used accounts for 88.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍888.9%
111.1%

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

Measured over the 19 most recent posts we hold, published 5 September 2025 to 3 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

16 Jul 2026, 09:48 UTC34 views1 reactionsread 10 August 2026

Чому AI пише тобі сміття: 5 помилок, які роблять всі (відео 21 хв) - Коротко про ключові моменти роботи з LLM. Одне з небанальних відео про прості речі, систематизовано. - #автоматізація #AI

👍1

4 Jun 2026, 09:02 UTC47 viewsread 10 August 2026

Що таке фреймворк: пояснюємо простими словами (стаття, 17 хв)

28 May 2026, 06:27 UTC62 views1 reactionsread 10 August 2026

https://www.instagram.com/reel/DXhA7dWtfPd/?igsh=c2d0MWUzNmpjbTM5

👍1

26 Mar 2026, 07:30 UTC93 viewsread 10 August 2026

▪️ChatGPT vs Claude vs Gemini: що вибрати для бізнесу 2025 (стаття, 18 хв) ▪️ Практичний посібник з вибору між ChatGPT, Claude, Gemini, Grok та Perplexity (стаття, 6 хв) ▪️Prompt Engineering для початківців: 10 правил ідеального промпту (стаття, 6 хв) - #AI

3 Mar 2026, 16:25 UTC100 views1 reactionsread 10 August 2026

Дороничев: ИИ — пузырь, который скоро ЛОПНЕТ. Какие перемены ждут мир? Цікава розмова з чуваком про його бачення розвитку технологій. Він безпосередньо займався розвитком YouTube на початковій стадії. • Цікава теза про здатність нести відповідальність.

1

12 Feb 2026, 14:14 UTC90 viewsread 10 August 2026

Що таке агенти штучного інтелекту? AI Agent. ШІ Агенти для бізнесу. Як створити ШІ Агента - #AI

24 Nov 2025, 08:05 UTC117 viewsread 10 August 2026

Огляд NotebookLM від Google (відео 18 хв) - AI інструмент для навчання. - Полегшує розуміння складних тем. - Систематизує джерела.

13 Nov 2025, 10:28 UTC123 viewsread 10 August 2026

- Як Apple Notes поліпшують життя! Лайфхаки і поради по використанню - Гид по Apple Notes: обзор функций и советы | Заметки Apple

31 Oct 2025, 18:59 UTC127 views4 reactionsread 10 August 2026

Правильна постановка завдання (це не про SMART)

👍4

27 Oct 2025, 07:33 UTC134 viewsread 10 August 2026

▪️Креатив для facebook: розміри, формати та поради для створення. ▪️Facebook для бізнесу: 25 корисні поради для застосування ▪️Розкрутка та просування сторінки у Facebook: інструкція з прикладами -- #маркетинг #smm

24 Oct 2025, 06:03 UTC141 viewsread 10 August 2026

▪️Алгоритми facebook 2025: практичні поради для більшого охоплення ▪️ Як у 2025-му працюють алгоритми Instagram, Facebook, TikTok, LinkedIn і X — дослідження Emplifi ▪️ Алгоритми Facebook та Instagram: як їх зрозуміти та використовувати на свою користь? ▪️ Найкращий час для постингу у Facebook у 2025 році ▪️ Популярні хештеги для Facebook 2025: де їх шукати? -- #маркетинг #smm

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

Forward network

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.

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

“На вчора” (@navchera), 40 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/navchera.

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.