biztrac. BETA
COMPANY REGISTER PROFILE
983970451 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

SØM LEGESENTER EIENDOM DA

Org. no. 983970451 General partnership with shared liability (DA) Kristiansand Incorporated 2001 Active
Ownership graph ↗
Revenue 2025 NOK 705,000
Operating profit NOK 480,000
Equity NOK −1.8m
Incorporated 2001

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,8 mill kr).

SØM LEGESENTER EIENDOM DA is registered as a general partnership with shared liability in Kristiansand, Agder with organisation number 983970451. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2001. The company's stated purpose is: “Eie og leie ut fast eiendom, samt alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 705,000 in revenue and NOK 480,000 in operating profit.

Former names: SØM LEGESENTER DA

Key figures · 2025

Revenue
NOK 705,000
▲ +15 %
Operating profit
NOK 480,000
▲ +154 %
Equity
NOK −1.8m
▲ +11 %
Est. value
NOK 3.4m

Financial health · 2025

Liquidity
0.79
Weak
Current assets ÷ current liabilities
Profitability
22.3%
Very good
Return on total assets
Solidity
-81.4%
Weak
Equity as a share of total capital

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

Who owns SØM LEGESENTER EIENDOM DA?

No shareholders are registered for SØM LEGESENTER EIENDOM DA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about SØM LEGESENTER EIENDOM DA

What is the revenue of SØM LEGESENTER EIENDOM DA?

SØM LEGESENTER EIENDOM DA had revenue of NOK 705,000 in 2025.

Where is SØM LEGESENTER EIENDOM DA based?

SØM LEGESENTER EIENDOM DA has its business address in Kristiansand S.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.