BIZTRAC BETA
Marine fishing

GRIMSHOLM FISKEDRIFT AS

Org. no. 915785166 Limited company (AS) Tromsø Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 53.5m
Operating profit NOK 20.5m
Equity NOK 115.1m
Incorporated 2015
Employees 9
Share capital NOK 30.0m

GRIMSHOLM FISKEDRIFT AS is registered as a limited company in Tromsø, Troms with organisation number 915785166. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2015 and has 9 registered employees. Registered share capital is NOK 30.0m, divided into 29970060 shares. The company's stated purpose is: “Drive fiske- og fangstvirksomhet, samt hva som naturlig står i forbindelse med dette. Selskapet kan også drive annen virksomhet med økonomisk formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 53.5m in revenue and NOK 20.5m in operating profit.

Key figures · 2024

Revenue
NOK 53.5m
Operating profit
NOK 20.5m
Equity
NOK 115.1m
Est. value
NOK 105.9m

Financial health · 2024

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

Who owns GRIMSHOLM FISKEDRIFT AS?

NYE GRIMSHOLM HOLDING AS
GRIMSHOLM FISKEDRIFT AS
NOK 53.5m rev. · NOK 20.5m profit

GRIMSHOLM FISKEDRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GRIMSHOLM FISKEDRIFT AS

Who owns GRIMSHOLM FISKEDRIFT AS?

NYE GRIMSHOLM HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of GRIMSHOLM FISKEDRIFT AS?

GRIMSHOLM FISKEDRIFT AS had revenue of NOK 53.5m in 2024.

Who is the general manager of GRIMSHOLM FISKEDRIFT AS?

Knut Martin Karlsen is registered as general manager of GRIMSHOLM FISKEDRIFT AS.

Where is GRIMSHOLM FISKEDRIFT AS based?

GRIMSHOLM FISKEDRIFT AS has its business address in Tromsø.

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.