2 measurements spanning 2 days. 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 35–37 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
10 Aug 2026, 23:01
36
no change
8 Aug 2026, 21:00
36
first reading
Engagement
17 posts held, back to 31 December 2025 — 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 pageof Telegram’s post history, 20 posts per page.
ERR · 30 days
180.6%
avg views ÷ 36 subscribers
Avg views / post
65.0
1 post measured
Reaction rate
6.15%
reactions ÷ views · ER floor
Posts in window
1
of 17 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
Window
Rolling 30 days · latest post in window 31 July 2026
Posts held
17 (31 December 2025 – 31 July 2026)
Views total
65
Reactions total
4
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
10 Aug 2026, 23:01 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
19
Videos
2
Links
12
Lifetime counters from Telegram’s own channel header, read 10 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Reaction mix
60 reactions across 14 posts, in 4 distinct kinds. The most used accounts for 56.7% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
34
56.7%
🔥
20
33.3%
👍
5
8.33%
🤝
1
1.67%
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 15 of the 17 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 60reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 31 December 2025 to 31 July 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.
⚡ Privacy Kitchen / Москва.
Есть вещи, которые лучше не менять. Например, традицию собираться за большим столом.
21 августа в Москве мы соберемся на камерный ужин, вдохновлённый кухней Испании и Латинской Америки.
В этот вечер обсудим, как сегодня строится privacy-функция в компаниях:
🟡когда одному DPO уже недостаточно работать в одиночку;
🟡как формировать команду и получать поддержку бизнеса;
🟡где проходит грани…
⚡ Privacy Kitchen. Петербург приезжает в Москву.
Есть вещи, которые лучше не менять. Например, традицию собираться за большим столом.
На один вечер Privacy Kitchen переезжает в Москву. С той же атмосферой, тем же подходом и новым ужином, вдохновлённым Латинской Америкой.
📅 21 августа
🕖 19:00–22:30
👇 О чём поговорим?
▶️ Как из одного DPO вырастает полноценная privacy-функция: когда приходит время перестать делать…
🔥 LAST CALL | Privacy-дебаты в Петербурге
РЕГИСТРАЦИЯ
Остается неделя до самых приватных и самых вежливых дебатов Denuo&RPPA в Петербурге.
🌟 О том, нужно ли DPO разбираться в технологических аспектах, может ли privacy-команда блокировать релиз продукта, нужны ли вообще privacy-консультанты и о многом-многом другом будут спорить:
🟡Кирилл Зюбанов, CDPO Wildberries&Russ, Со-основатель ПРОПД, автор ПЕРСОНЕМОВ, создат…
Вчера Privacy Kitchen собрала гостей за одним столом - и получилось именно так, как мы задумывали: камерно, спокойно, профессионально и по-человечески.
Спасибо всем, кто пришёл, поддержал нашу идею и разделил с нами этот вечер. Было очень приятно видеть, как люди обсуждают утечки персональных данных, спорят о роли DPO и ИБ, обмениваются опытом и продолжают разговоры далеко за пределами основной программы.
Отдельно …
⚡ Privacy Kitchen зовёт в гости: вечер у DPO
✨ Иногда самые важные разговоры про privacy случаются не на конференциях, а вечером - на кухне, с бокалом вина и людьми, которым не нужно объяснять, что такое “инцидент в пятницу в 18:47”.
👇 Что будет?
▶️ Соберём за одним столом юристов, DPO и специалистов по ИБ, чтобы обсудить утечки персональных данных без скучных презентаций и официоза
▶️ Поговорим о том, как расслед…
⚡ RPPA.pro приглашает тебя на Неделю знаний: усиление DPO
18.05 10:00 Проверки РКН — из первых уст
👇 О чём это мероприятие?
▶️ Всегда ли мероприятия РКН несут в себе угрозу применения санкций к оператору?
▶️ Как РКН осуществляет надзор за операторским сообществом в условиях моратория на плановые проверки: чем ограничен регулятор, а в чем его полномочия усилились?
🔥 Кто проведёт вебинар?
Светлана Чернова — DPO в…
😎RPPA.pro всегда под рукой!
1️⃣Наш официальный канал в Яндекс: дайджест за неделю + обсуждения
2️⃣Наша бесплатная библиотека со всеми тезисами, материалами, календарем прошедших мероприятий
3️⃣Уже всем знакомый сайт сообщества - RPPA.pro
4️⃣Все образовательные продукты - RPPAedu.pro
5️⃣А если еще не получаешь от нас рассылку - вступай в RPPA.pro!
С любовью и солнышком даже во время грозы!
Что могло бы сделать мероприятие Privacy Kitchen более удобным и ценным для вас?
(опрос анонимный, можно выбрать один или несколько вариантов)
Более удобная дата или время проведения13%
Более подробное раскрытие программы и тем заранее50%
Углублённая практическая часть (кейсы, разборы, прикладные инструменты)38%
Более комфортная стоимость участия25%
Я не видел(а) анонс мероприятия50%
Другое (будем рады вашему комментарию)13%
The shares total 189%, 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.
Уважаемые гости Privacy Kitchen!
Спасибо за ваш интерес к нашему мероприятию 🙏
К сожалению, мы вынуждены перенести встречу, запланированную на 27 марта, на более поздний срок в связи с организационными обстоятельствами.
Нам важно, чтобы мероприятие прошло в максимально комфортной и насыщенной атмосфере, с возможностью полноценного общения, обмена опытом и практической пользы для всех участников. Поэтому мы приняли …
Коллеги, напоминаем, что встречаемся 27 марта!
🍝 Готовим лазанью на мастер-классе с Дмитрием Величко (DPO Евросиб)
🔐 Обсуждаем практику и риски с Александром Поповым (DPO) и Евгением Буйволовым (Deputy Head of SOC в ITGSecurity):
— ответственность при утечках ПДн
— проверки Роскомнадзора
— какие меры реально снижают риски.
🎼 Винил, живая атмосфера, профессиональное общение и Polaroid-фото на память.
📅 27 марта в …
Showing the 12 most recent of 17 posts we hold for @privacy_kitchen_spb. 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.
Что могло бы сделать мероприятие Privacy Kitchen более удобным и ценным для вас?
(опрос анонимный, можно выбрать один или несколько вариантов)
Более удобная дата или время проведения13%
Более подробное раскрытие программы и тем заранее50%
Углублённая практическая часть (кейсы, разборы, прикладные инструменты)38%
Более комфортная стоимость участия25%
Я не видел(а) анонс мероприятия50%
Другое (будем рады вашему комментарию)13%
The shares total 189%, 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 17 most recent posts we hold, published 31 December 2025 to 31 July 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 — 1,067,785 of 1,350,102entries 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
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
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 10 August 2026 — this
entry's latest reading, not the date you are reading this.
“Privacy Kitchen” (@privacy_kitchen_spb), 36 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/privacy_kitchen_spb.
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.