BIZTRAC BETA
Buying and selling of own real estate

MUNKHOLMEN EIENDOM II AS

Org. no. 915634761 Limited company (AS) Trondheim Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK 17,000
Incorporated 2015
Share capital NOK 30,000

Signals

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

MUNKHOLMEN EIENDOM II AS is registered as a limited company in Trondheim, Trøndelag with organisation number 915634761. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering i fast eiendom og annen virksomhet som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 17,000
Est. value
NOK 15,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns MUNKHOLMEN EIENDOM II AS?

MUNKHOLMEN EIENDOM AS
MUNKHOLMEN EIENDOM II AS
NOK 0 rev. · NOK 0 profit

MUNKHOLMEN EIENDOM II AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MUNKHOLMEN EIENDOM II AS

Who owns MUNKHOLMEN EIENDOM II AS?

MUNKHOLMEN EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of MUNKHOLMEN EIENDOM II AS?

MUNKHOLMEN EIENDOM II AS had revenue of NOK 0 in 2024.

Where is MUNKHOLMEN EIENDOM II AS based?

MUNKHOLMEN EIENDOM II AS has its business address in Trondheim.

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.