BIZTRAC BETA
Site preparation

OLAV SOLVANG AS

Org. no. 976502337 Limited company (AS) Tokke Incorporated 1996 Active
Ownership graph ↗
Revenue 2025 NOK 230,000
Operating profit NOK −317,000
Equity NOK 617,000
Incorporated 1996
Share capital NOK 100,000

Signals

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

OLAV SOLVANG AS is registered as a limited company in Tokke, Telemark with organisation number 976502337. The business is classified under site preparation (NACE 43.120). The company was incorporated in 1996. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Drive som maskinentreprenør og det som naturlig hører til under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 230,000 in revenue and NOK −317,000 in operating profit.

Key figures · 2025

Revenue
NOK 230,000
Operating profit
NOK −317,000
Equity
NOK 617,000
Est. value
NOK 346,000

Financial health · 2025

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

Who owns OLAV SOLVANG AS?

OLAV SOLVANG
OLAV SOLVANG AS
NOK 230,000 rev. · NOK −317,000 profit

OLAV SOLVANG AS has 2 registered shareholders:

All shareholders and roles →

Which companies does OLAV SOLVANG AS own?

OLAV SOLVANG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about OLAV SOLVANG AS

Who owns OLAV SOLVANG AS?

OLAV SOLVANG is the largest registered owner, with 80.0%.

What is the revenue of OLAV SOLVANG AS?

OLAV SOLVANG AS had revenue of NOK 230,000 in 2025.

Who is the general manager of OLAV SOLVANG AS?

Olav Solvang is registered as general manager of OLAV SOLVANG AS.

Where is OLAV SOLVANG AS based?

OLAV SOLVANG AS has its business address in Dalen.

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.