BIZTRAC BETA
Rental and operating of own or leased real estate

SANDEM EIENDOM AS

Org. no. 992290242 Limited company (AS) Fredrikstad Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 548,000
Operating profit NOK 190,000
Equity NOK −106,000
Incorporated 2008
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−106k kr).

SANDEM EIENDOM AS is registered as a limited company in Fredrikstad, Østfold with organisation number 992290242. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Handel med og investering i fast eiendom, verdipapirer og andre formuesobjekter, herunder deltakelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 548,000 in revenue and NOK 190,000 in operating profit.

Key figures · 2025

Revenue
NOK 548,000
Operating profit
NOK 190,000
Equity
NOK −106,000
Est. value
NOK 2.0m

Financial health · 2025

Liquidity
7.58
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-1.7%
Weak
Equity as a share of total capital

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

Who owns SANDEM EIENDOM AS?

JENS MARTIN SOLBERG
SANDEM EIENDOM AS
NOK 548,000 rev. · NOK 190,000 profit

SANDEM EIENDOM AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about SANDEM EIENDOM AS

Who owns SANDEM EIENDOM AS?

JENS MARTIN SOLBERG is the largest registered owner, with 30.0%.

What is the revenue of SANDEM EIENDOM AS?

SANDEM EIENDOM AS had revenue of NOK 548,000 in 2025.

Where is SANDEM EIENDOM AS based?

SANDEM EIENDOM AS has its business address in Torp.

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.