biztrac. BETA
COMPANY REGISTER PROFILE
985717265 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Retail sale of pleasure boats and equipment

SIDDIS MARINE AS

Org. no. 985717265 Limited company (AS) Stavanger Incorporated 2003 Active
Ownership graph ↗
Revenue 2025 NOK 31.1m
Operating profit NOK 3.0m
Equity NOK 9.6m
Incorporated 2003
Employees 17
Share capital NOK 500,000

SIDDIS MARINE AS is registered as a limited company in Stavanger, Rogaland with organisation number 985717265. The business is classified under retail sale of pleasure boats and equipment (NACE 47.632). The company was incorporated in 2003 and has 17 registered employees. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Handel med båter, båtrekvisita og motorer med tilhørende virksomhet samt delta i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 31.1m in revenue and NOK 3.0m in operating profit.

Key figures · 2025

Revenue
NOK 31.1m
▲ +6 %
Operating profit
NOK 3.0m
▲ +59 %
Equity
NOK 9.6m
▲ +5 %
Est. value
NOK 14.7m

Financial health · 2025

Liquidity
3.11
Very good
Current assets ÷ current liabilities
Profitability
24.1%
Very good
Return on total assets
Solidity
67.9%
Very good
Equity as a share of total capital

Who owns SIDDIS MARINE AS?

SIDDIS MARINE AS
NOK 31.1m rev. · NOK 3.0m profit

SIDDIS MARINE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SIDDIS MARINE AS

Who owns SIDDIS MARINE AS?

SIDDIS HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SIDDIS MARINE AS?

SIDDIS MARINE AS had revenue of NOK 31.1m in 2025.

Who is the general manager of SIDDIS MARINE AS?

Jon Gaute Hille is registered as general manager of SIDDIS MARINE AS.

Where is SIDDIS MARINE AS based?

SIDDIS MARINE AS has its business address in Stavanger.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.