BIZTRAC BETA
Construction of residential and non-residential buildings

MYLSBRÅTEN & BERG BYGG AS

Org. no. 998482984 Limited company (AS) Lunner Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 7.9m
Operating profit NOK 244,000
Equity NOK 2.0m
Incorporated 2012
Share capital NOK 30,000

MYLSBRÅTEN & BERG BYGG AS is registered as a limited company in Lunner, Akershus with organisation number 998482984. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Oppføring og rehabilitering av bygg samt dertil naturlig tilhørende oppgaver.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.9m in revenue and NOK 244,000 in operating profit.

Key figures · 2025

Revenue
NOK 7.9m
Operating profit
NOK 244,000
Equity
NOK 2.0m
Est. value
NOK 1.9m

Financial health · 2025

Liquidity
2.58
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
62.0%
Very good
Equity as a share of total capital

Who owns MYLSBRÅTEN & BERG BYGG AS?

JOSTEIN MYLSBRÅTEN
MYLSBRÅTEN & BERG BYGG AS
NOK 7.9m rev. · NOK 244,000 profit

MYLSBRÅTEN & BERG BYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MYLSBRÅTEN & BERG BYGG AS

Who owns MYLSBRÅTEN & BERG BYGG AS?

JOSTEIN MYLSBRÅTEN is the largest registered owner, with 50.0%.

What is the revenue of MYLSBRÅTEN & BERG BYGG AS?

MYLSBRÅTEN & BERG BYGG AS had revenue of NOK 7.9m in 2025.

Who is the general manager of MYLSBRÅTEN & BERG BYGG AS?

Jostein Mylsbråten is registered as general manager of MYLSBRÅTEN & BERG BYGG AS.

Where is MYLSBRÅTEN & BERG BYGG AS based?

MYLSBRÅTEN & BERG BYGG AS has its business address in Grua.

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.