BIZTRAC BETA
Buying and selling of own real estate

JOMAI EIENDOM AS

Org. no. 911815354 Limited company (AS) Vefsn Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −977,000
Equity NOK 1.6m
Incorporated 2013
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−977k kr).

JOMAI EIENDOM AS is registered as a limited company in Vefsn, Nordland with organisation number 911815354. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Entreprenørvirksomhet og eiendomsutvikling.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −977,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −977,000
Equity
NOK 1.6m
Est. value
NOK 1.4m

Financial health · 2025

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

Who owns JOMAI EIENDOM AS?

JOHN MIKALSEN
JOMAI EIENDOM AS
NOK 0 rev. · NOK −977,000 profit

JOMAI EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JOMAI EIENDOM AS own?

JOMAI EIENDOM AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about JOMAI EIENDOM AS

Who owns JOMAI EIENDOM AS?

JOHN MIKALSEN is the largest registered owner, with 100.0%.

What is the revenue of JOMAI EIENDOM AS?

JOMAI EIENDOM AS had revenue of NOK 0 in 2025.

Who is the general manager of JOMAI EIENDOM AS?

John Mikalsen is registered as general manager of JOMAI EIENDOM AS.

Where is JOMAI EIENDOM AS based?

JOMAI EIENDOM AS has its business address in Mosjøen.

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.