Telegram RegisterThe public register of Telegram
Telegram profile photo for ТАКТИКА АДВЕРЗА (TACTICA ADVERSA)

Channel

ТАКТИКА АДВЕРЗА (TACTICA ADVERSA)

@Tactica_Adversa

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

731subscribers

-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-1001413692309
TypeChannel
Username@Tactica_Adversa
CreatedBetween 1 April 2019 and 31 October 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live27 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 27 August 2026
On Telegramt.me/Tactica_Adversa

Growth

730735732.57 August 2026 — 735 subscribers7 August 2026 — 735 subscribers20 August 2026 — 730 subscribers27 August 2026 — 731 subscribers7317 August 202627 August 2026
4 measurements spanning 20 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 729–736 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Aug 2026, 05:53731+1
20 Aug 2026, 21:37730-5
7 Aug 2026, 01:27735no change
7 Aug 2026, 01:17735first reading

Engagement

19 posts held, back to 14 June 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
37.1%
avg views ÷ 731 subscribers
Avg views / post
271
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 30 July 2026
Posts held19 (14 June 202630 July 2026)
Views total271
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 01:17 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.

Reaction mix

57 reactions across 10 posts, in 3 distinct kinds. The most used accounts for 91.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍5291.2%
🎉47.02%
👎11.75%

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 10 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 57reactions 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 14 June 2026 to 30 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

30 Jul 2026, 16:04 UTC271 viewsread 7 August 2026
Photo

#СВО Слова Д.А. Медведева и график в моменте...

29 Jul 2026, 13:48 UTC320 views7 reactionsread 7 August 2026

#BRENT #CB #CL https://www.youtube.com/watch?v=fH7SwEcdcdU

👍6👎1

24 Jul 2026, 05:33 UTC457 views4 reactionsread 7 August 2026
Photo

#SPCX В поисках дна... 240 мин, отработка основного сценария.

👍4

19 Jul 2026, 15:11 UTC525 views1 reactionsread 7 August 2026
Photo

#HG На годах открыта цель - 9.43, наиболее вероятное (если без потрясений и форс-мажоров) время достижения которой - период с октября 2026 по февраль 2027...

👍1

19 Jul 2026, 15:00 UTC424 viewsread 7 August 2026

#MUUSDT 1. не вижу Параболы на данных от Бинансе. 2. не думаю, что классическая стратегия фондового рынка (не только по внешнему виду, но и по внутреннему "убранству") buy and hold уместна для крипты, но я вполне могу ошибаться. Как бы то ни было у крипты долгосрочные по времени и новые максимумы по целям сейчас не просматриваются.

19 Jul 2026, 14:37 UTC360 viewsread 7 August 2026

#VIX Не "либо-либо", а "и-и". Если детальнее, то высокая волатильность ожидается по январь 2028 года включительно...

19 Jul 2026, 14:30 UTC334 viewsread 7 August 2026

Без детализации, а в рамках более общего, инвестиционного подхода (о котором говорил на прошлом эфире) с горизонтом 7-8 месяцев средне-срочно и, далее, 3-5 лет - цены на фондовом рынке России оптимальны для входа.

19 Jul 2026, 14:21 UTC349 views6 reactionsread 7 August 2026

#AMD #INTL #SNDK Пока эфир откладывается сценарии по заявкам: 1. AMD - на горизонте ближайших трех недель цели: 411-407. При пробое - 396 и 353. 2. INTEL - область 85-81 и в случае ее преодоления - 50. 3. Sandisk - по вторую декаду октября включительно - 936 и 590. По всем трем бумагам временной горизонт с запасом, т.к. высокая вероятность роста волатильности может обеспечить более быстрое достижение указанных цел

👍6

14 Jul 2026, 22:38 UTC467 views5 reactionsread 7 August 2026
Photo

#TTF #NG Ну, а теперь, основание упомянутой выше параболы (853.94) выступило сопротивлением при начале "Эпической (такой всей из себя) Ярости" и является хорошим ориентиром для будущего...

👍5

14 Jul 2026, 22:26 UTC438 viewsread 7 August 2026
Photo

#TTF #NG Самое время вспомнить о натуральном газе. Сценарий за двое суток до начала СВО, выступивший в моменте своего рода графическим отражением пожелания, которое выглядит сейчас, буквально как пророчество, Медведева. Отработку день за днем с дополнением можно отследить по тегу #TTF. И вот чем тогда все завершилось (см. график).

8 Jul 2026, 17:22 UTC472 viewsread 7 August 2026

#LIVE #ШколаТА Очередной эфир или очередной семестр? По последнему странным образом стали обращаться, но сразу предупреждаю - тема/ы тогда за вами. Так что предлагайте. P.S. Можно и пленэр.

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

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

“ТАКТИКА АДВЕРЗА (TACTICA ADVERSA)” (@Tactica_Adversa), 731 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/Tactica_Adversa.

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.