BIZTRAC BETA
Rental and leasing of recreational and sports goods

STAVANGER MARINE AS

Org. no. 985203261 Limited company (AS) Stavanger Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 663,000
Operating profit NOK 114,000
Equity NOK 554,000
Incorporated 2002
Share capital NOK 2.4m

STAVANGER MARINE AS is registered as a limited company in Stavanger, Rogaland with organisation number 985203261. The business is classified under rental and leasing of recreational and sports goods (NACE 77.210). The company was incorporated in 2002. Registered share capital is NOK 2.4m, divided into 24000 shares. The company's stated purpose is: “Utleie og salg av båter og maritimt utstyr, samt deltakelse i andre selskaper, herunder kjøp/salg av aksjer og andeler.”. The most recent filed accounts, for the 2024 financial year, show NOK 663,000 in revenue and NOK 114,000 in operating profit.

Key figures · 2024

Revenue
NOK 663,000
Operating profit
NOK 114,000
Equity
NOK 554,000
Est. value
NOK 593,000

Financial health · 2024

Liquidity
0.18
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
11.6%
Satisfactory
Equity as a share of total capital

Who owns STAVANGER MARINE AS?

ØYSTEIN ROALSØ SIREVÅG
STAVANGER MARINE AS
NOK 663,000 rev. · NOK 114,000 profit

STAVANGER MARINE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STAVANGER MARINE AS

Who owns STAVANGER MARINE AS?

ØYSTEIN ROALSØ SIREVÅG is the largest registered owner, with 100.0%.

What is the revenue of STAVANGER MARINE AS?

STAVANGER MARINE AS had revenue of NOK 663,000 in 2024.

Who is the general manager of STAVANGER MARINE AS?

Øystein Roalsø Sirevåg is registered as general manager of STAVANGER MARINE AS.

Where is STAVANGER MARINE AS based?

STAVANGER MARINE AS has its business address in Hundvå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.