BIZTRAC BETA
Rental and operating of own or leased real estate

MOA HANDELSEIENDOM II AS

Org. no. 896300482 Limited company (AS) Oslo Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 10.8m
Operating profit NOK 7.7m
Equity NOK 53.9m
Incorporated 2010
Share capital NOK 800,000

Signals

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

MOA HANDELSEIENDOM II AS is registered as a limited company in Oslo, Oslo with organisation number 896300482. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2010. Registered share capital is NOK 800,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av fast eiendom, utleie av fast eiendom, investering i aksjer, deltakelse i andre selskaper samt alt hva derved står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 10.8m in revenue and NOK 7.7m in operating profit.

Key figures · 2025

Revenue
NOK 10.8m
Operating profit
NOK 7.7m
Equity
NOK 53.9m
Est. value
NOK 50.1m

Financial health · 2025

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

Who owns MOA HANDELSEIENDOM II AS?

H-2 EIENDOM AS
MOA HANDELSEIENDOM II AS
NOK 10.8m rev. · NOK 7.7m profit

MOA HANDELSEIENDOM II AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MOA HANDELSEIENDOM II AS

Who owns MOA HANDELSEIENDOM II AS?

H-2 EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of MOA HANDELSEIENDOM II AS?

MOA HANDELSEIENDOM II AS had revenue of NOK 10.8m in 2025.

Where is MOA HANDELSEIENDOM II AS based?

MOA HANDELSEIENDOM II 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.