Telegram RegisterThe public register of Telegram
Telegram profile photo for eComCrew

Channel

eComCrew

@ecomcrew_ru

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

16subscribers

+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-1001867133566
TypeChannel
Username@ecomcrew_ru
DescriptionКоманда С-level специалистов. Опыт 15+ лет на каждого ;) Решаем задачи маркетинга, аналитики, стратегии и продуктоводства для SaaS и IT-компаний. 🛠 24/7: @eComCrewBot
Created18 February 2023measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live14 August 2026
Measurements held2
On Telegramt.me/ecomcrew_ru

Growth

167 August 2026 — 16 subscribers11 August 2026 — 16 subscribers7 August 202611 August 2026
2 measurements spanning 4 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 15–17 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 21:4516no change
7 Aug 2026, 15:3316first reading

Engagement

9 posts held, back to 18 February 2023the 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.

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

What this channel posts

Photos
5
Links
6

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

Reaction mix

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
533.3%
😁320.0%
👍213.3%
custom 542031577199149730716.67%
custom 581865153890143774816.67%
👏16.67%
🤔16.67%
🤯16.67%

Custom emoji. 2 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

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

Measured over the 9 most recent posts we hold, published 18 February 2023 to 18 June 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

18 Jun 2026, 13:32 UTC126 views6 reactionsread 11 August 2026
Photo

Спешим сообщить радостную весть. 24 и 25 июня мы будем представлять наше BizDev агентство на крупнейшей выставке интернет-торговли - ECOM Expo 2026. Регистрируйтесь, приходите и ищите наш стенд на 2 этаже под номером B1.4, будем ждать вас там оба дня с распростёртыми объятиями. Два дня будем демонстрировать свою супер силу услугу - "Биздев на час." #ecomcrew_мероприятие

3👍2👏1

27 Sept 2025, 08:31 UTC270 views1 reactionsread 11 August 2026
Photo

Как тестовый вход в партнёрскую сеть принёс eComCrew продажу с первого же лида. История в трёх актах: 1. Вызов — коллеги решили протестировать нашу партнёрскую сеть. Цель понять процесс и потенциал без лишних трудозатрат. ✅Передали всего один непрофильный запрос. ✅В одном запросе от других партнёров — приняли участие. 2. Решение — для «боевого испытания» выбрали сложный и специфический запрос — разработку платёжны

🤔1

30 Jun 2024, 21:54 UTC≈2,310 views4 reactionsread 11 August 2026
Photo

Photo, posted without a caption

😁3🤯1

11 Jun 2024, 10:45 UTC≈2,010 views4 reactionsread 11 August 2026
Photo

⏺💬 Итоги самой большой отраслевой есом выставки России ECOM.EXPO 2024 Дисклеймер: Внимание, умеющие читать! Прежде чем погрузиться в омут очевидностей и разоблачений, представленных в этом уникальном экспозе о самой большой выставке достижений в мире электронной торговли России, настоятельно рекомендую вам вооружиться зонтами. Нет-нет, не от дождя, а от потока бесспорных истин, которым вас собирается осчастливить ав

2custom 54203157719914973071custom 58186515389014377481

14 Feb 2024, 12:34 UTCviews —

eComCrew pinned «Наше агентство родилось из отдела маркетинга компании inSales, который прошел путь от 70 клиентов на старте до продажи СБЕРу за несколько ярдов. Каждый ключевой сотрудник команды имеет от 8 лет опыта в продвижении/разработке/управлении облачными IT-сервисами…»

14 Feb 2024, 12:34 UTC291 viewsread 11 August 2026

Наше агентство родилось из отдела маркетинга компании inSales, который прошел путь от 70 клиентов на старте до продажи СБЕРу за несколько ярдов. Каждый ключевой сотрудник команды имеет от 8 лет опыта в продвижении/разработке/управлении облачными IT-сервисами, в основном для СМБ. Мы умеем эффективно продвигать как в РФ, так и за его пределами. Инструментарий у нас обширный, от классических каналов, до партизанского м

13 Feb 2024, 11:36 UTC210 viewsread 11 August 2026
Forwarded from @bezsmuziFile

Приложил к почту мини-аудит нашего сервиса clickfraud.ru от ребят из eComCrew (специализируются на маркетинге для SaaS-сервисов). Не скажу, что увидел какие-то откровения, мы все таки глубоко в бизнесе. Но мнение со стороны подтверждают, что мы двигаемся правильно и есть куда расти.. Если у вас уже есть готовый продукт и клиенты, можете оставить заявку на бесплатный аудит ... Лично мне результат понравился, так чт

5 Dec 2023, 11:15 UTC170 viewsread 11 August 2026
Photo

#полезное Собрали для вас список полезных конференций по маркетингу на 23-24 год. Пользуйтесь и отправляйте своим маркетологам. https://ecomcrew.ru/activity

Showing the 9 most recent of 9 posts we hold for @ecomcrew_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

Citation-graph rank — 652,033 of 1,481,217entries 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.

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.

Mentions

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

“eComCrew” (@ecomcrew_ru), 16 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/ecomcrew_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.