Telegram RegisterThe public register of Telegram
Telegram profile photo for Таргетерия – агентство диджитал-маркетинга и SMM

Channel

Таргетерия – агентство диджитал-маркетинга и SMM

@targeteria

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

1,321subscribers

-29 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001125377828
TypeChannel
Username@targeteria
Created20 July 2017measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded7 August 2026
Last confirmed live15 September 2026
Measurements held13
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/targeteria

Growth

1,3201,3501,3357 August 2026 — 1,350 subscribers7 August 2026 — 1,350 subscribers10 August 2026 — 1,345 subscribers14 August 2026 — 1,342 subscribers17 August 2026 — 1,338 subscribers20 August 2026 — 1,337 subscribers23 August 2026 — 1,332 subscribers27 August 2026 — 1,324 subscribers30 August 2026 — 1,321 subscribers2 September 2026 — 1,320 subscribers6 September 2026 — 1,325 subscribers11 September 2026 — 1,323 subscribers15 September 2026 — 1,321 subscribers1,3217 August 202615 September 2026
13 measurements spanning 39 days, net -29. 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 1,316–1,355 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 03:151,321-2
11 Sept 2026, 12:361,323-2
6 Sept 2026, 23:401,325+5
2 Sept 2026, 05:461,320-1
30 Aug 2026, 04:241,321-3
27 Aug 2026, 08:121,324-8
23 Aug 2026, 22:151,332-5
20 Aug 2026, 15:221,337-1
17 Aug 2026, 11:331,338-4
14 Aug 2026, 04:181,342-3
10 Aug 2026, 16:121,345-5
7 Aug 2026, 11:011,350no change
7 Aug 2026, 00:151,350first reading

Engagement

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

Reaction mix

25 reactions across 3 posts, in 6 distinct kinds. The most used accounts for 28.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5283242685308617686728.0%
🔥728.0%
🎉624.0%
custom 528102415001664174028.00%
custom 528322184612729675428.00%
14.00%

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

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

5 Aug 2026, 08:00 UTC75 views8 reactionsread 7 August 2026
Photo

Если ваша реклама не окупается, откройте этот пост Прежде чем менять канал или увеличивать бюджет, проверьте всю воронку целиком. Собрали чек-лист для быстрого аудита всей воронки – листайте карточки. Тот самый контакт из последнего слайда – @manager_targeteria. Напишите ей с кодовым словом «аудит»!

🔥4custom 52832426853086176863custom 52832218461272967541

29 Jul 2026, 08:04 UTC134 views10 reactionsread 7 August 2026
Photo

Как привлечь владельцев бизнеса на онлайн-интенсив: кейс Хабра Спойлер – сделали лид ниже планового на 25% Как мы настраивали кампании и что сработало лучше всего – в карусели. А если вам хочется такой же результат, как на финальном слайде, пишите @manager_targeteria. Посчитаем цену лида для вашего бизнеса.

🎉6custom 52810241500166417402custom 52832426853086176862

27 Jul 2026, 08:03 UTC119 views7 reactionsread 7 August 2026
Photo

Нужен ли Мах вашему бизнесу? Разбираем ниши и продвижение Рынок Mах продолжает формироваться: конкуренция за внимание ниже, чем на зрелых площадках. Разобрали, кому в первую очередь стоит заходить и как продвигаться сейчас – смотрите карусель. А если вы уже уверены, что вам нужен Мах, пишите @manager_targeteria. Рассчитаем медиаплан по продвижению канала.

🔥3custom 528324268530861768621custom 52832218461272967541

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

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

“Таргетерия – агентство диджитал-маркетинга и SMM” (@targeteria), 1,321 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/targeteria.

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.