Channel
@concordgroup_official
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cross-platform identity · Referenced elsewhere · Cite this entry
458,149subscribers
-792 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 316,228–1,000,000.
| Telegram ID | -1001758168560 |
|---|---|
| Type | Channel |
| Username | @concordgroup_official |
| Description | https://m.vk.com/concordgroup_official |
| Created | 5 November 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/concordgroup_official |
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 74% 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 |
|---|---|---|
| 14 Aug 2026, 22:46 | 458,149 | -121 |
| 13 Aug 2026, 12:17 | 458,270 | -87 |
| 12 Aug 2026, 10:24 | 458,357 | -90 |
| 11 Aug 2026, 08:34 | 458,447 | -90 |
| 10 Aug 2026, 12:01 | 458,537 | -86 |
| 9 Aug 2026, 11:51 | 458,623 | -91 |
| 8 Aug 2026, 08:16 | 458,714 | -101 |
| 7 Aug 2026, 04:59 | 458,815 | -111 |
| 6 Aug 2026, 05:10 | 458,926 | -15 |
| 6 Aug 2026, 00:42 | 458,941 | no change |
| 5 Aug 2026, 23:50 | 458,941 | first reading |
20 posts held, back to 23 June 2023 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 23 pagesof 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 20 posts for this entry, the most recent from 14 December 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 15 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.
Measured directly from 1 video 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.
The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 27 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
Прощание с Евгением Викторовичем состоялось в закрытом формате. Желающие проститься могут посетить Пороховское кладбище.
#1851 Публикуем ответ Евгения Пригожина на многочисленные вопросы СМИ касательно последних событий
Voice message, posted without a caption
Voice message, posted without a caption
И множество писем
Photo, posted without a caption
Voice message, posted without a caption
#1847 Заявление Евгения Пригожина
#1846 Пригожин.ЧВК Вагнер. Ростов
#1845 Публикуем запрос от телеграм-канала «Горячие точки» и ответ: Евгений Викторович, в СМИ появилась информация о том, что ЧВК Вагнер взяли административные здания и штаб ЮВО в Ростове. Фактически город находится под вашим контролем, трудно ли было взять Штаб, оказывали ли вам сопротивление?
#1844 Заявление Евгения Пригожина
Showing the 12 most recent of 20 posts we hold for @concordgroup_official. 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 — 85,640 of 1,480,944entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 20 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
A Wikidata item names this Telegram handle as belonging to the entity it describes. This is Wikidata’s claim, not a verification made by this register — nobody here confirmed that the account is genuinely operated by the entity named. Wikidata content is CC0; every fact below is dated to when it was read from Wikidata, not to when the association was first made there.
| Label | Yevgeny Prigozhin |
|---|---|
| Description | Russian mercenary leader, oligarch, restaurateur, former owner of Wagner PVC (1961–2023) |
This handle named by sources this register does not control and did not measure — each shown exactly as found, attributed by name, dated to when it was read.
Hacker News
This handle was named 4 times in a Hacker News comment or story, via the public Algolia search API. HN comment and story text has no confirmed reuse licence, so nothing quoted from either is reproduced here — only that a mention exists, when, and by whom, with a link to read it at the source.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“Пресс-служба Пригожина” (@concordgroup_official), 458,149 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/concordgroup_official.
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.