BIZTRAC BETA
Rental and operating of own or leased real estate

SVACO AS

Org. no. 998040256 Limited company (AS) Asker Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 945,000
Operating profit NOK 265,000
Equity NOK 284,000
Incorporated 2012
Share capital NOK 40,000

SVACO AS is registered as a limited company in Asker, Akershus with organisation number 998040256. 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 40,000, divided into 100 shares. The company's stated purpose is: “Investering i og forvaltning av eiendeler, herunder fast eiendom, verdipapirer,selskapsandeler, aksjer i norske og utenlandske selskaper og annen kommersiel virksomhet med tilknytning til dette. I tillegg yter selskapet konsulent og rådgivningstjenester basert på erfaring og kunnskap fra selskapets eiere.”. The most recent filed accounts, for the 2024 financial year, show NOK 945,000 in revenue and NOK 265,000 in operating profit.

Key figures · 2024

Revenue
NOK 945,000
Operating profit
NOK 265,000
Equity
NOK 284,000
Est. value
NOK 839,000

Financial health · 2024

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

Who owns SVACO AS?

CHRIS ATLE SVANEMYR
SVACO AS
NOK 945,000 rev. · NOK 265,000 profit

SVACO AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SVACO AS own?

SVACO AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SVACO AS

Who owns SVACO AS?

CHRIS ATLE SVANEMYR is the largest registered owner, with 60.0%.

What is the revenue of SVACO AS?

SVACO AS had revenue of NOK 945,000 in 2024.

Where is SVACO AS based?

SVACO AS has its business address in Asker.

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.