biztrac. BETA
COMPANY REGISTER PROFILE
998309174 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Marine fishing

KJERRINGØY HAVFISKE AS

Org. no. 998309174 Limited company (AS) Bodø Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 217,000
Equity NOK 1.4m
Incorporated 2012
Share capital NOK 30,000

KJERRINGØY HAVFISKE AS is registered as a limited company in Bodø, Nordland with organisation number 998309174. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Drive fiske og hva som naturlig hører inn under dette. I tillegg skal selskapet drive med utleie av personell.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 217,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
▼ −45 %
Operating profit
NOK 217,000
▲ +38 %
Equity
NOK 1.4m
▲ +13 %
Est. value
NOK 1.5m

Financial health · 2025

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

Who owns KJERRINGØY HAVFISKE AS?

KJERRINGØY HAVFISKE AS
NOK 1.2m rev. · NOK 217,000 profit

KJERRINGØY HAVFISKE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KJERRINGØY HAVFISKE AS

Who owns KJERRINGØY HAVFISKE AS?

Morten Andre Pedersen is the largest registered owner, with 51.0%.

What is the revenue of KJERRINGØY HAVFISKE AS?

KJERRINGØY HAVFISKE AS had revenue of NOK 1.2m in 2025.

Who is the general manager of KJERRINGØY HAVFISKE AS?

Frank Harry Pedersen is registered as general manager of KJERRINGØY HAVFISKE AS.

Where is KJERRINGØY HAVFISKE AS based?

KJERRINGØY HAVFISKE AS has its business address in Kjerringøy.

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.