BIZTRAC BETA
Other building completion and finishing

SIVERT HOLDING AS

Org. no. 830035702 Limited company (AS) Skien Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −47,000
Equity NOK 17.8m
Incorporated 2022
Share capital NOK 500,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−47k kr).

SIVERT HOLDING AS is registered as a limited company in Skien, Telemark with organisation number 830035702. The business is classified under other building completion and finishing (NACE 43.350). The company was incorporated in 2022. Registered share capital is NOK 500,000, divided into 100 shares. The company's stated purpose is: “Eie aksjer i andre selskap, investere i aksjer og andre verdipapirer, samt annen virksomhet som står i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −47,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −47,000
Equity
NOK 17.8m
Est. value
NOK 24.8m

Financial health · 2025

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

Who owns SIVERT HOLDING AS?

HANS EGIL SIVERTSEN
SIVERT HOLDING AS
NOK 0 rev. · NOK −47,000 profit

SIVERT HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SIVERT HOLDING AS own?

SIVERT HOLDING AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about SIVERT HOLDING AS

Who owns SIVERT HOLDING AS?

HANS EGIL SIVERTSEN is the largest registered owner, with 100.0%.

What is the revenue of SIVERT HOLDING AS?

SIVERT HOLDING AS had revenue of NOK 0 in 2025.

Where is SIVERT HOLDING AS based?

SIVERT HOLDING AS has its business address in Skien.

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.