BIZTRAC BETA
Construction of residential and non-residential buildings

BNYTT AS

Org. no. 912829065 Limited company (AS) Bergen Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 554,000
Operating profit NOK 11,000
Equity NOK −133,000
Incorporated 2013
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−133k kr).

BNYTT AS is registered as a limited company in Bergen, Vestland with organisation number 912829065. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Å levere tjenester innen tømrerviksomhet. I tillegg til det utfører selskapet distribusjon av avis, og deltagelse i andre beslektede virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 554,000 in revenue and NOK 11,000 in operating profit.

Key figures · 2024

Revenue
NOK 554,000
Operating profit
NOK 11,000
Equity
NOK −133,000
Est. value
NOK 78,000

Financial health · 2024

Liquidity
0.53
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-88.2%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BNYTT AS?

PER MAGNE BYSHEIM
BNYTT AS
NOK 554,000 rev. · NOK 11,000 profit

BNYTT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BNYTT AS

Who owns BNYTT AS?

PER MAGNE BYSHEIM is the largest registered owner, with 100.0%.

What is the revenue of BNYTT AS?

BNYTT AS had revenue of NOK 554,000 in 2024.

Who is the general manager of BNYTT AS?

Maria Hunt Eilertsen Bysheim is registered as general manager of BNYTT AS.

Where is BNYTT AS based?

BNYTT AS has its business address in Rådal.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.