Telegram RegisterThe public register of Telegram
Telegram profile photo for Консалтинг для OF-руководителей

Channel

Консалтинг для OF-руководителей

@start_owner

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

17subscribers

-6 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-1003750177011
TypeChannel
Username@start_owner
Created7 May 2026measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live6 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 6 September 2026
On Telegramt.me/start_owner

Growth

1723207 August 2026 — 23 subscribers11 August 2026 — 23 subscribers14 August 2026 — 21 subscribers22 August 2026 — 20 subscribers29 August 2026 — 19 subscribers6 September 2026 — 17 subscribers7 August 20266 September 2026
6 measurements spanning 30 days, net -6. 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 16–24 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Sept 2026, 14:5517-2
29 Aug 2026, 21:0319-1
22 Aug 2026, 03:4620-1
14 Aug 2026, 20:5921-2
11 Aug 2026, 12:1923no change
7 Aug 2026, 19:3823first reading

Engagement

2 posts held, back to 7 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 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 2 posts for this entry, the most recent from 23 June 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

23 Jun 2026, 13:56 UTC61 viewsread 11 August 2026

SYNERA CONSULT - первое консалтинг-агентство для оунеров и руководителей нашего комьюнити. https://t.me/consult_ofm/ Наши проекты: • канал про CRM-системы для OF и аналитику • канал про увеличение продаж и управление чаттерами • канал про управление агентством • чат для оунеров • первый чат для тимлидов (условия в лс @Roma_eden)

Showing the 2 most recent of 2 posts we hold for @start_owner. 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

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

“Консалтинг для OF-руководителей” (@start_owner), 17 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/start_owner.

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.