Telegram RegisterThe public register of Telegram

Channel

Ivan Rybka

@ivan_rybka

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Cite this entry

26,341subscribers

+1 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001282222585
TypeChannel
Username@ivan_rybka
DescriptionЛюдоньки, цей телеграм канал створено для публікації новин по пригону, актуальних пропозицій по автомобілям з Німеччини «На продаж», а також іншої цікавої інформації, задля якої іноді просто не має часу або сенсу знімати нове відео. Приємного перегляду!
CreatedBetween 1 April 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held7
Confirmed unchanged2 times, most recently 14 August 2026
On Telegramt.me/ivan_rybka

Growth

26,33726,35026,343.57 August 2026 — 26,340 subscribers8 August 2026 — 26,342 subscribers9 August 2026 — 26,337 subscribers10 August 2026 — 26,341 subscribers11 August 2026 — 26,350 subscribers12 August 2026 — 26,344 subscribers13 August 2026 — 26,341 subscribers26,3417 August 202613 August 2026
7 measurements spanning 6 days, net +1. 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 26,335–26,352 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 06:1826,341-3
12 Aug 2026, 05:3126,344-6
11 Aug 2026, 05:1126,350+9
10 Aug 2026, 05:5826,341+4
9 Aug 2026, 02:3326,337-5
8 Aug 2026, 05:5526,342+2
7 Aug 2026, 17:1526,340first reading

Engagement

22 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 19 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
55.7%
avg views ÷ 26,341 subscribers
Avg views / post
14,700
15 posts measured
Reaction rate
0.52%
reactions ÷ views · ER floor
Posts in window
15
of 22 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 11 August 2026
Posts held22 (13 July 202611 August 2026)
Views total219,950
Reactions total1,143
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Aug 2026, 03:50 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.

What this channel posts

Photos
7,790
Videos
244
Links
1,830

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. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
2m 44s
Average length
55s

Measured directly from 3 videos 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.

Reaction mix

1,695 reactions across 22 posts, in 16 distinct kinds. The most used accounts for 51.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍86951.3%
36521.5%
🔥23914.1%
😁472.77%
😱342.01%
👎291.71%
🤔261.53%
🏆241.42%
👌191.12%
🍌160.944%
💯80.472%
60.354%
😍40.236%
😢40.236%
👏30.177%
🤬20.118%

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

Measured over the 22 most recent posts we hold, published 13 July 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.

Telegram Stars

Stars received
1
across the posts below
Posts paid on
1
of 22 we hold a reading for · 5%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @ivan_rybka. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 22 most recent posts we hold for this entry, published 13 July 2026 to 11 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

11 Aug 2026, 05:57 UTC≈8,150 views74 reactionsread 15 August 2026
Video

Забрав підписник для експлуатації по Німеччині 🇩🇪

👍57👌114🤬2

Signed Ivan Rybka

8 Aug 2026, 13:44 UTC≈10,600 views41 reactionsread 15 August 2026

Тема витрати - то є тема холіварна, а хто я такий щоб її не підтримати: https://youtu.be/QUb7XebseuA

👍365

Signed Ivan Rybka

8 Aug 2026, 08:51 UTC≈10,400 views76 reactionsread 15 August 2026
Photo

Доставлено підписнику по Німеччині ✅

👍678😢1

Signed Ivan Rybka

7 Aug 2026, 11:37 UTC≈12,500 views93 reactionsread 15 August 2026

🚘 BMW 320D Touring 📅 06/2022 | 🇩🇪 Німеччина 🛣 173.000 км 🔧 2.0D B47 190 к.с. | ZF (8) | Повний 🎨 Чорний металік VIN: WBA31DZ030FN20398 ⚠️ Авто зараз у Німеччині, доставка в Україну — 1–2 тижні 🔑 Ключові опції: Безпека та асистенти: • BMW LED фари • Адаптивний круїз • Смуга руху • Сліпі зони • Парктроніки + камера • Автодальній • Вибір режимів Комфорт: • 3-зонний клімат • KEYLESS • Підігрів сидінь • Підігрів/регу

46🔥27👍15😍4👎1

Signed Ivan Rybka

7 Aug 2026, 11:20 UTC≈10,200 views51 reactionsread 15 August 2026

🚘 Škoda Octavia IV iV 📅 04/2021 | 🇨🇿 Чехія 🛣 153.800 км 🔧 1.4 TSI 156 к.с. | DSG DQ400e (6) 🔌 Зарядний порт Type2 3.6kW 🔋 Батарея Li-ion 10.4kW.h. 🎨 Сірий (metal grey) VIN: TMBJW7NX3MY152962 ⚠️ Авто зараз у Німеччині, доставка в Україну — 1–2 тижні 🔑 Ключові опції: Безпека та асистенти: • Матричні LED фари • Адаптивний круїз • Front Assist + утримання смуги • Сліпі зони • Парктроніки 360° Комфорт: • Безключовий

🔥32👎853👍3

Signed Ivan Rybka

6 Aug 2026, 16:35 UTC≈10,500 views58 reactionsread 15 August 2026

Незнаю коли вам це може знадобитись, бажаю щоб якнайскоріше, але якщо вже треба буде - ось є інформація: https://youtu.be/ZmCNlHbL31c

👍44🏆95

Signed Ivan Rybka

6 Aug 2026, 10:00 UTC≈10,300 views122 reactionsread 15 August 2026
Forwarded from @valerii_markusVideo

Шановне панство, вітаю нас із позитивними новинами. Пропоную підсилити нового Головнокомандуючого якісним озброєннями )) Відкриваємо збір на УДАРНІ ДРОНИ та РЕБи для Сил оборони України. Ціль збору — 25 000 000 грн. За донат від 200 грн розігруємо раритетний автомобіль Яґуар 1984-го року. Банка: https://send.monobank.ua/jar/6Qe52N57Bx Для переказів з інших банків: 4874 1000 3040 3904 Ми намагаємося робити збори

81👍35😁5👎1

Signed Ivan Rybka

6 Aug 2026, 10:00 UTC≈10,800 views91 reactionsread 15 August 2026
Photo

Дарують автомобіль! Людоньки, всім привіт! У 2022му році я один з перших розіграв своє авто на допомогу ЗСУ. Тоді ми зібрали більше 1млн.грн, за які купили не 3 як планувалось, а 5 автівок і купу майна та витратних матеріалів для допомоги війську і волонтерам. На сьогодні потреби у забезпеченні наших військових не змінились і ваша допомога потрібна як ніколи. Докиньте посильний донат на збір, посильте військо, а за

👍7613😁2

Signed Ivan Rybka

4 Aug 2026, 14:07 UTC≈12,600 views100 reactionsread 15 August 2026

🚘 Škoda Octavia IV (A8) 📅 03/2023 | 🇨🇿 Чехія 🛣 171.000 км 🔧 2.0 TDI 150 к.с. | DSG DQ381 (7) 🎨 Graphit-Grau Metallic VIN: TMBJJ8NX5PY066917 ⚠️ Авто зараз у Німеччині, доставка в Україну — 1–2 тижні 🔑 Ключові опції: Безпека та асистенти: • Матричні LED фари • Адаптивний круїз • Front Assist + утримання смуги • Сліпі зони • Парктроніки 360° • Head-Up Комфорт: • Безключовий доступ • 2-зонний клімат • Підігрів сидін

52👍32🔥11😢3👌2

Signed Ivan Rybka

1 Aug 2026, 18:57 UTC≈15,000 views67 reactionsread 15 August 2026

Контент замість казки на ніч 😴 https://youtu.be/T1ct5ILj1uE

👍47🏆155

Signed Ivan Rybka

29 Jul 2026, 15:56 UTC≈20,600 views85 reactionsread 15 August 2026
Forwarded from @SG_Automobile

Таких автівок ми точно ще не показували 😉 https://youtu.be/2AwmK05FuGg

🔥59👍192👎2😁2👌1

Signed Ivan Rybka

25 Jul 2026, 15:40 UTC≈24,600 views58 reactionsread 15 August 2026

Тепер я нарешті знаю що означає «Audi не їде» 🤬 https://youtu.be/faYeVVBwE6g

😱34👍23😁1

Signed Ivan Rybka

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

Posts edited after publishing

@ivan_rybka edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
7 August 2026
Most recent edit
11 August 2026

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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.

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.

“Ivan Rybka” (@ivan_rybka), 26,341 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/ivan_rybka.

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.