BIZTRAC BETA
Rental and operating of own or leased real estate

MORO AS

Org. no. 926169661 Limited company (AS) Oslo Incorporated 1971 Active
Ownership graph ↗
Revenue 2024 NOK 5.1m
Operating profit NOK 1.3m
Equity NOK 796.6m
Incorporated 1971
Share capital NOK 6.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

MORO AS is registered as a limited company in Oslo, Oslo with organisation number 926169661. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1971. Registered share capital is NOK 6.0m, divided into 1 shares. The company's stated purpose is: “Å eie, leie ut og forvalte maskiner, utstyr og faste eiendommer samt eie aksjer.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.1m in revenue and NOK 1.3m in operating profit.

Key figures · 2024

Revenue
NOK 5.1m
Operating profit
NOK 1.3m
Equity
NOK 796.6m
Est. value
NOK 550.9m

Financial health · 2024

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

Who owns MORO AS?

ROAR MORTENSEN
MORO AS
NOK 5.1m rev. · NOK 1.3m profit

MORO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MORO AS own?

MORO AS holds stakes in 22 companies:

See the full ownership structure →

Frequently asked questions about MORO AS

Who owns MORO AS?

ROAR MORTENSEN is the largest registered owner, with 100.0%.

What is the revenue of MORO AS?

MORO AS had revenue of NOK 5.1m in 2024.

Who is the general manager of MORO AS?

Roar Mortensen is registered as general manager of MORO AS.

Where is MORO AS based?

MORO 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.