Telegram RegisterThe public register of Telegram
Telegram profile photo for Корені

Channel

Корені

@koreni_org_ua

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

326subscribers

+63 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003635654875
TypeChannel
Username@koreni_org_ua
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live12 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 12 September 2026
On Telegramt.me/koreni_org_ua

Topic

Other / unclassifiable — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 50% 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

263326294.56 August 2026 — 263 subscribers7 August 2026 — 263 subscribers21 August 2026 — 264 subscribers27 August 2026 — 316 subscribers3 September 2026 — 324 subscribers12 September 2026 — 326 subscribers6 August 202612 September 2026
6 measurements spanning 36 days, net +63. 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 254–335 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Sept 2026, 06:40326+2
3 Sept 2026, 19:38324+8
27 Aug 2026, 08:46316+52
21 Aug 2026, 05:07264+1
7 Aug 2026, 01:02263no change
6 Aug 2026, 18:46263first reading

Engagement

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

Reaction mix

67 reactions across 17 posts, in 7 distinct kinds. The most used accounts for 38.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥2638.8%
😁1420.9%
1116.4%
🤩811.9%
👍34.48%
🤔34.48%
🤝22.99%

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

Measured over the 20 most recent posts we hold, published 13 July 2026 to 6 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

6 Aug 2026, 14:36 UTC37 views1 reactionsread 7 August 2026
Forwarded from @fazulyanovPhoto

Шановне панство, дорога родино, поважні гості! Нарешті настав час Передплати! Спекотна передплата на Повний план (Complete Plan) MyHeritage вже тут — 50% знижки на найкращий з існуючих планів передплати. За половину вартості ви отримуєте річний доступ до всіх функцій MyHeritage, які сьогодні є найціннішими для генеалогічних досліджень. 📅 Акція триває з 6 по 10 серпня 2026 року. Для тих, кому не треба зайвих слів

1

4 Aug 2026, 19:35 UTC116 views2 reactionsread 7 August 2026

Нові надходження до бази (7): 🗂 Гереженівка – перепис, 1897 📅 1897 | 📊 210 записів 🏛 ДАКО-384-12-239, ДАКО-384-12-240, ДАКО-384-12-241 👤 Володимир Цибульський 🔗 Переглянути таблицю 🗂 Мар'янівські хутори (Мар'янівка), Дніпровський пов. Таврійська губ. | шлюби (1910-1913) 📅 1910–1913 | 📊 209 записів 🏛 ДАХеО-259-33-1, ДАХеО-259-33-2 👤 Олена Савків 🔗 Переглянути таблицю 🗂 Наталівка, Дніпровський пов. Таврійська губ.

🔥2

31 Jul 2026, 19:22 UTC185 views4 reactionsread 7 August 2026

Нові надходження до бази (1): 🗂 Лагодів (Перемишлянський), МК 1858-1863 📅 1858–1863 | 📊 173 записів 🏛 ЦДІАЛ-201-4а-2933 👤 Степан Проць 🔗 Переглянути таблицю

🔥31

28 Jul 2026, 10:32 UTC268 views13 reactionsread 7 August 2026

Завдяки героїчним зусиллям команди Коренів пошук знову працює! (Я взагалі хз, що це було, воно ожило само після ребута)

😁13

28 Jul 2026, 08:24 UTC267 viewsread 7 August 2026

Щось серйозно не так з пошуком. Буду досліджувати пізніше

27 Jul 2026, 19:25 UTC250 views1 reactionsread 7 August 2026

Нові надходження до бази (2): 🗂 Списки виборців по виборам в сейм 86 виборчої дільниці. Гміна Сарни, м. Сарни (працівники Kier. Rob. Nr 13) 📅 1938 | 📊 767 записів 🏛 ДАРО-263-1-65 👤 Sa Kan 🔗 Переглянути таблицю 🗂 Дем'янці – сповідний розпис (1795) 📅 1795 | 📊 1770 записів 🏛 ЦДІАК-127-1015-110 👤 Радана Кузьменко 🔗 Переглянути таблицю

1

26 Jul 2026, 19:08 UTC238 views3 reactionsread 7 August 2026

Нові надходження до бази (7): 🗂 Наталівка, Дніпровський пов. Таврійська губ. | народження (1919) 📅 1919 | 📊 1085 записів 🏛 ДАХеО-259-36-5 👤 Олена Савків 🔗 Переглянути таблицю 🗂 Наталівка, Дніпровський пов. Таврійська губ. | шлюби (1905, 1907, 1913-1919) 📅 1905–1919 | 📊 1214 записів 🏛 ДАХеО-259-36-1, ДАХеО-259-36-2, ДАХеО-259-36-3 та ще 2 👤 Олена Савків 🔗 Переглянути таблицю 🗂 Списки виборців по виборам в сейм 87 в

🔥3

26 Jul 2026, 13:37 UTC179 views4 reactionsread 7 August 2026

Дякую усім за таблички! Будь ласка, коли присилаєте табличку, вписуйте в поле назви – назву населеного пункта, але так, аби вона була унікальною (не "Писарівка", а "Писарівка (Шаргородська)"). Так само, якщо назва змінилася від часу складання документа (був Янів, а став Іванів), краще сучасну назву подати в дужках: "Янів (Іванів Хмільницький)".

🤔3👍1

23 Jul 2026, 19:15 UTC243 views4 reactionsread 7 August 2026

Нові надходження до бази (2): 🗂 Політанки 1822-1853 📅 1822–1853 | 📊 9055 записів 🏛 ДАХмО-315-1-7147 👤 Віталій Перегончук 🔗 Переглянути таблицю 🗂 Списки виборців по виборам в сейм 86 виборчої дільниці. Гміна Сарни, м. Сарни 📅 1938 | 📊 710 записів 🏛 ДАРО-263-1-65 👤 Sa Kan 🔗 Переглянути таблицю

🔥4

22 Jul 2026, 16:29 UTC242 views5 reactionsread 7 August 2026

ЇХ Подкаст – випуск № 2 Громадо, наш з Олександром @spravnakachka генеалогічний "ЇХ Подкаст" набирає обертів. У другому епізоді ми годину і двадцять хвилин розбираємо неочевидні аспекти родоводу: • етику ведення дерева: чи варто вести спільне дерево подружжя, чи краще окремо • походження українських прізвищ і те, як Московія привласнила по батькові на "-ович" • психологічний профіль генеалога: відкладене задоволен

👍2🔥21

22 Jul 2026, 08:03 UTC205 viewsread 7 August 2026

Створив спільноту для генеалогії Шаргородського та Джуринського районів! Долучайтеся, хто наш https://www.facebook.com/groups/1748115539548381

Showing the 12 most recent of 20 posts we hold for @koreni_org_ua. 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 1 registered channel — 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.

“Корені” (@koreni_org_ua), 326 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/koreni_org_ua.

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.