BIZTRAC BETA
Rental and operating of own or leased real estate

OTTESENS SKIPSBYGGERI AS

Org. no. 915087779 Limited company (AS) Stord Incorporated 1968 Active
Ownership graph ↗
Revenue 2024 NOK 716,000
Operating profit NOK 64,000
Equity NOK −5.2m
Incorporated 1968
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−5,2 mill kr).

OTTESENS SKIPSBYGGERI AS is registered as a limited company in Stord, Vestland with organisation number 915087779. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1968. Registered share capital is NOK 100,000, divided into 40 shares. The company's stated purpose is: “Kjøp, salg, oppføring og utleie av eiendom samt generell handel og tjenesteyting.”. The most recent filed accounts, for the 2024 financial year, show NOK 716,000 in revenue and NOK 64,000 in operating profit.

Key figures · 2024

Revenue
NOK 716,000
Operating profit
NOK 64,000
Equity
NOK −5.2m
Est. value
NOK 440,000

Financial health · 2024

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

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

Who owns OTTESENS SKIPSBYGGERI AS?

LARS GUNVALD OTTESEN
OTTESENS SKIPSBYGGERI AS
NOK 716,000 rev. · NOK 64,000 profit

OTTESENS SKIPSBYGGERI AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about OTTESENS SKIPSBYGGERI AS

Who owns OTTESENS SKIPSBYGGERI AS?

LARS GUNVALD OTTESEN is the largest registered owner, with 90.0%.

What is the revenue of OTTESENS SKIPSBYGGERI AS?

OTTESENS SKIPSBYGGERI AS had revenue of NOK 716,000 in 2024.

Where is OTTESENS SKIPSBYGGERI AS based?

OTTESENS SKIPSBYGGERI AS has its business address in Sagvåg.

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.