BIZTRAC BETA
Development of building projects

MEKKAO EIENDOM OG INVEST AS

Org. no. 918328947 Limited company (AS) Nesodden Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 2.2m
Operating profit NOK 1.7m
Equity NOK 1.9m
Incorporated 2016
Share capital NOK 30,000

MEKKAO EIENDOM OG INVEST AS is registered as a limited company in Nesodden, Akershus with organisation number 918328947. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kjøp og salg av eiendom, samt kjøp og salg av aksjer, og det som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK 1.7m in operating profit.

Key figures · 2025

Revenue
NOK 2.2m
Operating profit
NOK 1.7m
Equity
NOK 1.9m
Est. value
NOK 4.6m

Financial health · 2025

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

Who owns MEKKAO EIENDOM OG INVEST AS?

ODDMUND ELDFINN FOSS
MEKKAO EIENDOM OG INVEST AS
NOK 2.2m rev. · NOK 1.7m profit

MEKKAO EIENDOM OG INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MEKKAO EIENDOM OG INVEST AS

Who owns MEKKAO EIENDOM OG INVEST AS?

ODDMUND ELDFINN FOSS is the largest registered owner, with 100.0%.

What is the revenue of MEKKAO EIENDOM OG INVEST AS?

MEKKAO EIENDOM OG INVEST AS had revenue of NOK 2.2m in 2025.

Who is the general manager of MEKKAO EIENDOM OG INVEST AS?

Oddmund Eldfinn Foss is registered as general manager of MEKKAO EIENDOM OG INVEST AS.

Where is MEKKAO EIENDOM OG INVEST AS based?

MEKKAO EIENDOM OG INVEST AS has its business address in Nesodden.

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.