BIZTRAC BETA
Wholesale of fish, crustaceans and molluscs

VIKINGENS TØRRFISKSNACK AS

Org. no. 998237335 Limited company (AS) Kvinnherad Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 4.3m
Operating profit NOK 229,000
Equity NOK 331,000
Incorporated 2012
Share capital NOK 100,000

VIKINGENS TØRRFISKSNACK AS is registered as a limited company in Kvinnherad, Vestland with organisation number 998237335. The business is classified under wholesale of fish, crustaceans and molluscs (NACE 46.322). The company was incorporated in 2012. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Importere og selge islandske varer og virksomhet som har tilhørighet til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.3m in revenue and NOK 229,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.3m
Operating profit
NOK 229,000
Equity
NOK 331,000
Est. value
NOK 958,000

Financial health · 2025

Liquidity
1.31
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
20.3%
Good
Equity as a share of total capital

Who owns VIKINGENS TØRRFISKSNACK AS?

ERLING NICLASEN
VIKINGENS TØRRFISKSNACK AS
NOK 4.3m rev. · NOK 229,000 profit

VIKINGENS TØRRFISKSNACK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VIKINGENS TØRRFISKSNACK AS

Who owns VIKINGENS TØRRFISKSNACK AS?

ERLING NICLASEN is the largest registered owner, with 50.0%.

What is the revenue of VIKINGENS TØRRFISKSNACK AS?

VIKINGENS TØRRFISKSNACK AS had revenue of NOK 4.3m in 2025.

Who is the general manager of VIKINGENS TØRRFISKSNACK AS?

Niels Jakob Erlingsson is registered as general manager of VIKINGENS TØRRFISKSNACK AS.

Where is VIKINGENS TØRRFISKSNACK AS based?

VIKINGENS TØRRFISKSNACK AS has its business address in Sunde I Sunnhordland.

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.