BIZTRAC BETA
Development of building projects

VALEMON EIENDOM AS

Org. no. 879284562 Limited company (AS) Tønsberg Incorporated 1997 Active
Ownership graph ↗
Revenue 2025 NOK 52,000
Operating profit NOK −968,000
Equity NOK 435,000
Incorporated 1997
Share capital NOK 51,000

Signals

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

VALEMON EIENDOM AS is registered as a limited company in Tønsberg, Vestfold with organisation number 879284562. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 1997. Registered share capital is NOK 51,000, divided into 153 shares. The company's stated purpose is: “Kjøp, salg, herunder eie, utvikle fast eiendom, videre delta som andels/aksjeeier i andre selskaper med slik interesse samt alt hva som hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 52,000 in revenue and NOK −968,000 in operating profit.

Key figures · 2025

Revenue
NOK 52,000
Operating profit
NOK −968,000
Equity
NOK 435,000
Est. value
NOK 1.7m

Financial health · 2024

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

Who owns VALEMON EIENDOM AS?

WIND. AS
VALEMON EIENDOM AS
NOK 52,000 rev. · NOK −968,000 profit

VALEMON EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VALEMON EIENDOM AS

Who owns VALEMON EIENDOM AS?

WIND. AS is the largest registered owner, with 50.0%.

What is the revenue of VALEMON EIENDOM AS?

VALEMON EIENDOM AS had revenue of NOK 52,000 in 2025.

Who is the general manager of VALEMON EIENDOM AS?

Øyvind Johnsen is registered as general manager of VALEMON EIENDOM AS.

Where is VALEMON EIENDOM AS based?

VALEMON EIENDOM AS has its business address in Tønsberg.

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.