BIZTRAC BETA
Business and other management consultancy activities

OLE SØRSKÅR AS

Org. no. 988450073 Limited company (AS) Hjelmeland Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 2.2m
Operating profit NOK −122,000
Equity NOK 730,000
Incorporated 2005
Share capital NOK 100,000

Signals

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

OLE SØRSKÅR AS is registered as a limited company in Hjelmeland, Rogaland with organisation number 988450073. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Konsulenttjenester innen regnskap og økonomi. Samt finansiell investeringsvirksomhet, og alt hva dermed er forbundet.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.2m in revenue and NOK −122,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.2m
Operating profit
NOK −122,000
Equity
NOK 730,000
Est. value
NOK 1.7m

Financial health · 2024

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

Who owns OLE SØRSKÅR AS?

OLE NORMANN SØRSKÅR
OLE SØRSKÅR AS
NOK 2.2m rev. · NOK −122,000 profit

OLE SØRSKÅR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OLE SØRSKÅR AS

Who owns OLE SØRSKÅR AS?

OLE NORMANN SØRSKÅR is the largest registered owner, with 100.0%.

What is the revenue of OLE SØRSKÅR AS?

OLE SØRSKÅR AS had revenue of NOK 2.2m in 2024.

Who is the general manager of OLE SØRSKÅR AS?

Ole Normann Sørskår is registered as general manager of OLE SØRSKÅR AS.

Where is OLE SØRSKÅR AS based?

OLE SØRSKÅR AS has its business address in Hjelmeland.

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.