Telegram RegisterThe public register of Telegram
Telegram profile photo for Uzbek DNA

Channel

Uzbek DNA

@uzbekdna

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

716subscribers

+17 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-1002331711578
TypeChannel
Username@uzbekdna
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live12 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 12 September 2026
On Telegramt.me/uzbekdna

Topic

Science — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 20 September 2026 and assigned it the closest of 31 fixed categories, at 67% 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.

Growth

699716707.57 August 2026 — 699 subscribers7 August 2026 — 699 subscribers14 August 2026 — 703 subscribers20 August 2026 — 708 subscribers27 August 2026 — 710 subscribers3 September 2026 — 713 subscribers12 September 2026 — 716 subscribers7 August 202612 September 2026
7 measurements spanning 36 days, net +17. 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 696–719 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Sept 2026, 02:18716+3
3 Sept 2026, 19:57713+3
27 Aug 2026, 12:34710+2
20 Aug 2026, 23:48708+5
14 Aug 2026, 05:08703+4
7 Aug 2026, 05:57699no change
7 Aug 2026, 02:03699first reading

Engagement

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

Reaction mix

110 reactions across 12 posts, in 3 distinct kinds. The most used accounts for 54.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥6054.5%
👍4944.5%
🤔10.909%

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

Measured over the 14 most recent posts we hold, published 2 July 2026 to 4 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

4 Aug 2026, 11:44 UTC626 views9 reactionsread 7 August 2026
Photo

Узбек из Ташкента Род: Ходжа Q1 → Q-FT112504 По данным Family Finder, у узбека из Ташкента определена Y-гаплогруппа Q-FT112504. Её общий предок жил примерно в 1900 году до н. э. Субклад восходит к древним северным евразийцам (ANE). Древнейший образец предковой ветви Q-F1161 принадлежал западносибирскому охотнику-собирателю эпохи мезолита. Позднее родственные линии встречались в Майкопской, Ямной, Андроновской, Сру

👍8🔥1

2 Aug 2026, 11:35 UTC175 views8 reactionsread 7 August 2026
Forwarded from @qazaqdnaPhoto

Субклад R1b-L1433 является свойственным для казахов из рода Кара-кыпшак, имеет происхождение связанное с Одинцовской культурой лесостепного Алтая, что интересно как и клада R-Y20750 что было указано выше имеет сереьезный аутосомный вклад связанный с группой(WSHG) как Ботайская культура, позже в результате смешивание с группой тюрок из Севернего Казахстана образовалось Сросткинская/Кимакская кульутра что дало широкое

🔥8

28 Jul 2026, 12:59 UTC839 views10 reactionsread 7 August 2026
Photo

Узбек из Яйпана R1b → R-PH155 → R-FTB336 По результатам Family Finder у узбека из города Яйпан Узбекистанского района выявлена Y-гаплогруппа R-FTB336, общий предок которой жил около 3950 года до н. э. Она относится к редкой азиатской ветви R1b — R-PH155. Ранние носители R-PH155 известны среди населения культуры Сяохэ в Таримском бассейне, близкого к ботайской культуре и западносибирским охотникам-собирателям. Позд

🔥6👍4

24 Jul 2026, 15:50 UTC≈1,650 views17 reactionsread 7 August 2026
Photo

Узбек из Истаравшана Род: Джалаир → Ураклы R1b → R-FGC13557 По результатам FamilyFinder у узбека из Истаравшанского района Таджикистана выявлена гаплогруппа R-FGC13557, общий предок которой жил около 1700 г. до н. э. Эта редкая западноевропейская ветвь R1b встречается во Франции и Великобритании и, вероятно, связана с кельтами. Интересно, что у тестируемого обнаружено 53 сМ родства с французом. Джалаиры — древнее

🔥10👍7

18 Jul 2026, 13:59 UTC616 viewsread 7 August 2026
Forwarded from @SteppeArchivePhoto

📜 Descriptions of Physical Appearance of Turkic-Speaking Peoples in Medieval Historical Sources Credit: Steppe Archive

15 Jul 2026, 15:51 UTC878 views19 reactionsread 7 August 2026
Photo

Реконструкции средневековых тюрков в узбекской чайхане ——— O‘zbek choyxonasida o‘rta asr turkiylarining rekonstruksiyalari (AI-generated)

👍16🔥3

13 Jul 2026, 13:25 UTC≈1,590 views12 reactionsread 7 August 2026
Photo

Узбек из Ферганской области Самый ранний известный предок — из села Эскиараб, Алтыарыкский район. С2 → C-F1918 По результатам FamilyFinder у узбека из Алтыарыкского района Ферганской области выявлена гаплогруппа C-F1918, с общим предком около 1100 г. до н. э. Эта линия распространена среди азиатских степных народов как монголы, казахи, кыргызы, хазарейцы, ногайцы, каракалпаки и узбеки. Субклад C-F1918 считается х

🔥12

12 Jul 2026, 14:29 UTC426 views4 reactionsread 7 August 2026
Forwarded from @qazaqdnaPhoto

Прото-түркілік прокси деген не? Дэниел Табиннің анықтамасы бойынша, Core Xiongnu тегі прото-түркілік тектің проксиі (генетикалық баламасы) болып саналады және оғыр (Lir) мен жалпы түркі (Shaz) тармақтарын байланыстырады. Core Xiongnu құрамында шығыс азиялық тектің үлесі өте жоғары (шамамен 80–100%) және ол хунну құрамындағы сақ-сармат текті аутлайерлерден ерекшеленеді. —— Что такое прото-тюркский прокси? Согласно о

👍2🔥2

11 Jul 2026, 15:26 UTC471 viewsread 7 August 2026
Forwarded from @J2aM410Photo

▪️ Согласно Özdemir 2026, у тюркских мужчин из погребений типа Katanda (культура Altay Shaz) преимущественно выявляется гаплогруппа J2a-PH1795 — наследие культуры Bulan-Koby. ▪️ Согласно Akbari 2026, в погребениях типа Sivashovka (оногуры Цент. Европы аварского периода) преимущ. встречается гаплогруппа N1a-M2019 — наследие культуры Slab-Grave. Материал: https://x.com/aboutadna

10 Jul 2026, 08:46 UTC398 views5 reactionsread 7 August 2026
Forwarded from @G_L830Photo

The TMRCA of G-FTB22321 is estimated to live around 2230 BCE, corresponding to the onset of BMAC period. It is expected that two Uzbeks (from Bukhara and Taraz), one Pashto, Gondal Jat and chinese Hui (Dungan) all tested with G-L830 will eventually fall into G-FTB22321 subclade.

🔥5

10 Jul 2026, 08:46 UTC397 views5 reactionsread 7 August 2026
Forwarded from @qazaqdnaPhoto

🇷🇺🇰🇿 K0051 ▫️Род / Clan: Жагалбайлы — Бозбет — Шыны 🧬 G1b-FTJ64125 (BIG-Y) 📚 Время образования субклада G-FTJ64125 пока неизвестно, так как это первый результат, относящийся к данной ветви. Он является частью ветви G1b-L830. 🧬 Ранее у рода Бозбет (Жагалбайлы) уже выявлялась гаплогруппа G1b. Родство с другими носителями этой ветви превышает 3300 лет. Среди них есть представители Индии, каренов Таиланда, Палестины, Т

🔥5

7 Jul 2026, 17:10 UTC429 views5 reactionsread 7 August 2026
Forwarded from @SteppeArchivePhoto

Y-DNA & mtDN Haplogroups for Turkic & non-Turkic Speaking Groups Turkic: Kyrgyz, Uzbek, Karakalpak, Karluks from Khatlon region in Tajiktsan, Uyghur, Turkmen non-Turkic: Hazara, Tajik, Dungan Source (Supporting Information > Supporting File 2 > table S4): Whole-Genome Sequencing Pilot of the Central Asian Genomic Diversity Project Reveals Distinct Histories, Adaptation, and Introgression

👍4🤔1

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

Forward network

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.

Mentions

Named by 2 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.

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

“Uzbek DNA” (@uzbekdna), 716 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/uzbekdna.

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.