BIZTRAC BETA
Marine fishing

SPJÆRINGEN AS

Org. no. 991014896 Limited company (AS) Hvaler Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 42.3m
Operating profit NOK 422,000
Equity NOK 10.9m
Incorporated 2007
Share capital NOK 179,000

SPJÆRINGEN AS is registered as a limited company in Hvaler, Østfold with organisation number 991014896. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2007. Registered share capital is NOK 179,000, divided into 179000 shares. The company's stated purpose is: “Selskapets virksomhet er selv, gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter å drive fiske, samt annen virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 42.3m in revenue and NOK 422,000 in operating profit.

Key figures · 2024

Revenue
NOK 42.3m
Operating profit
NOK 422,000
Equity
NOK 10.9m
Est. value
NOK 6.1m

Financial health · 2024

Liquidity
0.73
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
5.3%
Weak
Equity as a share of total capital

Who owns SPJÆRINGEN AS?

SPJÆRINGEN HOLDING AS
SPJÆRINGEN AS
NOK 42.3m rev. · NOK 422,000 profit

SPJÆRINGEN AS has 4 registered shareholders:

All shareholders and roles →

Which companies does SPJÆRINGEN AS own?

SPJÆRINGEN AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SPJÆRINGEN AS

Who owns SPJÆRINGEN AS?

SPJÆRINGEN HOLDING AS is the largest registered owner, with 55.9%.

What is the revenue of SPJÆRINGEN AS?

SPJÆRINGEN AS had revenue of NOK 42.3m in 2024.

Who is the general manager of SPJÆRINGEN AS?

Henning Olaf Iversen is registered as general manager of SPJÆRINGEN AS.

Where is SPJÆRINGEN AS based?

SPJÆRINGEN AS has its business address in Vesterøy.

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.