Telegram RegisterThe public register of Telegram
Telegram profile photo for Buna Byte

Channel

Buna Byte

@bunabytecs

On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry

1,121subscribers

+73 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1002081451131
TypeChannel
Username@bunabytecs
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live17 September 2026
Measurements held13
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/bunabytecs

Topic

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 18 September 2026 and assigned it the closest of 31 fixed categories, at 56% 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

1,0481,1211,084.59 August 2026 — 1,048 subscribers10 August 2026 — 1,050 subscribers12 August 2026 — 1,053 subscribers15 August 2026 — 1,059 subscribers18 August 2026 — 1,065 subscribers22 August 2026 — 1,072 subscribers25 August 2026 — 1,080 subscribers28 August 2026 — 1,091 subscribers31 August 2026 — 1,098 subscribers3 September 2026 — 1,105 subscribers9 September 2026 — 1,112 subscribers13 September 2026 — 1,114 subscribers17 September 2026 — 1,121 subscribers9 August 202617 September 2026
13 measurements spanning 39 days, net +73. 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 1,037–1,132 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 08:551,121+7
13 Sept 2026, 04:381,114+2
9 Sept 2026, 01:351,112+7
3 Sept 2026, 23:381,105+7
31 Aug 2026, 10:271,098+7
28 Aug 2026, 17:171,091+11
25 Aug 2026, 10:071,080+8
22 Aug 2026, 20:031,072+7
18 Aug 2026, 23:331,065+6
15 Aug 2026, 19:371,059+6
12 Aug 2026, 13:541,053+3
10 Aug 2026, 00:011,050+2
9 Aug 2026, 15:461,048first reading

Engagement

17 posts held, back to 16 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 1 page 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 17 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

130 reactions across 14 posts, in 10 distinct kinds. The most used accounts for 38.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥5038.5%
❤2620.0%
👍1914.6%
✍1310.0%
⚡86.15%
🏆53.85%
💔43.08%
❤‍🔥21.54%
🥰21.54%
💊10.769%

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 14 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 130 reactions 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 16 July 2026 to 9 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
5
across the posts below
Posts paid on
2
of 14 we hold a reading for · 14%
Most on one post
3
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @bunabytecs. 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 16 July 2026 to 9 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

9 Aug 2026, 15:42 UTC11 views1 reactionsread 9 August 2026
Photo

We’re giving Buna Byte CTF a new identity. 🇪🇹 Today, we’re introducing the new Buna Byte CTF Ranking System. Instead of the usual Bronze, Silver, Gold, and Diamond ranks, players will rise through a progression inspired by Ethiopian historical military titles. From: ጓንዳሪ — Gwandari to አሥር አለቃ — Asir Aleqa ሃምሳ አለቃ — Hamsa Aleqa ሻለቃ — Shalaqa ፊታውራሪ — Fitawrari ደጃዝማች — Dejazmatch and ultimately… ራስ — Ra…

👍1

31 Jul 2026, 08:28 UTC322 views9 reactionsread 9 August 2026
Photo

✨ I think you guys loved Afya mind, the ML Security challenge. 😊 @bunabytecs

❤4🏆2🔥2👍1

28 Jul 2026, 15:41 UTC339 views8 reactionsread 9 August 2026
Photo

Recognition Roulette Bypassing blacklist filters to exploit SSTI and extract environment variables in the Recognition Roulette web challenge. Buna Byte | bunabyte​.com • Jul 28, 2026

🔥3✍2❤‍🔥2💊1

Signed RSS.app

27 Jul 2026, 11:29 UTC397 views12 reactionsread 9 August 2026
Photo

Eight days into the EACASummit CTF Archive, not a single team has completed all 19 challenges. The closest competitor is only 2 flags away. Now the challenge is yours. The archived CTF remains available for 22/30 days after the launch. Break the final challenge. Claim all 19 flags. Earn the bragging rights that no one else has. @bunabytecs

🔥9❤1👍1🥰1

23 Jul 2026, 08:43 UTC450 views8 reactionsread 9 August 2026
Photo

If you see this kind of page on the lab based challenges, give it time to initiate (5 to 10 sec) and then ctr + r @bunabytecs

✍5❤2🏆1

23 Jul 2026, 04:34 UTC414 views9 reactionsread 9 August 2026

Additional lab based challenges are Available at the live ctf event. @bunabytecs

🔥8🥰1

20 Jul 2026, 17:25 UTC441 views12 reactionsread 9 August 2026

Now file based challenges work. we are working on the lab challenges, will update you as soon as they also work.

👍10❤1🏆1

20 Jul 2026, 16:21 UTC430 views7 reactionsread 9 August 2026

Sorry for the technical glitch we are on it. Thanks for understanding.

❤6🔥1

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

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.

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

“Buna Byte” (@bunabytecs), 1,121 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/bunabytecs.

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.