BIZTRAC BETA
Development of building projects

SOLING EIENDOM AS

Org. no. 998934001 Limited company (AS) Bergen Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 40,000
Operating profit NOK −37,000
Equity NOK 1.0m
Incorporated 2012
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−37k kr).

SOLING EIENDOM AS is registered as a limited company in Bergen, Vestland with organisation number 998934001. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2012. Registered share capital is NOK 100,000, divided into 10000 shares. The company's stated purpose is: “Å eie og utvikle fast eiendom for utleie og salg og tilsvarende virksomhet, herunder deltagelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 40,000 in revenue and NOK −37,000 in operating profit.

Key figures · 2024

Revenue
NOK 40,000
Operating profit
NOK −37,000
Equity
NOK 1.0m
Est. value
NOK 751,000

Financial health · 2024

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

Who owns SOLING EIENDOM AS?

WILHING HOLDING AS
SOLING EIENDOM AS
NOK 40,000 rev. · NOK −37,000 profit

SOLING EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SOLING EIENDOM AS own?

SOLING EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SOLING EIENDOM AS

Who owns SOLING EIENDOM AS?

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

What is the revenue of SOLING EIENDOM AS?

SOLING EIENDOM AS had revenue of NOK 40,000 in 2024.

Where is SOLING EIENDOM AS based?

SOLING EIENDOM AS has its business address in Olsvik.

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.