Telegram RegisterThe public register of Telegram
Telegram profile photo for Bounty On Coffee

Channel

Bounty On Coffee

@BountyOnCoffee

On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Citations · Telegram's recommendations · Cite this entry

4,763subscribers

+65 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001523043386
TypeChannel
Username@BountyOnCoffee
Created13 February 2022measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded7 August 2026
Last confirmed live18 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/BountyOnCoffee

Topic

Hacking & security — 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 13 September 2026 and assigned it the closest of 31 fixed categories, at 57% 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 why it has no browse page of its own yet.

Growth

4,6984,7634,730.57 August 2026 — 4,698 subscribers7 August 2026 — 4,699 subscribers10 August 2026 — 4,703 subscribers14 August 2026 — 4,709 subscribers17 August 2026 — 4,720 subscribers20 August 2026 — 4,735 subscribers23 August 2026 — 4,747 subscribers26 August 2026 — 4,739 subscribers29 August 2026 — 4,734 subscribers2 September 2026 — 4,732 subscribers5 September 2026 — 4,736 subscribers10 September 2026 — 4,752 subscribers14 September 2026 — 4,757 subscribers18 September 2026 — 4,763 subscribers7 August 202618 September 2026
14 measurements spanning 43 days, net +65. 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,688–4,773 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 20:544,763+6
14 Sept 2026, 06:404,757+5
10 Sept 2026, 20:384,752+16
5 Sept 2026, 14:214,736+4
2 Sept 2026, 02:024,732-2
29 Aug 2026, 18:254,734-5
26 Aug 2026, 23:574,739-8
23 Aug 2026, 20:454,747+12
20 Aug 2026, 07:344,735+15
17 Aug 2026, 15:274,720+11
14 Aug 2026, 05:364,709+6
10 Aug 2026, 17:124,703+4
7 Aug 2026, 12:424,699+1
7 Aug 2026, 06:464,698first reading

Engagement

13 posts held, back to 19 April 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 7 pages of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 13 posts for this entry, the most recent from 20 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

446 reactions across 13 posts, in 5 distinct kinds. The most used accounts for 44.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥20044.8%
😁14332.1%
👍9020.2%
👏71.57%
👎61.35%

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

Measured over the 13 most recent posts we hold, published 19 April 2026 to 20 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.

Telegram Stars

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

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @BountyOnCoffee. 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 13 most recent posts we hold for this entry, published 19 April 2026 to 20 July 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

20 Jul 2026, 16:48 UTC≈1,670 views36 reactionsread 12 August 2026

1. Увидел пост 2. Обрадовался, что теперь логику норм будут оценивать 3. Репостнул 4. Через 3 часа сдал 2 крита 5. Понял, что в целом то выплаты хорошенько так снизили 6. Через 19 дней получил выплату 7. Если бы сдал на 4 часа раньше, получил бы на 600к больше ( не учитывая Bounty Pass ) Возвращаясь к сообщению от 1 июля, получается хорошо, но только для VK 😁🗿

😁36

1 Jul 2026, 16:47 UTC≈2,750 views16 reactionsread 12 August 2026
Forwarded from @vk_securityPhoto

🤩 Максимальные выплаты — за реальную защищенность пользователей Фокусируемся на том, что действительно важно — на приватности и безопасности пользовательских данных. 🔹С 1 июля мы меняем правила программы багбаунти: теперь не важно, какая именно бага найдена, важно — какой импакт она несет. Любые узявимости, которые позволяют получить доступ к данным пользователей будут оцениваться по новой шкале. 🔹 Например, в наш

🔥11😁4👎1

1 Jul 2026, 16:47 UTC≈2,570 views4 reactionsread 12 August 2026

А вот так вот уже хорошо

🔥4

26 Jun 2026, 11:39 UTC≈3,280 views30 reactionsread 12 August 2026
Photo

Несколько дней назад сдавал довольно критический недостаток, в ходе эксплуатации с моей стороны был деструктив, из-за чего один из сервисов прилёг. После нескольких дней изучения инцидента было вынесено решение ничего не выплачивать мне. По правилам багбаунти вендор имеет на это полное право! Но правильно ли так делать сразу при первом таком косяке? Учитывая, что за последние пару лет приносил много критов и хаев и

🔥21😁9

1 Jun 2026, 09:16 UTC≈3,440 views63 reactionsread 12 August 2026
Forwarded from @pigPeter

Один из «отцов» русскоязычного Bug Bounty залетел на подкаст и поделился своим опытом, подходами и стратегиями поиска уязвимостей. Поговорили про выбор целей, участие в hacking events, состояние bug bounty в СНГ и то, что на самом деле помогает находить хорошие баги годами, а не случайно время от времени. Уверен, что выпуск будет интересен и полезен как новичкам, так и опытным исследователям. Приятного просмотра 😉

🔥58😁5

22 May 2026, 20:43 UTC≈3,490 views39 reactionsread 12 August 2026
Photo

Альфа забыл мыло положить в мерч 😁

😁39

22 May 2026, 20:42 UTC≈2,620 views19 reactionsread 12 August 2026
Forwarded from @bizone_bugbountyPhoto

🐞 Мы официально подвели итоги, вот наш топ-10: 1️⃣thxStuck 2️⃣r0hack 3️⃣adsec2s 4️⃣rolegiv 5️⃣DiZZxExZuperi 6️⃣ghosthacker 7️⃣godfuzz3r 8️⃣zero-0x00 9️⃣K1nder 1️⃣0️⃣savAnna Поздравляем ребят и отправляемся все вместе отмечать успехи нашего сообщества! Спасибо всем участникам, друзьям сообщества и вендорам за ивент. Фото и видео с мероприятия выложим чуть позже. Stay tuned 💙

🔥14😁3👍2

19 May 2026, 10:40 UTC≈2,830 views46 reactionsread 12 August 2026

Если недостатка нет, в чем проблема раскрыть ? Репорт же отклонен

👍40🔥4👎2

19 May 2026, 10:37 UTC≈3,070 views33 reactionsread 12 August 2026

@standoff_365 что скажете ?

👍31👎2

19 May 2026, 10:36 UTC≈3,000 views68 reactionsread 12 August 2026
Forwarded from @hackadvisor

Positive Technologies · Standoff365 👎 Not recommend · @d3n13d «Пофиксили уязвимость, чтобы не платить баунти? Три месяца ждал разбор простейшего репорта по отравлению кеша (взяли в работу через пару дней, но потом ушли в игнор, допинал через поддержку с 3 раза). По итогу уязвимость они пофиксили (есть два скринкаста в репорте - видно, что поведение изменилось; есть скринкаст, что раньше стреляло), а в репорте отве

😁46👍14👏7👎1

1 May 2026, 16:40 UTC≈3,550 views29 reactionsread 12 August 2026
Photo

В самом первом Hacks (не прозвали 😒) и в Ahmedabad не участвовал https://hacks.standoff365.com/

🔥29

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

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 1 registered channel — 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.

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.

Appears in Telegram’s recommendations for other channels

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.

The Bug Bounty Hunter
@thebugbountyhunter · 50,736
Telegram ranks this channel #48 of 60 here — alongside 59 others — read 25 August 2026
Life-Hack - Хакер
@haccking · 63,203
Telegram ranks this channel #61 of 85 here — alongside 84 others — read 21 August 2026
OSINT mindset
@osint_mindset · 64,564
Telegram ranks this channel #63 of 83 here — alongside 82 others — read 21 August 2026
Codeby
@codeby_sec · 36,985
Telegram ranks this channel #67 of 76 here — alongside 75 others — read 1 September 2026
Хакер — Xakep.RU
@xakep_ru · 39,506
Telegram ranks this channel #73 of 83 here — alongside 82 others — read 30 August 2026
Пакет Безопасности
@package_security · 33,106
Telegram ranks this channel #74 of 82 here — alongside 81 others — read 4 September 2026
Positive Technologies
@Positive_Technologies · 28,968
Telegram ranks this channel #83 of 87 here — alongside 86 others — read 9 September 2026
Positive Hack Days Media
@positivehackmedia · 30,694
Telegram ranks this channel #87 of 88 here — alongside 87 others — read 6 September 2026

This channel appears in 8 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Bounty On Coffee” (@BountyOnCoffee), 4,763 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/BountyOnCoffee.

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.