BIZTRAC BETA
Sports activities n.e.c.

OLSEN & SØNN AS

Org. no. 889253452 Limited company (AS) Våler Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −97,000
Equity NOK 16.5m
Incorporated 2005
Share capital NOK 100,000

Signals

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

OLSEN & SØNN AS is registered as a limited company in Våler, Østfold with organisation number 889253452. The business is classified under sports activities n.e.c. (NACE 93.190). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Rådgivning og deltagelse i andre virksomheter, samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −97,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −97,000
Equity
NOK 16.5m
Est. value
NOK 128.0m

Financial health · 2024

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

Who owns OLSEN & SØNN AS?

ROY ESPEN OLSEN
OLSEN & SØNN AS
NOK 0 rev. · NOK −97,000 profit

OLSEN & SØNN AS has 2 registered shareholders:

All shareholders and roles →

Which companies does OLSEN & SØNN AS own?

OLSEN & SØNN AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about OLSEN & SØNN AS

Who owns OLSEN & SØNN AS?

ROY ESPEN OLSEN is the largest registered owner, with 88.0%.

What is the revenue of OLSEN & SØNN AS?

OLSEN & SØNN AS had revenue of NOK 0 in 2024.

Who is the general manager of OLSEN & SØNN AS?

Roy Espen Olsen is registered as general manager of OLSEN & SØNN AS.

Where is OLSEN & SØNN AS based?

OLSEN & SØNN AS has its business address in Våler I Østfold.

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.