BIZTRAC BETA
Development of building projects

MAKE EIENDOMSUTVIKLING AS

Org. no. 931147579 Limited company (AS) Lørenskog Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 299,000
Operating profit NOK 256,000
Equity NOK −196,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−196k kr).

MAKE EIENDOMSUTVIKLING AS is registered as a limited company in Lørenskog, Akershus with organisation number 931147579. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Bygge- og vedlikeholdsvirksomhet og alt som hermed er forbundet, samt kjøp og salg av eiendom og aksjer.”. The most recent filed accounts, for the 2025 financial year, show NOK 299,000 in revenue and NOK 256,000 in operating profit.

Key figures · 2025

Revenue
NOK 299,000
Operating profit
NOK 256,000
Equity
NOK −196,000
Est. value
NOK 1.8m

Financial health · 2025

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

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

Who owns MAKE EIENDOMSUTVIKLING AS?

FOKUS EIENDOM AS
MAKE EIENDOMSUTVIKLING AS
NOK 299,000 rev. · NOK 256,000 profit

MAKE EIENDOMSUTVIKLING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MAKE EIENDOMSUTVIKLING AS

Who owns MAKE EIENDOMSUTVIKLING AS?

FOKUS EIENDOM AS is the largest registered owner, with 50.0%.

What is the revenue of MAKE EIENDOMSUTVIKLING AS?

MAKE EIENDOMSUTVIKLING AS had revenue of NOK 299,000 in 2025.

Where is MAKE EIENDOMSUTVIKLING AS based?

MAKE EIENDOMSUTVIKLING AS has its business address in Fjellhamar.

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.