biztrac. BETA
COMPANY REGISTER PROFILE
914154936 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Business and other management consultancy activities

MYRLI MASKIN OG EIENDOM AS

Org. no. 914154936 Limited company (AS) Nes Incorporated 2014 Active
Operating profit NOK −7,000
Equity NOK −26,000
Incorporated 2014
Share capital NOK 30,000

Signals

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

MYRLI MASKIN OG EIENDOM AS is registered as a limited company in Nes, Akershus with organisation number 914154936. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Forretnings- og eiendomsutvikling, og alt som står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −7,000
▲ +11 %
Equity
NOK −26,000
▼ −38 %

Financial health · 2025

Liquidity
0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-24.3%
Weak
Equity as a share of total capital

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

Who owns MYRLI MASKIN OG EIENDOM AS?

MYRLI MASKIN OG EIENDOM AS has 5 registered shareholders:

All shareholders and roles →

Which companies does MYRLI MASKIN OG EIENDOM AS own?

MYRLI MASKIN OG EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MYRLI MASKIN OG EIENDOM AS

Who owns MYRLI MASKIN OG EIENDOM AS?

Ole Petter Johansen is the largest registered owner, with 20.0%.

Who is the general manager of MYRLI MASKIN OG EIENDOM AS?

Barbro Brenna is registered as general manager of MYRLI MASKIN OG EIENDOM AS.

Where is MYRLI MASKIN OG EIENDOM AS based?

MYRLI MASKIN OG EIENDOM AS has its business address in Oppaker.

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

Report a problem

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