BIZTRAC BETA
Development of building projects

MYRERVEIEN 31 AS

Org. no. 994642979 Limited company (AS) Oslo Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 84.0m
Operating profit NOK 3.8m
Equity NOK 1.2m
Incorporated 2009
Share capital NOK 100,000

Signals

2 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-03-16 Adresseendring registrert 2026-03-16.

MYRERVEIEN 31 AS is registered as a limited company in Oslo, Oslo with organisation number 994642979. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eiendomsutvikling, kjøp og salg av fast eiendom, utleie av eiendom. ”. The most recent filed accounts, for the 2024 financial year, show NOK 84.0m in revenue and NOK 3.8m in operating profit.

Key figures · 2024

Revenue
NOK 84.0m
Operating profit
NOK 3.8m
Equity
NOK 1.2m
Est. value
NOK 8.1m

Financial health · 2024

Liquidity
0.62
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.8%
Not satisfactory
Equity as a share of total capital

Who owns MYRERVEIEN 31 AS?

EIRIK ASP AS
MYRERVEIEN 31 AS
NOK 84.0m rev. · NOK 3.8m profit

MYRERVEIEN 31 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MYRERVEIEN 31 AS

Who owns MYRERVEIEN 31 AS?

EIRIK ASP AS is the largest registered owner, with 100.0%.

What is the revenue of MYRERVEIEN 31 AS?

MYRERVEIEN 31 AS had revenue of NOK 84.0m in 2024.

Who is the general manager of MYRERVEIEN 31 AS?

Eirik Asp is registered as general manager of MYRERVEIEN 31 AS.

Where is MYRERVEIEN 31 AS based?

MYRERVEIEN 31 AS has its business address in Oslo.

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.