BIZTRAC BETA
Rental and operating of own or leased real estate

MJELDALEN NÆRINGSPARK AS

Org. no. 923186522 Limited company (AS) Osterøy Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 99,000
Operating profit NOK 45,000
Equity NOK 807,000
Incorporated 2019
Share capital NOK 30,000

MJELDALEN NÆRINGSPARK AS is registered as a limited company in Osterøy, Vestland with organisation number 923186522. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 301 shares. The company's stated purpose is: “Investering i og utvikling av fast eiendom, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 99,000 in revenue and NOK 45,000 in operating profit.

Key figures · 2024

Revenue
NOK 99,000
Operating profit
NOK 45,000
Equity
NOK 807,000
Est. value
NOK 703,000

Financial health · 2024

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

Who owns MJELDALEN NÆRINGSPARK AS?

MIN FORVALTNING AS
MJELDALEN NÆRINGSPARK AS
NOK 99,000 rev. · NOK 45,000 profit

MJELDALEN NÆRINGSPARK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MJELDALEN NÆRINGSPARK AS

Who owns MJELDALEN NÆRINGSPARK AS?

MIN FORVALTNING AS is the largest registered owner, with 100.0%.

What is the revenue of MJELDALEN NÆRINGSPARK AS?

MJELDALEN NÆRINGSPARK AS had revenue of NOK 99,000 in 2024.

Who is the general manager of MJELDALEN NÆRINGSPARK AS?

Nils Skjerping is registered as general manager of MJELDALEN NÆRINGSPARK AS.

Where is MJELDALEN NÆRINGSPARK AS based?

MJELDALEN NÆRINGSPARK AS has its business address in Valestrandsfossen.

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.