Channel
@G_L830
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
14subscribers
+9 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003850594164 |
|---|---|
| Type | Channel |
| Username | @G_L830 |
| Created | Between 1 February 2026 and 12 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 3 times, most recently 11 September 2026 |
| On Telegram | t.me/G_L830 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Aug 2026, 08:15 | 14 | +1 |
| 21 Aug 2026, 05:39 | 13 | +1 |
| 15 Aug 2026, 03:16 | 12 | +7 |
| 13 Aug 2026, 00:04 | 5 | no change |
| 7 Aug 2026, 02:03 | 5 | first reading |
8 posts held, back to 12 May 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 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 8 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
16 reactions across 8 posts, in 2 distinct kinds. The most used accounts for 87.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 14 | 87.5% | |
| ✍ | 2 | 12.5% |
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 8 of the 8 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 16 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 12 May 2026 to 11 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.
Согдийские потомки G-L830 в Китае. В китайской базе данных есть 7 образцов G-L830 (G1b): 4 ханьца (вкл. двоих с G-Z17874), 1 уйгур (G-Z17874), 1 дунганин Ма (马) из Цзинаня, Шаньдун, и 1 монгол из Ордоса (G-Y16796). Интересны ханец Ши (石) и дунганин Ма (马). Фамилия Ши относится к «Девяти согдийским фамилиям» и связывается с областью Шаш (Ташкент). Эти фамилии согдийцы приняли при Суй и Тан. Поэтому Ши мог унаследова…
👍5
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.
👍3
Status update: TMRCA с палео Кюйгенжар 5 имеет очень большую погрешность, вероятно из-за плохого покрытия палео образца. Среднее значение на рубеже нашей эры кажется маловероятным.
👍2
Мой биг наконец то появился на временном дереве. Посмотрим будут ли еще какие то обновления/уточнения. Хотелось бы узнать мой точный TMRCA с палео Кюйгенжар 5. Стоит отметить, что теперь появилась более точная TMRCA субклада FTB22321, а именно 1697 BCE. Эта датировка находится на поздней границе периода БМАК
👍2
G1b-L830 sample from Georgia. Surname: Davitadze. The sample is listed from Batumi, Adjara, Georgia.
👍1
Расчеты на основе STR маркеров показывают, что узбек из Ташкента с G1b скорее всего является потомком арабов (исламских миссионеров?). Ближайшим в базе G1b оказался араб Aqel из Палестины, образовавший общую ветку с итальянцем по фамилии Passaro, а также араб Alsabeen
✍1
G1b бухарские купцы мусульмане (город Варзонзи/Вардана)
👍1
G1b турки и туркмены
✍1
Showing the 8 most recent of 8 posts we hold for @G_L830. 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.
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.
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.
“G-L830 research” (@G_L830), 14 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/G_L830.
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.