BIZTRAC BETA
Development of building projects

MARK EIENDOMSUTVIKLING AS

Org. no. 913049993 Limited company (AS) Stavanger Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 382,000
Operating profit NOK 159,000
Equity NOK 200,000
Incorporated 2013
Share capital NOK 30,000

MARK EIENDOMSUTVIKLING AS is registered as a limited company in Stavanger, Rogaland with organisation number 913049993. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp, forvaltning, utvikling, utleie og salg av fast eiendom, herunder gjennom underliggende eiendomsselskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 382,000 in revenue and NOK 159,000 in operating profit.

Key figures · 2025

Revenue
NOK 382,000
Operating profit
NOK 159,000
Equity
NOK 200,000
Est. value
NOK 561,000

Financial health · 2025

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

Who owns MARK EIENDOMSUTVIKLING AS?

MARK GRUPPEN AS
MARK EIENDOMSUTVIKLING AS
NOK 382,000 rev. · NOK 159,000 profit

MARK EIENDOMSUTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MARK EIENDOMSUTVIKLING AS

Who owns MARK EIENDOMSUTVIKLING AS?

MARK GRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of MARK EIENDOMSUTVIKLING AS?

MARK EIENDOMSUTVIKLING AS had revenue of NOK 382,000 in 2025.

Who is the general manager of MARK EIENDOMSUTVIKLING AS?

Olav Meling is registered as general manager of MARK EIENDOMSUTVIKLING AS.

Where is MARK EIENDOMSUTVIKLING AS based?

MARK EIENDOMSUTVIKLING AS has its business address in Stavanger.

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.