BIZTRAC BETA
Development of building projects

MOLVIKA TOMTESELSKAP AS

Org. no. 913897218 Limited company (AS) Vestby Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 167,000
Operating profit NOK −941,000
Equity NOK 572,000
Incorporated 2014
Share capital NOK 40,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−941k kr).

MOLVIKA TOMTESELSKAP AS is registered as a limited company in Vestby, Akershus with organisation number 913897218. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2014. Registered share capital is NOK 40,000, divided into 40 shares. The company's stated purpose is: “Kjøp og salg av tomter samt utvikling av disse.”. The most recent filed accounts, for the 2024 financial year, show NOK 167,000 in revenue and NOK −941,000 in operating profit.

Key figures · 2024

Revenue
NOK 167,000
Operating profit
NOK −941,000
Equity
NOK 572,000
Est. value
NOK 642,000

Financial health · 2024

Liquidity
1.37
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
28.2%
Good
Equity as a share of total capital

Who owns MOLVIKA TOMTESELSKAP AS?

MOLVIKA HOLDING AS
MOLVIKA TOMTESELSKAP AS
NOK 167,000 rev. · NOK −941,000 profit

MOLVIKA TOMTESELSKAP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MOLVIKA TOMTESELSKAP AS

Who owns MOLVIKA TOMTESELSKAP AS?

MOLVIKA HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of MOLVIKA TOMTESELSKAP AS?

MOLVIKA TOMTESELSKAP AS had revenue of NOK 167,000 in 2024.

Who is the general manager of MOLVIKA TOMTESELSKAP AS?

Per Johan Hoel is registered as general manager of MOLVIKA TOMTESELSKAP AS.

Where is MOLVIKA TOMTESELSKAP AS based?

MOLVIKA TOMTESELSKAP AS has its business address in Hølen.

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.