BIZTRAC BETA
Freight coastal transport

SKIBSAKSJESELSKAPET HAASUND AS

Org. no. 817065252 Limited company (AS) Lillesand Incorporated 2016 Active
Ownership graph ↗
Operating profit NOK −3,000
Equity NOK −436,000
Incorporated 2016
Share capital NOK 36,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−436k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−3k kr).

SKIBSAKSJESELSKAPET HAASUND AS is registered as a limited company in Lillesand, Agder with organisation number 817065252. The business is classified under freight coastal transport (NACE 50.202). The company was incorporated in 2016. Registered share capital is NOK 36,000, divided into 36124 shares. The company's stated purpose is: “Kjøp og salg av skip og skipsandeler og skipsaksjer, drift og operasjon av skip og hva hermed står i forbindelse, samt deltakelse i selskaper av enhver art.”.

Key figures · 2024

Operating profit
NOK −3,000
Equity
NOK −436,000

Financial health · 2024

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

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

Who owns SKIBSAKSJESELSKAPET HAASUND AS?

KNUD GABRIEL FLØRENÆS KNUDSEN
SKIBSAKSJESELSKAPET HAASUND AS
· NOK −3,000 profit

SKIBSAKSJESELSKAPET HAASUND AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SKIBSAKSJESELSKAPET HAASUND AS own?

SKIBSAKSJESELSKAPET HAASUND AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SKIBSAKSJESELSKAPET HAASUND AS

Who owns SKIBSAKSJESELSKAPET HAASUND AS?

KNUD GABRIEL FLØRENÆS KNUDSEN is the largest registered owner, with 50.0%.

Where is SKIBSAKSJESELSKAPET HAASUND AS based?

SKIBSAKSJESELSKAPET HAASUND AS has its business address in Lillesand.

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.