BIZTRAC BETA
Rental and operating of own or leased real estate

SIVERT BOLIG AS

Org. no. 930046965 Limited company (AS) Skien Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 150,000
Operating profit NOK −190,000
Equity NOK 491,000
Incorporated 2022
Share capital NOK 800,000

Signals

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

SIVERT BOLIG AS is registered as a limited company in Skien, Telemark with organisation number 930046965. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 800,000, divided into 100 shares. The company's stated purpose is: “Utleie, drift og utvikling av fast eiendom samt virksomhet som naturlig faller innunder dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 150,000 in revenue and NOK −190,000 in operating profit.

Key figures · 2025

Revenue
NOK 150,000
Operating profit
NOK −190,000
Equity
NOK 491,000
Est. value
NOK 561,000

Financial health · 2025

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

Who owns SIVERT BOLIG AS?

AM SIVERTSEN HOLDING AS
SIVERT BOLIG AS
NOK 150,000 rev. · NOK −190,000 profit

SIVERT BOLIG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SIVERT BOLIG AS

Who owns SIVERT BOLIG AS?

AM SIVERTSEN HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of SIVERT BOLIG AS?

SIVERT BOLIG AS had revenue of NOK 150,000 in 2025.

Who is the general manager of SIVERT BOLIG AS?

Andreas Sivertsen is registered as general manager of SIVERT BOLIG AS.

Where is SIVERT BOLIG AS based?

SIVERT BOLIG 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.