BIZTRAC BETA
Rental and operating of own or leased real estate

MOAK EIENDOM AS

Org. no. 921996500 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 280,000
Operating profit NOK 161,000
Equity NOK 842,000
Incorporated 2018
Share capital NOK 100,000

Signals

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

MOAK EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 921996500. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Drift av egen eiendom samt investeringer i fast eiendom og verdipapirer.”. The most recent filed accounts, for the 2025 financial year, show NOK 280,000 in revenue and NOK 161,000 in operating profit.

Key figures · 2025

Revenue
NOK 280,000
Operating profit
NOK 161,000
Equity
NOK 842,000
Est. value
NOK 900,000

Financial health · 2025

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

Who owns MOAK EIENDOM AS?

MOAK HOLDING AS
MOAK EIENDOM AS
NOK 280,000 rev. · NOK 161,000 profit

MOAK EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MOAK EIENDOM AS

Who owns MOAK EIENDOM AS?

MOAK HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of MOAK EIENDOM AS?

MOAK EIENDOM AS had revenue of NOK 280,000 in 2025.

Who is the general manager of MOAK EIENDOM AS?

Mohamed Akkouh is registered as general manager of MOAK EIENDOM AS.

Where is MOAK EIENDOM AS based?

MOAK EIENDOM 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.