Telegram RegisterThe public register of Telegram
Telegram profile photo for Kripto Biztonság

Channel

Kripto Biztonság

@kriptobiztonsag

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

112subscribers

-1 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001557567342
TypeChannel
Username@kriptobiztonsag
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live3 October 2026
Measurements held3
Confirmed unchanged3 times, most recently 3 October 2026
On Telegramt.me/kriptobiztonsag

Topic

Crypto & trading — 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 26 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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

112113112.57 August 2026 — 113 subscribers9 August 2026 — 113 subscribers9 September 2026 — 112 subscribers7 August 20269 September 2026
3 measurements spanning 33 days, net -1. 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 112–113 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 17:01112-1
9 Aug 2026, 06:31113no change
7 Aug 2026, 21:43113first reading

Engagement

19 posts held, back to 23 November 2023 — 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 19 posts for this entry, the most recent from 9 September 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

14 reactions across 6 posts, in 3 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍750.0%
👏642.9%
😁17.14%

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

Measured over the 19 most recent posts we hold, published 23 November 2023 to 9 September 2025, 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

4 Jan 2025, 08:01 UTC225 viewsread 9 August 2026

Bitcoin sörözés ma 18:00-kor: https://www.meetup.com/bitcoinbudapest/events/305400770/?utm_medium=referral&utm_campaign=share-btn_savedevents_share_modal&utm_source=link

3 Jan 2025, 22:00 UTC175 viewsread 9 August 2026

Itt az én crypto airdrop tier listem: https://www.youtube.com/watch?v=GDxpVKSg77w Kíváncsi vagyok, sikerült-e páraknak elcsípni belőlük.

31 Dec 2024, 11:27 UTC169 viewsread 9 August 2026

https://www.facebook.com/kriptobiztonsag/posts/pfbid0eNDSzGy4wDaiGMmgD1Bhmjn4CuQs2dkH3SGD3RBmqRNjApnn6U6CsEn9fbSLfpxKl

9 Dec 2024, 10:51 UTC196 viewsread 9 August 2026

https://wise.com/help/articles/1zFAJivSk9ewlkfPASHUPN/the-fees-for-customers-in-hungary-are-changing

14 Aug 2024, 05:24 UTC287 views2 reactionsread 9 August 2026
Photo

Yield App csőd Emlékeztek még arra az időszakra, amikor naponta mentek csődbe hitelező platformok? A műsor folytatódik, ugyanis a Yield App még így Bitcoin ATH közelében is csődbe tudott menni valahogy. Azt, hogy mennyit buktak a felhasználók, még megtippelni sem tudom, mert a haszontalan közleményükből ez (sem) derül ki. Remélem közülünk senkinek nem volt kriptója náluk ✌️

👍2

18 Jul 2024, 20:52 UTC237 viewsread 9 August 2026

A Fractal ID KYC cégnél adatszivárgás történt. https://twitter.com/LefterisJP/status/1813606284077539345

10 May 2024, 14:32 UTC267 views2 reactionsread 9 August 2026
Photo

Találkozzunk a Blockchain Budapest konferencián Május 14-én előadok a B-day-en: a Bitcoin gyengeségeivel fogom riogatni a közönséget, főként az 51% támadásról és a kripto államosításáról lesz szó. Ha jössz a konferenciára (vagy akár csak az afterra), gyere oda hozzám bátran, találkozzunk végre élőben is!

👏2

27 Apr 2024, 15:38 UTC312 views0 reactionsread 9 August 2026
Photo

A leghaszontalanabb blokkláncokról írt a Forbes: Eredeti link: https://www.forbes.com/sites/stevenehrlich/2024/03/27/the-rise-of-cryptos-billion-dollar-zombies/ Ingyenes: https://www.forbesindia.com/article/billionaires/cryptos-billiondollar-zombies/92783/1

22 Jan 2024, 09:19 UTC662 viewsread 9 August 2026

A Trezortól 66 ezer ügyfél adatait lopták el A crypto-hardvertárcákat gyártó Trezor megerősítette, hogy január 17-én jogosulatlan hozzáférés történt egy support portáljukon. Az incidens során, a Trezor ügyfélszolgálattal 2021 decembere óta kapcsolatba lépő felhasználók adataihoz hozzáférhettek, valószínűleg olyan 66 000 ügyfél érintett az ügyben. A vállalat közölte, hogy mind a 66 ezer kontaktot e-mailben értesítet…

11 Jan 2024, 04:12 UTC224 views1 reactionsread 9 August 2026

🤥 Ez tehát azt jelenti, hogy a JPMorgan - aminek az igazgatója szerint a Bitcoin csak terrorizmusra és szexkereskedelemre használható - részt vesz a Bitcoin ETF létrehozásában. Érdekesség, hogy négy hónappal ezelőtt pont a JPMorgant büntették meg szexkereskedelemben való részvétel miatt: https://www.pbs.org/newshour/world/jpmorgan-to-pay-75-million-for-role-in-epstein-sex-trafficking-operation

😁1

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

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

“Kripto Biztonság” (@kriptobiztonsag), 112 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/kriptobiztonsag.

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.