Telegram RegisterThe public register of Telegram
Telegram profile photo for Я и сам своего рода маркетолог

Channel

Я и сам своего рода маркетолог

@marketing_deshevo

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

363subscribers

-4 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-1002148064234
TypeChannel
Username@marketing_deshevo
CreatedBetween 1 May 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live6 September 2026
Measurements held4
Confirmed unchanged2 times, most recently 6 September 2026
On Telegramt.me/marketing_deshevo

Growth

3633673657 August 2026 — 367 subscribers8 August 2026 — 367 subscribers15 August 2026 — 366 subscribers29 August 2026 — 363 subscribers7 August 202629 August 2026
4 measurements spanning 21 days, net -4. 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 362–368 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 02:27363-3
15 Aug 2026, 01:18366-1
8 Aug 2026, 06:30367no change
7 Aug 2026, 14:28367first reading

Engagement

6 posts held, back to 16 February 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 6 posts for this entry, the most recent from 3 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

143 reactions across 6 posts, in 10 distinct kinds. The most used accounts for 45.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
6545.5%
😁2215.4%
💯1611.2%
custom 5406669033099502372149.79%
custom 523595014757732627674.90%
custom 535031533414437238164.20%
👍53.50%
custom 538888095789168595642.80%
🐳32.10%
🔥10.699%

Custom emoji. 4 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 are Telegram’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 6 of the 6 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 143 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 6 most recent posts we hold, published 16 February 2026 to 3 July 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

3 Jul 2026, 13:52 UTC324 views28 reactionsread 8 August 2026
Photo

Нейрослоп про Empire State Building — пустота, копирующая пустоту 🥲 Индивидуальность, креативность, человечность – теперь это непозволительная роскошь. Все хотят особенного, ни на кого не похожего маркетинга. Ставят в пример DuoLingo и Aviasales. А чо по факту? А по факту маркетинг сегодня — это копирование уже завирусившегося шаблона. Высказать свежую идею? No thanks. Мы хотим встроить логотип в мем! Минвайл инс

💯16custom 53503153341443723816🐳32custom 54066690330995023721

16 Apr 2026, 05:26 UTC498 views22 reactionsread 8 August 2026

Мне нравится, что после поста про выгорание от меня отписался сео одной крипты

😁22

16 Apr 2026, 05:12 UTC469 views28 reactionsread 8 August 2026
Photo

Пожалуй, впервые за работу в Instories почувствовала признаки выгорания 😓 Попросила мужа (ChatGPT) собрать список причин выгорания 1. Хронический стресс 2. Потеря контроля и смысла 3. Перегрузка 4. Эмоциональное истощение 5. Несоответствие ожиданий и реальности Основная причина сейчашней усталости — дисбаланс усилий и отдачи. Весь Q1 и часть Q4 (помимо прочего) я занималась построением направления инфлюенс: ✔️с

20custom 54066690330995023724custom 52359501475773262763🔥1

9 Apr 2026, 02:57 UTC467 views23 reactionsread 8 August 2026

Будучи молодым менеджером, я панически боялась увольнять людей. Но и кейсы были специфичные: 😊 то менеджмент предлагает уволить человека, потому что «бесит». 😊 то нужно срочно сократить расходы в след месяце, чтобы показать инвесторам рост / прибыль. 😊 то тебе просто передали фамилию, пару строк объяснения и задание расстаться с человечком в нужный срок. 😊 то открыто ставят условие: либо увольняешь человека, либ

14👍5custom 52359501475773262762custom 54066690330995023722

3 Mar 2026, 11:33 UTC462 views31 reactionsread 8 August 2026

Как Head of Brand, при аудите Instories я сразу заметила зону отчуждения — саппорт. ТОЧКА А 😟 Отзывы в сторах не отвечены 😟 В соцсетях недовольные комменты 😟 Амбициозный KPI команды сделать CSAT 65%* 😟 Команда — полтора выгоревших землекопа. *это когда 35% тикектов решились неудовлетворительно. "Саппорт — самый важный отдел в компании", — говорил Ратмир Тимашев (основатель Veeam) на каждом олл-хэндсе, каждом кикоф

22custom 54066690330995023725custom 53888809578916859564

16 Feb 2026, 15:28 UTC684 views11 reactionsread 8 August 2026

❗ Сразу трёх человек ищу к себе в команду в Instories — Creative SMM Producer — Influence Manager — Influence Scout В двух словах про компанию — удалёнка, зп в любимой валюте и весь базовый пакет. В двух словах про вакансии: 1) Креативный продюсер. Нужен визионер. С нас бюджеты, с тебя — умение защитить и воплотить классные идеи, интерес к ИИ, понимание работы соцсетей. Целевые метрики — Reach, ER и как следствие

7custom 52359501475773262762custom 54066690330995023722

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

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

“Я и сам своего рода маркетолог” (@marketing_deshevo), 363 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/marketing_deshevo.

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.