BIZTRAC BETA
Rental and operating of own or leased real estate

SOLKYSTEN EIENDOM AS

Org. no. 912314758 Limited company (AS) Trondheim Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 343,000
Operating profit NOK −43,000
Equity NOK −1.5m
Incorporated 2013
Share capital NOK 300,000

Signals

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

SOLKYSTEN EIENDOM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 912314758. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Kjøp og utleie av eiendom i Spania.”. The most recent filed accounts, for the 2024 financial year, show NOK 343,000 in revenue and NOK −43,000 in operating profit.

Key figures · 2024

Revenue
NOK 343,000
Operating profit
NOK −43,000
Equity
NOK −1.5m

Financial health · 2025

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

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

Who owns SOLKYSTEN EIENDOM AS?

JAN T. THOMASSEN HOLDING AS
SOLKYSTEN EIENDOM AS
NOK 343,000 rev. · NOK −43,000 profit

SOLKYSTEN EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SOLKYSTEN EIENDOM AS

Who owns SOLKYSTEN EIENDOM AS?

JAN T. THOMASSEN HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of SOLKYSTEN EIENDOM AS?

SOLKYSTEN EIENDOM AS had revenue of NOK 343,000 in 2024.

Where is SOLKYSTEN EIENDOM AS based?

SOLKYSTEN EIENDOM AS has its business address in Trondheim.

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.