Telegram RegisterThe public register of Telegram

Channel

Поросёнок Пётр

@pigPeter

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

4,128subscribers

+6 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001091069533
TypeChannel
Username@pigPeter
Created22 February 2017measured — cross-checked against a third-party dataset (TGDataset)
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/pigPeter

Growth

4,1164,1284,1226 August 2026 — 4,122 subscribers6 August 2026 — 4,122 subscribers9 August 2026 — 4,116 subscribers13 August 2026 — 4,128 subscribers6 August 202613 August 2026
4 measurements spanning 7 days, net +6. 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 4,114–4,130 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 05:184,128+12
9 Aug 2026, 23:324,116-6
6 Aug 2026, 14:004,122no change
6 Aug 2026, 13:524,122first reading

Engagement

17 posts held, back to 25 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 5 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
44.9%
avg views ÷ 4,128 subscribers
Avg views / post
1,850
10 posts measured
Reaction rate
1.64%
reactions ÷ views · ER floor
Posts in window
10
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
WindowRolling 30 days · latest post in window 7 August 2026
Posts held17 (25 June 20267 August 2026)
Views total18,527
Reactions total304
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 12:17 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

Video runtime
1m 06s
Average length
1m 06s

Measured directly from 1 video 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

605 reactions across 17 posts, in 14 distinct kinds. The most used accounts for 41.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥24841.0%
17729.3%
😁6811.2%
👍335.45%
custom 5463186335948878489233.80%
🤯223.64%
👏142.31%
🤔71.16%
👻40.661%
custom 543162888335289528730.496%
💔30.496%
🕊10.165%
😱10.165%
🥰10.165%

Custom emoji. 2 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

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 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 605reactions 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 25 June 2026 to 7 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
3
across the posts below
Posts paid on
3
of 17 we hold a reading for · 18%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @pigPeter. 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 17 most recent posts we hold for this entry, published 25 June 2026 to 7 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

7 Aug 2026, 20:26 UTC937 views9 reactionsread 8 August 2026

Джоел раскидал тут по полочкам куда скатился Hackerone. В целом он всегда был категоричным. Но в этот раз он разложил все как положено. Не забыв и про смену СЕО компании, и потерю идентичности компании. Но большинство из читателей и без Джоеля знало, что HackerOne заносило на поворотах сильно, а аккаунты ричёрчеров банились с балансами и 50к$ и 150к$ 🥲 Приятного чтения. https://blog.teknogeek.io/posts/what-happened

5🤔3👍1

6 Aug 2026, 16:30 UTC≈1,200 views14 reactionsread 8 August 2026

Отрицательный рост в Bug Bounty тоже возможен. Запустив своих Claude, Coded, Grok, Мариус буквально теряет на каждом репорте в среднем по 483$ (в статистику было взято 203 репорта где около 100 сдано на Bugcrowd). Ну и очевидно, что всё это сделано для пиара(считалась не подписочная модель), продвижения личного бренда и для возможности получить ценный опыт. Судя по статистике Bugcrowd - из 99 отчетов идет размеренно

😁112custom 54316288833528952871

3 Aug 2026, 19:09 UTC≈1,720 views59 reactionsread 8 August 2026
Photo

Сперва ребята заскамили меня на двух-трёх критичных репортах. Потом залегли на дно и перестали отвечать по уже отправленным отчётам примерно на два месяца. Причём я видел, что фиксы накатывались, но платить никто не торопился. Я уже было подумал, что они решили придумать причины, чтобы не платить и за оставшиеся десять критов. Но то ли в начале августа бюджеты подъехали, то ли совесть замучила. Как итог — теперь я

🔥43👏97

1 Aug 2026, 12:30 UTC≈1,870 views37 reactions1 Starread 8 August 2026
Photo

Пожалуй самый полезный подгон от организаторов ивента. На заметку другим организаторам 😉 Портативный дисплей на 16’1 и набор с отмычками и прозрачным замком. Малой натренируется и сможет ездить вскрывать квартиры тем кто забыл ключи внутри квартиры😁 PS: пойду теперь добивать свои репорты в “need more info” и попробую слепить что-то годное из оставшегося, что не успел сдать.

👍22🔥114

30 Jul 2026, 13:51 UTC≈1,970 views60 reactionsread 8 August 2026
Photo

Вот и закончился Life Hacking Event 030 от HackerOne (мой второй LHE). Прежде чем принять приглашение, я трижды подумал. Многое меня останавливало в этой истории: реально сложный таргет, крутые приглашенные хакеры, шанс «опозориться». Ну реально, залететь на ивент и показать ноль — это не то, о чём я мечтал. Но в итоге получилось весьма круто. Только надо вынести за скобки тот факт, что я почти две недели по 10–12

35🔥19👏5🕊1

28 Jul 2026, 12:33 UTC≈2,010 views14 reactionsread 8 August 2026

Тут ребята попытались разобрать историю про взлом Hugging Face. И в целом у меня нет сомнений что взлом мог начаться из-за Context Compacting, который привел к Сontex Drift модели и полной смене фокуса на задаче. Максимально полезные 15 минут времени, которые откроют Вам глаза на новые риски.

11🔥3

27 Jul 2026, 08:25 UTC≈1,890 views31 reactionsread 8 August 2026
Photo

Видимо это будет ответ на вопрос о том как я провел лето. И провел я его в весьма сложном Live Hacking Event от HackerOne. Сам Event закончится на этой неделе. И понравилось и не понравилось одновременно. Выводы по ивенту и мои впечатления будут в следующих постах 😉

🔥209😁2

16 Jul 2026, 08:35 UTC≈2,550 views10 reactionsread 8 August 2026
Photo

Недавно я видел статистику что HackerOne имеет чуть более 50 миллионеров хакеров. Сегодня CEO платформы назвала точную цифру - 77. Но самое интересное что некоторые из этих людей даже не находятся в TOP 100 Leaderboard. Еще весьма интересная статистика "инфляции". Скачок в выплатах за эти пол года выше на 25% в сравнении с прошлым. Думаю что в ближайшее время все больше компаний начнет резать бюджеты коррелируя поте

10

15 Jul 2026, 10:11 UTC≈2,290 views23 reactionsread 8 August 2026
Photo

Когда даже триажер платформы на твоей стороне, но команда программы включила заднюю передачу и едет в пропасть. Mediation-тикет создан. Все доказательства представлены. Максимально интересно почитать причины, почему сервисы, которые используются на главном домене через middleware-прокси, внезапно перестали быть частью скоупа. Это же как сказать, что IP-адрес базы данных не в скоупе, а значит, и прямой доступ к этим

custom 5463186335948878489164👍2🥰1

14 Jul 2026, 08:02 UTC≈2,090 views47 reactionsread 8 August 2026

Респект тому кто сделал эмулятор этого великолепия 👾 Олдскулы свело не только мне. Малой отложил в сторону Nintendo switch с фортнайт и пытался разгадать пропажу слона 🤣 https://dos.zone/ru/bratya-piloty-po-sledam-polosatogo-slona/

🔥32👍65😁3😱1

10 Jul 2026, 18:31 UTC≈2,290 views31 reactionsread 8 August 2026
Photo

Трудяга пошуршал вентилятором и помог вытащить пятничный крит. Теперь думаю быть максимальным подонком отправив сейчас (в вечер пятницы), или подержать до понедельника? 🙈

🔥22😁52👻2

9 Jul 2026, 09:50 UTC≈2,300 views67 reactions1 Starread 8 August 2026
Video

Все еще не могу осознать что сходил на их концерт. Если кому-то раньше удалось их увидеть в живую - то я вам завидую. Большую часть жизни у меня не было таких возможностей. В том числе и финансовых. А единство огромного олимпийского стадиона было невероятным. Хочется чтоб весь мир жил в таком единстве. Make love not war 🫶 SOAD 🤟🏻🇦🇲

34🔥27💔3custom 54631863359488784893

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Citation-graph rank

Citation-graph rank — 43,797 of 1,160,990entries 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 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.

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

“Поросёнок Пётр” (@pigPeter), 4,128 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/pigPeter.

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.