BIZTRAC BETA
COMPANY REGISTER PROFILE
917863806 ORG. NO. 2024 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Rental and operating of own or leased real estate

SOLBERG EIENDOM OG UTLEIE AS

Org. no. 917863806 Limited company (AS) Skien Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK −80,000
Operating profit NOK −1.1m
Equity NOK −668,000
Incorporated 2016
Share capital NOK 1.0m

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−668k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,1 mill kr).

SOLBERG EIENDOM OG UTLEIE AS is registered as a limited company in Skien, Telemark with organisation number 917863806. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 1.0m, divided into 3350 shares. The company's stated purpose is: “Kjøp, salg og utleie av eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK −80,000 in revenue and NOK −1.1m in operating profit.

Key figures · 2024

Revenue
NOK −80,000
Operating profit
NOK −1.1m
Equity
NOK −668,000

Financial health · 2024

Liquidity
0.14
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-22.2%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SOLBERG EIENDOM OG UTLEIE AS?

No shareholders are registered for SOLBERG EIENDOM OG UTLEIE AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about SOLBERG EIENDOM OG UTLEIE AS

What is the revenue of SOLBERG EIENDOM OG UTLEIE AS?

SOLBERG EIENDOM OG UTLEIE AS had revenue of NOK −80,000 in 2024.

Where is SOLBERG EIENDOM OG UTLEIE AS based?

SOLBERG EIENDOM OG UTLEIE 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.