BIZTRAC BETA
Rental and operating of own or leased real estate

SVETOR EIENDOM AS

Org. no. 930782394 Limited company (AS) Bærum Incorporated 1962 Active
Ownership graph ↗
Revenue 2024 NOK 4.9m
Operating profit NOK −2.2m
Equity NOK 9.5m
Incorporated 1962
Share capital NOK 2.2m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,2 mill kr).

SVETOR EIENDOM AS is registered as a limited company in Bærum, Akershus with organisation number 930782394. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1962. Registered share capital is NOK 2.2m, divided into 7088 shares. The company's stated purpose is: “Passiv forvaltning av kapital i form av faste eiendommer, selskapsandeler o.a., med sikte på å oppnå avkastning på den investerte kapital.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.9m in revenue and NOK −2.2m in operating profit.

Key figures · 2024

Revenue
NOK 4.9m
Operating profit
NOK −2.2m
Equity
NOK 9.5m
Est. value
NOK 13.9m

Financial health · 2024

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

Who owns SVETOR EIENDOM AS?

SVEIN PERSSON AS
SVETOR EIENDOM AS
NOK 4.9m rev. · NOK −2.2m profit

SVETOR EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SVETOR EIENDOM AS

Who owns SVETOR EIENDOM AS?

SVEIN PERSSON AS is the largest registered owner, with 50.0%.

What is the revenue of SVETOR EIENDOM AS?

SVETOR EIENDOM AS had revenue of NOK 4.9m in 2024.

Who is the general manager of SVETOR EIENDOM AS?

Svein Roald Persson is registered as general manager of SVETOR EIENDOM AS.

Where is SVETOR EIENDOM AS based?

SVETOR EIENDOM AS has its business address in Stabekk.

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.