BIZTRAC BETA
Business and other management consultancy activities

OLE E SØRDAHL AS

Org. no. 937922094 Limited company (AS) Asker Incorporated 1986 Active
Ownership graph ↗
Revenue 2024 NOK 2.1m
Operating profit NOK −17,000
Equity NOK 233,000
Incorporated 1986
Share capital NOK 100,000

Signals

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

OLE E SØRDAHL AS is registered as a limited company in Asker, Akershus with organisation number 937922094. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 1986. Registered share capital is NOK 100,000. The company's stated purpose is: “Selskapets formål er å drive rådgivning overfor næringslivet, samt alt som står i forbindelse med dette, herunder deltakelse i andre selskaper med lignende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.1m in revenue and NOK −17,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.1m
Operating profit
NOK −17,000
Equity
NOK 233,000
Est. value
NOK 1.3m

Financial health · 2024

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

Who owns OLE E SØRDAHL AS?

OLE EKROLL SØRDAHL
OLE E SØRDAHL AS
NOK 2.1m rev. · NOK −17,000 profit

OLE E SØRDAHL AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about OLE E SØRDAHL AS

Who owns OLE E SØRDAHL AS?

OLE EKROLL SØRDAHL is the largest registered owner, with 60.0%.

What is the revenue of OLE E SØRDAHL AS?

OLE E SØRDAHL AS had revenue of NOK 2.1m in 2024.

Who is the general manager of OLE E SØRDAHL AS?

Ole Ekroll Sørdahl is registered as general manager of OLE E SØRDAHL AS.

Where is OLE E SØRDAHL AS based?

OLE E SØRDAHL AS has its business address in Nesbru.

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.