BIZTRAC BETA
Drying and salting of fish

YNGVE OLSEN AS

Org. no. 965896511 Limited company (AS) Moskenes Incorporated 1992 Active
Ownership graph ↗
Revenue 2024 NOK 4.9m
Operating profit NOK −1.1m
Equity NOK −371,000
Incorporated 1992
Share capital NOK 1.1m

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−371k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,1 mill kr).

YNGVE OLSEN AS is registered as a limited company in Moskenes, Nordland with organisation number 965896511. The business is classified under drying and salting of fish (NACE 10.201). The company was incorporated in 1992. Registered share capital is NOK 1.1m, divided into 11100 shares. The company's stated purpose is: “Handel og produksjon, samt hva herved står i forbindelse, herunder deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.9m in revenue and NOK −1.1m in operating profit.

Key figures · 2024

Revenue
NOK 4.9m
Operating profit
NOK −1.1m
Equity
NOK −371,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns YNGVE OLSEN AS?

Yngve Olsen
YNGVE OLSEN AS
NOK 4.9m rev. · NOK −1.1m profit

YNGVE OLSEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about YNGVE OLSEN AS

Who owns YNGVE OLSEN AS?

Yngve Olsen is the largest registered owner, with 56.3%.

What is the revenue of YNGVE OLSEN AS?

YNGVE OLSEN AS had revenue of NOK 4.9m in 2024.

Who is the general manager of YNGVE OLSEN AS?

Yngve Olsen is registered as general manager of YNGVE OLSEN AS.

Where is YNGVE OLSEN AS based?

YNGVE OLSEN AS has its business address in Sørvågen.

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.