BIZTRAC BETA
Rental and leasing of water transport equipment

SEADREAM YACHTS AS

Org. no. 883602412 Limited company (AS) Asker Incorporated 2001 Active
Ownership graph ↗
Revenue 2024 NOK 6.9m
Operating profit NOK −175,000
Equity NOK 11.7m
Incorporated 2001
Share capital NOK 1.1m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−175k kr).

SEADREAM YACHTS AS is registered as a limited company in Asker, Akershus with organisation number 883602412. The business is classified under rental and leasing of water transport equipment (NACE 77.340). The company was incorporated in 2001. Registered share capital is NOK 1.1m, divided into 11000 shares. The company's stated purpose is: “Kjøp, salg, produksjon, tjenesteytende virksomhet, investering i fast eiendom, shipping, verdipapirer m.v. samt hva herved står i forbindelse herunder deltagelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.9m in revenue and NOK −175,000 in operating profit.

Key figures · 2024

Revenue
NOK 6.9m
Operating profit
NOK −175,000
Equity
NOK 11.7m
Est. value
NOK 7.3m

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
29.4%
Good
Equity as a share of total capital

Who owns SEADREAM YACHTS AS?

SEADREAM YACHT CLUB AS
SEADREAM YACHTS AS
NOK 6.9m rev. · NOK −175,000 profit

SEADREAM YACHTS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SEADREAM YACHTS AS

Who owns SEADREAM YACHTS AS?

SEADREAM YACHT CLUB AS is the largest registered owner, with 100.0%.

What is the revenue of SEADREAM YACHTS AS?

SEADREAM YACHTS AS had revenue of NOK 6.9m in 2024.

Where is SEADREAM YACHTS AS based?

SEADREAM YACHTS AS has its business address in Billingstad.

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.