BIZTRAC BETA
Rental and operating of own or leased real estate

SILJØ HOLDING AS

Org. no. 989069551 Limited company (AS) Hole Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 1.9m
Operating profit NOK −2.5m
Equity NOK 6.4m
Incorporated 2005
Share capital NOK 704,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,5 mill kr).

SILJØ HOLDING AS is registered as a limited company in Hole, Buskerud with organisation number 989069551. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 704,000, divided into 176 shares. The company's stated purpose is: “Eie og drive fast eiendom, investeringer i andre selskaper, investering i aksjer og andre verdipapirer og hva som derved er forbundet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.9m in revenue and NOK −2.5m in operating profit.

Key figures · 2024

Revenue
NOK 1.9m
Operating profit
NOK −2.5m
Equity
NOK 6.4m
Est. value
NOK 6.6m

Financial health · 2024

Liquidity
1.05
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
56.2%
Very good
Equity as a share of total capital

Who owns SILJØ HOLDING AS?

JØRN KRISTIAN ULLERN
SILJØ HOLDING AS
NOK 1.9m rev. · NOK −2.5m profit

SILJØ HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SILJØ HOLDING AS own?

SILJØ HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SILJØ HOLDING AS

Who owns SILJØ HOLDING AS?

JØRN KRISTIAN ULLERN is the largest registered owner, with 50.0%.

What is the revenue of SILJØ HOLDING AS?

SILJØ HOLDING AS had revenue of NOK 1.9m in 2024.

Where is SILJØ HOLDING AS based?

SILJØ HOLDING AS has its business address in Røyse.

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.