biztrac. BETA
COMPANY REGISTER PROFILE
966024607 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Site preparation

OLA FISKETJØN AS

Org. no. 966024607 Limited company (AS) Suldal Incorporated 1992 Active
Ownership graph ↗
Revenue 2025 NOK 8.7m
Operating profit NOK 443,000
Equity NOK 7.2m
Incorporated 1992
Employees 10
Share capital NOK 30,000

OLA FISKETJØN AS is registered as a limited company in Suldal, Rogaland with organisation number 966024607. The business is classified under site preparation (NACE 43.120). The company was incorporated in 1992 and has 10 registered employees. Registered share capital is NOK 30,000, divided into 80 shares. The company's stated purpose is: “Transport- og entreprenørvirksomhet og virksomhet som er knyttet til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.7m in revenue and NOK 443,000 in operating profit.

Key figures · 2025

Revenue
NOK 8.7m
▼ −26 %
Operating profit
NOK 443,000
▼ −44 %
Equity
NOK 7.2m
▲ +1 %
Est. value
NOK 5.2m

Financial health · 2025

Liquidity
3.47
Very good
Current assets ÷ current liabilities
Profitability
6.3%
Satisfactory
Return on total assets
Solidity
80.8%
Very good
Equity as a share of total capital

Who owns OLA FISKETJØN AS?

OLA FISKETJØN AS has 4 registered shareholders:

All shareholders and roles →

Which companies does OLA FISKETJØN AS own?

OLA FISKETJØN AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about OLA FISKETJØN AS

Who owns OLA FISKETJØN AS?

Solveig Fisketjøn is the largest registered owner, with 25.0%.

What is the revenue of OLA FISKETJØN AS?

OLA FISKETJØN AS had revenue of NOK 8.7m in 2025.

Who is the general manager of OLA FISKETJØN AS?

Dag Fisketjøn is registered as general manager of OLA FISKETJØN AS.

Where is OLA FISKETJØN AS based?

OLA FISKETJØN AS has its business address in Suldalsosen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.