Telegram RegisterThe public register of Telegram
Telegram profile photo for Noise Security Bit

Channel

Noise Security Bit

@N0iSeBit

On this record: Growth · Engagement · Posts · Polls · Citations · Cite this entry

611subscribers

-1 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001007066598
TypeChannel
Username@N0iSeBit
Created4 October 2015measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live15 August 2026
Measurements held3
Confirmed unchanged2 times, most recently 15 August 2026
On Telegramt.me/N0iSeBit

Growth

611612611.56 Aug 2026, 14:36 — 612 subscribers6 Aug 2026, 17:46 — 612 subscribers7 Aug 2026, 10:05 — 611 subscribers6 Aug 2026, 14:367 Aug 2026, 10:05
3 measurements taken within a single day, 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 611–612 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 10:05611-1
6 Aug 2026, 17:46612no change
6 Aug 2026, 14:36612first reading

Engagement

19 posts held, back to 2 March 2021the 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.

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 26 May 2021. An engagement rate over an empty window would be a number about nothing.

Recent posts

25 May 2021, 03:00 UTC≈3,270 viewsread 6 August 2026

🔥🤘🍿 https://securityconversations.com/episode/alex-matrosov-on-the-state-of-security-at-the-firmware-layer/

Signed AM

17 May 2021, 02:19 UTC≈2,430 viewsread 6 August 2026

Первый эксперимент с голосовым чатом прошел отлично, получилось очень интерактивно и бодро. Спасибо @dukeBarman @dump_stack @xairy @nabdullin @socialengineer за то что поддержали дискуссию! 🤟🔥🍻

Signed AM

10 May 2021, 04:30 UTC≈2,470 viewsread 6 August 2026
Photo

Сделать дешевый микроконтроллер безопасным довольно тяжело по многим причинам. Вот и Apple со своим AirTag тоже не осилил 😈

Signed AM

24 Apr 2021, 18:11 UTC≈2,330 viewsread 6 August 2026
Photo

Phenoelit - Hacker Hacker https://www.youtube.com/watch?v=IZYQILfxHiw

Signed AM

24 Apr 2021, 18:01 UTC≈1,790 viewsread 6 August 2026

В возрасте 42-х лет ушел из жизни Dan Kaminsky, известный ресечер продемонстрировавший миру уязвимости в DNS и сети Интернет в целом. Твои исследования останутся в нашей памяти навсегда. R.I.P. my friend!

Signed AM

23 Apr 2021, 13:02 UTC≈1,530 viewsread 6 August 2026
Forwarded from @zeronightsPhoto

Юбилейные события отправляют нас к истокам. Когда-то в истории ZeroNights воркшопы были традиционными активностями, так почему бы нам не вернуть эту традицию и не включить их в программу? Мы принимаем заявки на проведение практических воркшопов, где вы сможете поделиться своми идеями и наработками! Подать заявку и задать вопросы по проведению вы можете по почте [email protected]. В письме укажите время прод

Signed dukeBarman

22 Apr 2021, 00:38 UTC≈1,120 viewsread 6 August 2026
Forwarded from @zeronightsPhoto

Известны первые утвержденные доклады ZN 2021! Рассказываем о тех, которые войдут в основную программу. 1. Эксплуатация checkm8 с неизвестным SecureROM на примере чипа T2 Алексей Коврижных покажет продвинутый способ дампинга прошивки, который будет работать на устройствах с WXN, на примере T2. 2. LPE в Ring -3 / Intel ME Дмитрий Турченков раскроет тайны эксплуатации багов в системном компоненте ME через механизм IPC

Signed AM

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

22 Mar 2021, 21:00 UTCFinal Results153 voters

Интересен был бы регулярный голосовой чат на нашем канале?

  1. звучит интригующе 🍿53%
  2. что за дичь, в топку 🤦‍♂️47%

Shares as published. No per-option vote count is published by Telegram, so none is 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 19 most recent posts we hold, published 2 March 2021 to 26 May 2021. 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.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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.

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

“Noise Security Bit” (@N0iSeBit), 611 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/N0iSeBit.

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.