Telegram RegisterThe public register of Telegram

Channel

DOU | QA

@dou_qa

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry

12,619subscribers

-16 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001658444532
TypeChannel
Username@dou_qa
DescriptionВсе про тестування від QA-спільноти DOU: https://dou.ua/goto/QA • технічні статті та блоги • войсчати • професійні обговорення • QA події • QA вакансії З побажаннями, ідеями чи скаргами пишіть – pt@dou.ua 👈
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/dou_qa

Growth

12,61812,63512,626.56 August 2026 — 12,635 subscribers7 August 2026 — 12,632 subscribers8 August 2026 — 12,626 subscribers9 August 2026 — 12,622 subscribers10 August 2026 — 12,618 subscribers11 August 2026 — 12,622 subscribers12 August 2026 — 12,619 subscribers12,6196 August 202612 August 2026
7 measurements spanning 6 days, net -16. 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 12,615–12,638 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 11:4712,619-3
11 Aug 2026, 12:4512,622+4
10 Aug 2026, 11:3212,618-4
9 Aug 2026, 14:1612,622-4
8 Aug 2026, 16:1512,626-6
7 Aug 2026, 15:4412,632-3
6 Aug 2026, 21:0312,635first reading

Engagement

28 posts held, back to 20 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 16 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
29.9%
avg views ÷ 12,619 subscribers
Avg views / post
3,780
28 posts measured
Reaction rate
0.935%
reactions ÷ views · ER floor
Posts in window
28
of 28 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 held28 (20 July 202611 August 2026)
Views total105,710
Reactions total988
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 03:13 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
1,570
Videos
63
Links
2,030

Lifetime counters from Telegram’s own channel header, read 13 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.

Reaction mix

988 reactions across 28 posts, in 17 distinct kinds. The most used accounts for 26.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤡25926.2%
😁18318.5%
15215.4%
🤣10810.9%
😭989.92%
👍696.98%
🔥373.74%
🤮373.74%
🫡111.11%
🐳80.81%
👀70.709%
😢60.607%
🥰60.607%
👎20.202%
🤬20.202%
🤷‍♂20.202%
🤔10.101%

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

Measured over the 28 most recent posts we hold, published 20 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.

Recent posts

11 Aug 2026, 15:00 UTC≈2,060 views20 reactionsread 13 August 2026
Photo

Користувач за пів року соло-розробки витратив десятки годин на баги, які в підсумку виявлялись дрібницею. На форумі він розбирає три реальні баги та показує, як AI допомагає шукати причини проблем, перевіряти гіпотези та звужувати зону пошуку. 👉 https://dou.ua/goto/ZZC7

👀6🤣6🤡4👍3👎1

11 Aug 2026, 12:00 UTC≈2,420 views10 reactionsread 13 August 2026
Photo

Middle Manual QA в JATAPP Київ, за кордоном, віддалено 👉 https://dou.ua/goto/JeVs General\Automation QA Engineer в Bank Pivdenny Київ, Одеса, віддалено 👉 https://dou.ua/goto/qmwF QA Engineer (Львів) в VoIPTime Львів 👉 https://dou.ua/goto/rCoG Embedded QA Lead [R&D] в Vyriy, $1800–4500 Київ 👉 https://dou.ua/goto/gC3n Middle+ QA Engineer в Empat Київ, за кордоном, віддалено 👉 https://dou.ua/goto/cV9R

👍7🤮3

11 Aug 2026, 08:01 UTC≈2,690 views45 reactionsread 13 August 2026
Photo

QA в DefTech заробляють дещо більше, ніж в ІТ, але різниця поки незначна – $150 Результати зарплатного опитування щодо фахівців, задіяних у DefTech 👉 https://dou.ua/goto/oSKO

😁24🤡1110

10 Aug 2026, 16:00 UTC≈2,790 views20 reactionsread 13 August 2026
Photo

Коли обираєте нову компанію, що для вас має найбільше значення? Зарплата, цікаві проєкти, команда, гнучкий графік чи, можливо, щось зовсім інше? Поділіться своєю думкою в опитуванні 👉 https://dou.ua/goto/yxgi

🤡11😁71🤔1

9 Aug 2026, 11:41 UTC≈2,990 views43 reactionsread 13 August 2026
Poll

Який механізм найкраще мав би запобігти такій ситуації?

  1. A) Rate limiting16%
  2. B) Idempotency key62%
  3. C) Caching6%
  4. D) Retry з exponential backoff15%

Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.

🤡328👍3

8 Aug 2026, 10:00 UTC≈3,380 views75 reactionsread 13 August 2026
Photo

Ні, ну а що 😅 Джерело

🤣47😁15🔥7🤡4👍2

7 Aug 2026, 14:00 UTC≈3,800 views47 reactionsread 13 August 2026
Photo

QA-інженер із сьома роками досвіду мобілізувався та шукає напрямок, де його навички працюватимуть на армію. Якщо переводились після мобілізації або знаєте підрозділи, де потрібні тестувальники - розкажіть на форумі. 👉 https://dou.ua/goto/WY8t

21😁16😢4👍3🤮3

7 Aug 2026, 08:00 UTC≈3,640 views26 reactionsread 13 August 2026
Photo

Актуальні зарплати General QA Повні результати літнього зарплатного опитування для тестувальників 👉🏻 https://dou.ua/goto/7LC8

🤡10😁8👍5😢21

6 Aug 2026, 14:33 UTC≈3,370 views28 reactionsread 13 August 2026
Photo

Серпень, спека, а ти лежиш посеред кукурудзяного поля, вдаєш, що полеш бур'яни, та мрієш піти до місцевої річки, або ще краще - гайнути на велосипеді до ставка у сусідньому селі. Згадуємо на форумі про село та літо. А вас відправляли в дитинстві на канікули в село? 👉 https://dou.ua/goto/gKqc

20😭5🤬2👍1

5 Aug 2026, 15:00 UTC≈3,350 views13 reactionsread 13 August 2026
Photo

У якій українській IT-компанії ви мрієте працювати? 💭 Вже четвертий рік поспіль DOU запускає масштабне дослідження Employer Brand Research. Ми хочемо дізнатися, що українські фахівці насправді думають про IT-компанії, чиї бренди сприймаються найсильнішими та які чинники сьогодні є вирішальними під час вибору роботодавця. Як завжди, схема проста: ▫️ З вас — 5 хвилин на заповнення анкети ▫️ З нас — прозора та детальн

🤡111🤮1

5 Aug 2026, 12:00 UTC≈4,130 views102 reactionsread 13 August 2026
Photo

Конкуренція для QA в липні зросла до 92 відгуків на одну вакансію

😭86🐳8🤡4🤣3😁1

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

Polls

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.

9 Aug 2026, 11:41 UTCAnonymous Quiz1,090 voters approx.

Який механізм найкраще мав би запобігти такій ситуації?

  1. A) Rate limiting16%
  2. B) Idempotency key62%
  3. C) Caching6%
  4. D) Retry з exponential backoff15%

Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is 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 28 most recent posts we hold, published 20 July 2026 to 11 August 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.

Citation-graph rank

Citation-graph rank — 117,099 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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 6 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.

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

“DOU | QA” (@dou_qa), 12,619 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/dou_qa.

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.