BIZTRAC BETA
Buying and selling of own real estate

MERINO EIENDOM II AS

Org. no. 925369284 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 9.0m
Operating profit NOK 8.2m
Equity NOK 18.8m
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-04-14 Adresseendring registrert 2026-04-14.

MERINO EIENDOM II AS is registered as a limited company in Oslo, Oslo with organisation number 925369284. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å eie aksjer i andre selskap, investere i aksjer og andre verdipapirer, kjøp og salg av eiendom, samt annen virksomhet som står i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.0m in revenue and NOK 8.2m in operating profit.

Key figures · 2024

Revenue
NOK 9.0m
Operating profit
NOK 8.2m
Equity
NOK 18.8m
Est. value
NOK 30.0m

Financial health · 2024

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

Who owns MERINO EIENDOM II AS?

MERINO UTVIKLING AS
MERINO EIENDOM II AS
NOK 9.0m rev. · NOK 8.2m profit

MERINO EIENDOM II AS has 1 registered shareholder:

All shareholders and roles →

Group structure

MERINO EIENDOM II AS er morselskap for 13 datterselskaper:

Frequently asked questions about MERINO EIENDOM II AS

Who owns MERINO EIENDOM II AS?

MERINO UTVIKLING AS is the largest registered owner, with 100.0%.

What is the revenue of MERINO EIENDOM II AS?

MERINO EIENDOM II AS had revenue of NOK 9.0m in 2024.

Where is MERINO EIENDOM II AS based?

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