BIZTRAC BETA
Freight ocean transport

SIEM DAY II AS

Org. no. 930456705 Limited company (AS) Kristiansand Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 22.4m
Operating profit NOK 9.7m
Equity NOK 45.2m
Incorporated 2022
Share capital NOK 60,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SIEM DAY II AS is registered as a limited company in Kristiansand, Agder with organisation number 930456705. The business is classified under freight ocean transport (NACE 50.201). The company was incorporated in 2022. Registered share capital is NOK 60,000, divided into 2000 shares. The company's stated purpose is: “Drift av og eierskap i offshorefartøyer, shippingvirksomhet, entreprenørvirksomhet, samt hva som står i forbindelse med de nevnte aktivitetsområder, herunder deltakelse i andre selskaper gjennom eierskap, Iån eller lignende engasjement.”. The most recent filed accounts, for the 2024 financial year, show NOK 22.4m in revenue and NOK 9.7m in operating profit.

Key figures · 2024

Revenue
NOK 22.4m
Operating profit
NOK 9.7m
Equity
NOK 45.2m
Est. value
NOK 54.1m

Financial health · 2024

Liquidity
0.60
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
80.9%
Very good
Equity as a share of total capital

Who owns SIEM DAY II AS?

SIEM OFFSHORE AS
SIEM DAY II AS
NOK 22.4m rev. · NOK 9.7m profit

SIEM DAY II AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SIEM DAY II AS

Who owns SIEM DAY II AS?

SIEM OFFSHORE AS is the largest registered owner, with 100.0%.

What is the revenue of SIEM DAY II AS?

SIEM DAY II AS had revenue of NOK 22.4m in 2024.

Where is SIEM DAY II AS based?

SIEM DAY II AS has its business address in Kristiansand S.

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.