BIZTRAC BETA
Rental and operating of own or leased real estate

SØM AS

Org. no. 898354032 Limited company (AS) Ringerike Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −38,000
Equity NOK 17.3m
Incorporated 2012
Share capital NOK 449,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−38k kr).
  • Nylig endring 2026-02-16 Adresseendring registrert 2026-02-16.

SØM AS is registered as a limited company in Ringerike, Buskerud with organisation number 898354032. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 449,000, divided into 449 shares. The company's stated purpose is: “forvalte verdipapirer og eiendom, drive eiendomsutvikling og utøve konsulentvirksomhet. Selskapet kan helt eller delvis eie annen virksomhet som hører naturlig sammen med virksomheten i selskapet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −38,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −38,000
Equity
NOK 17.3m
Est. value
NOK 44.0m

Financial health · 2025

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

Who owns SØM AS?

METTE SØNSTEBY
SØM AS
NOK 0 rev. · NOK −38,000 profit

SØM AS has 7 registered shareholders:

All shareholders and roles →

Which companies does SØM AS own?

SØM AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about SØM AS

Who owns SØM AS?

METTE SØNSTEBY is the largest registered owner, with 93.3%.

What is the revenue of SØM AS?

SØM AS had revenue of NOK 0 in 2025.

Where is SØM AS based?

SØM AS has its business address in Hønefoss.

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.