Telegram RegisterThe public register of Telegram

Channel

Caucasus DNA

@caucasdna

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

1,216subscribers

+5 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002047078537
TypeChannel
Username@caucasdna
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/caucasdna

Growth

1,2101,2161,2136 August 2026 — 1,211 subscribers7 August 2026 — 1,210 subscribers10 August 2026 — 1,211 subscribers13 August 2026 — 1,216 subscribers6 August 202613 August 2026
4 measurements spanning 7 days, net +5. 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,209–1,217 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 11:181,216+5
10 Aug 2026, 08:011,211+1
7 Aug 2026, 15:501,210-1
6 Aug 2026, 21:031,211first reading

Engagement

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

ERR · 30 days
37.6%
avg views ÷ 1,216 subscribers
Avg views / post
457
16 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
17
of 17 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 6 August 2026
Posts held17 (23 July 20266 August 2026)
Views total7,319
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 21:03 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.

Recent posts

6 Aug 2026, 04:32 UTC157 viewsread 6 August 2026
Photo

Тепловая карты генетической близости к Ямной культуре (протоиндоевропейцам) Только современные популяции Максимальное расстояние = 0.20 https://x.com/heatmappr

4 Aug 2026, 19:34 UTC241 viewsread 6 August 2026
Forwarded from @TsakhurArchive

🔠🔠🔠🔠🔠🔠 🌟 Введение Вопрос о происхождении кумыков, одного из крупнейших тюркских народов Северного Кавказа, долгое время оставался предметом острых дискуссий. Упрощённый взгляд на кумыков как на "пришлый" степной этнос, вытеснивший или полностью замещавший коренное население равнин Дагестана, не выдерживает критики при комплексном междисциплинарном подходе. Ключевая методологическая ошибка таких построений заключа

4 Aug 2026, 00:05 UTC240 viewsread 6 August 2026
Forwarded from @tschqoni

Лексика осетинского/аланского происхождения в сванском языке Аланы в V – XIV вв. активно участвовали в исторических событиях и жизни многих народов Кавказа и имели интенсивные отношения с ними в торговле, политике, войне, культуре и др. аспектах. Результатами этих взаимоотношений проявляется и лексике кавказских языков. Следы этих контактов видны и в сванском языке. По мнению Л. Лаврова, сваны могли проживать и на

1 Aug 2026, 18:50 UTC301 viewsread 6 August 2026
Forwarded from @turkicdnaPhoto

Проект по полногеномному секвенированию в рамках инициативы по изучению геномного разнообразия Центральной Азии выявил различия в истории популяций, а также признаки адаптации и интрогрессии. Народы Центральной Азии недостаточно представлены в геномных исследованиях, что ограничивает понимание их генетической истории и риска заболеваний. Мы создали Проект по изучению геномного разнообразия Цент. Азии и секвенировали

1 Aug 2026, 11:25 UTC291 viewsread 6 August 2026
Forwarded from @Genealogy_of_the_LaksFile

если кому то еще нужно древо 1842 с отмеченными процентами по народам. актуальная версия всегда будет лежать в предикторе по кнопке "🌳 J-Z1842 clade tree" https://ypredictor.github.io/#clade

1 Aug 2026, 10:54 UTC276 viewsread 6 August 2026
Forwarded from @turkicdnaPhoto

О прото-тюркской прародине. Что нам говорит лингвистика? PT - Proto-Turkic ... Turkic peoples shared their ancestry with populations from southern Siberia and Mongolia, supporting the hypothesis that they originated there. ... current genetic evidence is not adequate to track the exact time and location for the origin of the PT lang., it is clear that it probably originated somewhere in northeastern Asia given the

30 Jul 2026, 13:32 UTC262 viewsread 6 August 2026
Forwarded from @dargwadnaFile

Почему «встать в корень» Y-дерева — это иллюзия, а не повод для гордости Знакомая сцена: человек видит на дереве FamilyTreeDNA длинную прямую линию, уходящую вглубь веков, и заявляет: «Мы в самом корне, ветка наша, вы все пошли от нас». На самом деле эта линия говорит ровно одно: с ним пока никто не совпал. Это не биология, это дыра в данных. Собрал справочник по чтению дерева и раздела Discover. PDF, 19 страниц,

27 Jul 2026, 21:27 UTC431 viewsread 6 August 2026
Forwarded from @Genealogy_of_the_LaksPhoto

Результат BigY700: #Алиев_И #Алиев_И - лакец из с. Тулизма Гаплогруппа: J1-Z1842 Terminal SNP: J-BY122167 #Алиев_И попадает в ветвь J-BY122167 возрастом ~1000 лет (X век), в корень ветви, где расположены результаты хурхинцев #Дибиров и #Алиханов (600 лет между собой) и потомков Шамхалов (600 лет между собой), он делит ветку вместе с: #Дибиров #Алиханов #Муртазалиев* #Уллубиев #Умаев #Велибеков* #Мамайханов* (1) #М

26 Jul 2026, 04:13 UTC521 viewsread 6 August 2026
Photo

Отличия между северными и южными европейцами.

26 Jul 2026, 00:12 UTC443 viewsread 6 August 2026
Forwarded from @scythosarmatianVideo

🐴 Скифы и их внешность

25 Jul 2026, 12:58 UTC729 viewsread 6 August 2026
Video

🐴 Ямная культура Ямная культура — арх культура раннего бронзового века, существовавшая примерно 3300-2600 гг. до н. э. в Понтийско-Каспийской степи. Исследования палеоДНК показывают, что её носители внесли значит. вклад в ген. состав многих совр. популяций Европы, а их наследие также распространилось в Цент. и Юж. Азию. Многие исследователи связывают ямную культуру с распространением позднепраиндоевропейского языка

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

Citation-graph rank — 131,677 of 1,189,255entries 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.

Forward network

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.

Mentions

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

“Caucasus DNA” (@caucasdna), 1,216 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/caucasdna.

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.