BIZTRAC BETA
Marine fishing

OLAGUTT AS

Org. no. 968571303 Limited company (AS) Sortland Incorporated 1993 Active
Ownership graph ↗
Revenue 2024 NOK 34.7m
Operating profit NOK 5.0m
Equity NOK 33.2m
Incorporated 1993
Employees 9
Share capital NOK 578,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

OLAGUTT AS is registered as a limited company in Sortland, Nordland with organisation number 968571303. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 1993 and has 9 registered employees. Registered share capital is NOK 578,000, divided into 578 shares. The company's stated purpose is: “Drive rederiveirksomhet med fiske og brønnbåttransport som hovedaktivitet, samt enhver form for deltakelse i nadre selskaper og annen virksomhet av økonomisk art.”. The most recent filed accounts, for the 2024 financial year, show NOK 34.7m in revenue and NOK 5.0m in operating profit.

Key figures · 2024

Revenue
NOK 34.7m
Operating profit
NOK 5.0m
Equity
NOK 33.2m
Est. value
NOK 26.8m

Financial health · 2024

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

Who owns OLAGUTT AS?

HÅKON GULLVIK HOLDING AS
OLAGUTT AS
NOK 34.7m rev. · NOK 5.0m profit

OLAGUTT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about OLAGUTT AS

Who owns OLAGUTT AS?

HÅKON GULLVIK HOLDING AS is the largest registered owner, with 81.8%.

What is the revenue of OLAGUTT AS?

OLAGUTT AS had revenue of NOK 34.7m in 2024.

Who is the general manager of OLAGUTT AS?

Håkon Gullvik is registered as general manager of OLAGUTT AS.

Where is OLAGUTT AS based?

OLAGUTT AS has its business address in Sortland.

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.