🔥 До кінця акції на квитки WAWTech залишилося 5 годин 🔥 Ще встигаєте купити квитки Regular за спеціальними цінами 😉 Купити квитки 👉 https://dou.ua/goto/NaPk
❤5😱1

Channel
@dou_polska
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Polls · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
8,662subscribers
-135 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001539043629 |
|---|---|
| Type | Channel |
| Username | @dou_polska |
| Description | Телеграм-канал українського IT-ком'юніті DOU в Польщі. • Умови розміщення реклами: https://dou.ua/goto/2XrY • Terms of advertising: https://dou.ua/goto/D1Tc • Code of Conduct: https://dou.ua/goto/pLUu Contact — @vlada_z |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 13 November 2026 |
| On Telegram | t.me/dou_polska |
Technology — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 the other topics.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear in near-verbatim form on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @doucommunity/1792927 Aug 2026, 07:17 UTC | @dou_polska/1483 · this entry27 Aug 2026, 08:00 UTC | 1.00 | 43 minutes |
| @dou_polska/1505 · this entry2 Oct 2026, 09:42 UTC | @doucommunity/184405 Oct 2026, 13:31 UTC | 1.00 | 3 days |
| @dou_polska/1506 · this entry5 Oct 2026, 10:01 UTC | @doucommunity/1850411 Oct 2026, 08:30 UTC | 1.00 | 6 days |
| @doucommunity/184466 Oct 2026, 06:21 UTC | @dou_polska/1507 · this entry6 Oct 2026, 07:30 UTC | 1.00 | 70 minutes |
| @dou_polska/1509 · this entry12 Oct 2026, 15:49 UTC | @doucommunity/1853013 Oct 2026, 11:00 UTC | 1.00 | 19 hours |
| @dou_polska/1518 · this entry28 Oct 2026, 13:19 UTC | @doucommunity/1876928 Oct 2026, 16:10 UTC | 1.00 | 2.9 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @doucommunity | 6 (6/6 hand-verifiable sample passed) | 1.00 | 11 hours | this entry (4–2) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 2 of the 2 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 43 comparable posts for this entry, running 15 July 2026 to 13 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Recorded under the key clone_source, last confirmed 14 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Nov 2026, 10:21 | 8,662 | -15 |
| 9 Nov 2026, 06:10 | 8,677 | -10 |
| 6 Nov 2026, 06:46 | 8,687 | -2 |
| 3 Nov 2026, 05:58 | 8,689 | -6 |
| 31 Oct 2026, 10:19 | 8,695 | -9 |
| 28 Oct 2026, 02:36 | 8,704 | -2 |
| 25 Oct 2026, 09:16 | 8,706 | +9 |
| 22 Oct 2026, 14:05 | 8,697 | -9 |
| 16 Oct 2026, 04:38 | 8,706 | -16 |
| 12 Oct 2026, 21:21 | 8,722 | -11 |
| 6 Oct 2026, 11:37 | 8,733 | -14 |
| 29 Sept 2026, 18:40 | 8,747 | -17 |
| 15 Sept 2026, 01:39 | 8,764 | +8 |
| 11 Sept 2026, 08:15 | 8,756 | -8 |
| 6 Sept 2026, 21:36 | 8,764 | -11 |
| 2 Sept 2026, 08:54 | 8,775 | -5 |
| 30 Aug 2026, 06:55 | 8,780 | -3 |
| 27 Aug 2026, 13:33 | 8,783 | -21 |
| 24 Aug 2026, 04:24 | 8,804 | +1 |
| 20 Aug 2026, 17:22 | 8,803 | first reading |
50 posts held, back to 15 July 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 56 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 13 November 2026 |
|---|---|
| Posts held | 50 (15 July 2026 – 13 November 2026) |
| Views total | 24,680 |
| Reactions total | 165 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 16 Nov 2026, 01:42 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.
Lifetime counters from Telegram’s own channel header, read 16 November 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.
1,005 reactions across 47 posts, in 30 distinct kinds. The most used accounts for 40.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 404 | 40.2% | |
| 👎 | 113 | 11.2% | |
| 🔥 | 94 | 9.35% | |
| 👍 | 68 | 6.77% | |
| 🖕 | 64 | 6.37% | |
| 😁 | 59 | 5.87% | |
| 🥴 | 45 | 4.48% | |
| ❤🔥 | 37 | 3.68% | |
| 🤣 | 15 | 1.49% | |
| 😢 | 13 | 1.29% | |
| 🤔 | 11 | 1.09% | |
| ⚡ | 9 | 0.896% | |
| 🗿 | 9 | 0.896% | |
| 🥱 | 9 | 0.896% | |
| ✍ | 7 | 0.697% | |
| 🆒 | 7 | 0.697% | |
| 😱 | 7 | 0.697% | |
| ☃ | 5 | 0.498% | |
| 🌚 | 5 | 0.498% | |
| 💊 | 4 | 0.398% | |
| 10 further kinds | 20 | 1.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 47 of the 50 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,005 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 50 most recent posts we hold, published 15 July 2026 to 13 November 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.
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. They are printed side by side with the count behind each rather than as a ratio: an ad and an ordinary post are not otherwise matched — for topic, for length, for hour of day — so the gap between them is a description of two groups and not the effect of one being an ad.
Measured over the 50 most recent posts we hold, published 15 July 2026 to 13 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Telegram’s own ‘edited’ marker: 2 of 10 posts held from the last 30 days (20.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
🔥 До кінця акції на квитки WAWTech залишилося 5 годин 🔥 Ще встигаєте купити квитки Regular за спеціальними цінами 😉 Купити квитки 👉 https://dou.ua/goto/NaPk
❤5😱1
Ще два дні діє акція на квитки WAWTech🔥️️️️️️ До 13 листопада включно купуйте квитки на конференцію за спеціальними цінами: 👽 1 квиток — 333 PLN 👁️ 2 квитки — 555 PLN (277,50 PLN з людини) 🔥 3 квитки — 666 PLN (222 PLN з людини) Пропозиція діє лише на квитки Regular. Кількість квитків обмежена. Купити квиток 👉 https://dou.ua/goto/NaPk
😁8❤5🌚2🐳1🤔1
11–13 листопада — спеціальні ціни на квитки WAWTech 🔥 👽 Соло — 1 квиток за 333 PLN замість 425 PLN 👁️ Дуо — 2 квитки за 555 PLN замість 850 PLN (277,50 PLN з людини) 🔥 Тріо — 3 квитки за 666 PLN замість 1 275 PLN (222 PLN з людини) Пропозиція діє лише на квитки Regular. Кількість квитків обмежена. Купити квиток 👉 https://dou.ua/goto/NaPk
☃5🤪3👍2🌚1🖕1
Ми заховали гарбузи на сайті WAWTech 🎃 З 28 до 31 жовтня знайдіть 10 гарбузів на wawtech.io та отримайте шанс виграти квитки Regular, PRO і MAX, апгрейди, мерч або знижки 🔥 😎 Хочете гарантований приз? Першими знайдіть секретний Boss Pumpkin (чорного кольору) та отримайте квиток PRO або MAX! Новий Boss з’являється кожні 3 години. 🏆 Результати розіграшу — до 5 листопада. Переможцям напишемо на email. Готові до полю…
❤12🥴6🌚1🎃1
500 грн, які працюють одразу у двох напрямках Для тебе — практичний воркшоп зі створення AI-агентів. Для військових — підтримка збору НРКастом. 4 листопада запрошуємо на благодійний DOU Live з Денисом Ювженком. Будемо розбирати Agentic AI, harness engineering, planning, tool use та інші принципи роботи агентних систем. А головне — створимо власного AI-агента на Python наживо! 🎁 Бонус: серед усіх донатів розіграєм…
🖕14❤1👍1
Програма WAWTECH вже на сайті🔥 На сценах — спікери з OpenAI, Netflix, Microsoft, Google, Dropbox, Bolt, Oracle, Agoda та багатьох інших компаній. А ще — творці Elixir та cURL! Вже за місяць — 26–27 листопада у Варшаві, EXPO XXI. Шукайте квитки за посиланням 👉 https://dou.ua/goto/4yoP
😁3❤2🔥2🖕2
Ми вже анонсували 77 спікерів на WAWTech— і ще 20+ попереду 😱 Знайомтеся з новими спікерами: Siim Viidu з Bolt, Jarek Kusmierek з Google, Dmytro Kovalenko з Dropbox та Nicolai Parlog з Oracle. Акція для жінок закінчується вже сьогодні о 23:59! -35% на квитки Regular з промокодом: WOMENINTECH 👉 Квитки тут: https://dou.ua/goto/pZwf
🔥4🥱4🗿1
Привіт усім! 👋 Шукаємо людей, які працюють в IT-компаніях у Польщі, створюють цікаві продукти, розвивають технології та мають круті кейси, якими варто поділитися. Також дуже цікавлять представники банків і фінтех-компаній. Маємо для вас цікаву пропозицію, пов’язану з міжнародною технологічною конференцією WAWTech 2026 у Варшаві 🚀 Якщо впізнали себе або знаєте когось, кому це може бути цікаво, напишіть, будь ласка, …
👍5🤣5🙈1
«Przepraszam, panie i panowie, ale musimy trochę podonatować i ponetworkować» :) На DOU зараз триває благодійний тиждень нетворку, тому ваша задача на сьогодні: — Задонатити від 300 гривень на збір для «АЗОВу» (але чим більше - тим краще); — Заповнити коротеньку форму; — Зачекати до понеділка і отримати свій метч. Реєстрація відкрита до 1 листопада включно, тому не баріться! 💰 Донатити 👉 https://dou.ua/goto/mFaF ☕…
🥴6🔥5👍2💊2🖕2🙈2⚡1❤1
ДахаБраха виступить на WAWTech 2026🔥 27 листопада о 18:00 на Головній сцені! Для жінок зараз діє знижка -35% на квитки Regular до 21 жовтня включно з промокодом: WOMENINTECH 👉 Квитки тут: https://dou.ua/goto/pZwf
❤26🥴13👍1🔥1🤔1🤣1
🇪🇺 Як вести бізнес у Європі дистанційно: можливості для українських підприємців Вихід на ринок ЄС – це нові клієнти, інвестиції та масштаб для бізнесу. Але як зареєструвати компанію в Європі, управляти нею та працювати з фінансами, не виїжджаючи з України? Відповіді – на практичному вебінарі за участі команду e-Residency та експертів ринку. 💡 Для кого: Для засновників бізнесу, які планують вихід на ринок ЄС, керуют…
🥱2😁2❤1
🎓 СПЕЦІАЛЬНА ЦІНА ДЛЯ СТУДЕНТІВ🎓 Купуй квиток на WAWTech by DOU за €45 замість €98! Студентський квиток включає: 👉 Доступ до всіх технічних сцен 👉 Експозону 👉 Партнерські мітапи ❗️Для студентів до 21 року. На вході перевірятимуть студентський квиток. Квитки тут: https://dou.ua/goto/4yoP
🔥6🖕5
Showing the 12 most recent of 50 posts we hold for @dou_polska. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
На яку тему провести Live?
The shares total 123%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 50 most recent posts we hold, published 15 July 2026 to 13 November 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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.
Named by 5 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.
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.
@dou_polska named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 12 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 November 2026 — this entry's latest reading, not the date you are reading this.
“DOU Polska” (@dou_polska), 8,662 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/dou_polska.
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.