Channel
@condottieros
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Advertising · Posts · Citations · Telegram's recommendations · Cite this entry
211,502subscribers
+20 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
| Telegram ID | -1001264305087 |
|---|---|
| Type | Channel |
| Username | @condottieros |
| Description | Авантюристы из сеньории. Дикие гуси современности. Ветеран PMC Wagner Быстро,качественно,дорого. Вип,Лакшери и хорошая музыка. ——————————————- Для рекламы сюда @Soldo_bot |
| Created | 14 October 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 38 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/condottieros |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 79% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Sept 2026, 00:55 | 211,502 | +43 |
| 18 Sept 2026, 21:17 | 211,459 | +288 |
| 16 Sept 2026, 16:15 | 211,171 | -43 |
| 14 Sept 2026, 19:16 | 211,214 | +16 |
| 13 Sept 2026, 07:58 | 211,198 | -46 |
| 11 Sept 2026, 09:38 | 211,244 | -10 |
| 8 Sept 2026, 18:39 | 211,254 | -75 |
| 5 Sept 2026, 11:19 | 211,329 | +39 |
| 3 Sept 2026, 10:46 | 211,290 | +11 |
| 2 Sept 2026, 05:05 | 211,279 | -8 |
| 1 Sept 2026, 06:46 | 211,287 | +42 |
| 31 Aug 2026, 03:24 | 211,245 | +176 |
| 30 Aug 2026, 04:03 | 211,069 | +214 |
| 29 Aug 2026, 02:46 | 210,855 | +46 |
| 28 Aug 2026, 06:13 | 210,809 | -98 |
| 27 Aug 2026, 09:25 | 210,907 | -13 |
| 26 Aug 2026, 11:44 | 210,920 | -73 |
| 25 Aug 2026, 08:11 | 210,993 | -95 |
| 24 Aug 2026, 11:32 | 211,088 | -23 |
| 22 Aug 2026, 21:03 | 211,111 | first reading |
737 posts held, back to 5 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 107 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 27 September 2026 |
|---|---|
| Posts held | 737 (5 August 2026 – 27 September 2026) |
| Views total | 35,348,400 |
| Reactions total | 1,019,817 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 27 Sept 2026, 08:10 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.
Lifetime counters from Telegram’s own channel header, read 27 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 60 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
1,640,474 reactions across 721 posts, in 21 distinct kinds. The most used accounts for 21.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 346,080 | 21.1% | |
| 👍 | 317,766 | 19.4% | |
| 💯 | 195,445 | 11.9% | |
| 🤣 | 188,313 | 11.5% | |
| 😁 | 142,534 | 8.69% | |
| 🙏 | 110,740 | 6.75% | |
| ❤ | 103,904 | 6.33% | |
| 🤔 | 73,943 | 4.51% | |
| 🤬 | 71,699 | 4.37% | |
| 👎 | 29,244 | 1.78% | |
| 👏 | 22,005 | 1.34% | |
| 😱 | 8,784 | 0.535% | |
| 😭 | 6,756 | 0.412% | |
| 😎 | 5,615 | 0.342% | |
| 👌 | 4,051 | 0.247% | |
| 🕊 | 3,605 | 0.22% | |
| custom 5220181900999544591 | 3,538 | 0.216% | |
| ⚡ | 2,878 | 0.175% | |
| custom 5438537681845895651 | 1,697 | 0.103% | |
| 😡 | 1,279 | 0.078% | |
| 1 further kind | 598 | 0.036% |
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 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 737 of the 737 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 1,677,700 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 737 most recent posts we hold, published 5 August 2026 to 27 September 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @condottieros. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 737 most recent posts we hold for this entry, published 5 August 2026 to 27 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| 2VtzqwB69MN | 1 | 16 September 2026 | 16 September 2026 |
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 737 most recent posts we hold, published 5 August 2026 to 27 September 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Киев Третьи сутки в город летит все что можно. Без остановки. Уже в газете Bloomberg написали, что Киев стал прифронтовым городом. Ну им там виднее конечно, из Киева.
👍1,170🔥431👏97🤣37❤35😁22😎15custom 52201819009995445919
Иран • Морская блокада КСИР начал минировать южный маршрут Ормузского пролива. План понятен — долгое противостояние в Ормузе. Это не для завтра, это по персидски надолго. Закупоривают все узкие места, берут пески под контроль.
👍840🔥81❤72🤔44⚡14🤣5👎3😎2
Не совсем понятно в чем конкретно вина министра обороны Казахстана, но национальный менталитет казахов зарешал — поставили на колени и уволили уважаемого генерала.
🤔568👍139🤣63💯57❤15custom 528278563636380709911🤬9🔥8
Это еще не всё. Уже арестованы, признаны виновными пять высокопоставленных военных, а бывший уже министр обороны встал на колени и попросил прощение у родственников погибших бойцов.
👍478🤔156🔥47custom 528278563636380709935🙏25🤣23🤬15❤14
В Казахстане сняли министра обороны после ЧП на учениях ВС Казахстана. При высадке на берег Каспия погибли 14 морпехов.
custom 5282785636363807099417😱270👍79🙏77🤔30😭26🤣10❤3
В Киеве пропали сигналы тв. Город постепенно переходит на интернет детокс.
🔥1,900👍498⚡86🤣64👏43❤39🤔20😁17
Именно поэтому, практически аннулирован договор о РСМД. Нет других сценариев, кроме одного — война без контроля человека. Без эмоций и переживаний.
💯741🤬205😱78🤔71😭26❤19👎13😁11
Наблюдаю пакт согласованности администрации Трампа с Россией, особенно в контексте регулирования ИИ и военного применения. Многие военные аналитики разведки считают, что Трамп и Путин работают вместе против демократических процессов, и выражают обеспокоенность по поводу сближения США и РФ. Скажу больше, ИИ сегодня «открывают» не для войны, хотя это тоже, а для беспрепятственного развития военных технологий. Особенно…
🤔641❤93🤣50😱29👎20👍15🔥7👌5
Одесса • Блок Ада Сколько еще надо сжечь грузовиков, что бы страховщики перестали страховать суда из Европы? С тупой настырностью баклана, хохол тащит в свои порты на убой корабли. Ну и цусима, как говорится.
👍1,710💯582🔥208🤣60❤56😁17😎6👎2
Зал заседаний ООН, 2026 год. Интенсивность использования мебели на лицо. Качество принятых решений и авторитета ООН такое же поёбанное.
😁1,760💯601😱168🔥53custom 528278563636380709929❤19👍11🤬6
Музыкальная пауза
🔥597🤣289👍60❤39👎18🤔9😱7⚡4
Всем кто на «Стажировке» на дальнем — наше с кисточкой! Желающим принять участие в выездных выступлениях Оркестра на африканском континенте — удачного набора.
❤902🔥327🙏280👍33👎11😎8🤣5custom 52827856363638070993
Showing the 12 most recent of 737 posts we hold for @condottieros. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republished by 133 registered channels. The 48 listed are the ones that have forwarded the most posts; the rest are counted here but not each listed.
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.
Named by 54 registered channels — 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 25 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“Condottiero ™” (@condottieros), 211,502 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/condottieros.
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.