BIZTRAC BETA
Rental and operating of own or leased real estate

VIKAN HANDELSPARK AS

Org. no. 999660622 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 10.8m
Operating profit NOK 5.5m
Equity NOK 15,000
Incorporated 2013
Share capital NOK 2.0m

VIKAN HANDELSPARK AS is registered as a limited company in Oslo, Oslo with organisation number 999660622. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 2.0m, divided into 20000 shares. The company's stated purpose is: “Kjøp, salg, utleie og framleie av fast eiendom, samt annen virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 10.8m in revenue and NOK 5.5m in operating profit.

Key figures · 2025

Revenue
NOK 10.8m
Operating profit
NOK 5.5m
Equity
NOK 15,000
Est. value
NOK 8.3m

Financial health · 2025

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

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

Who owns VIKAN HANDELSPARK AS?

CONCILIA RETAIL PROPERTY AS
VIKAN HANDELSPARK AS
NOK 10.8m rev. · NOK 5.5m profit

VIKAN HANDELSPARK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VIKAN HANDELSPARK AS

Who owns VIKAN HANDELSPARK AS?

CONCILIA RETAIL PROPERTY AS is the largest registered owner, with 85.0%.

What is the revenue of VIKAN HANDELSPARK AS?

VIKAN HANDELSPARK AS had revenue of NOK 10.8m in 2025.

Who is the general manager of VIKAN HANDELSPARK AS?

Bjørn Unhjem is registered as general manager of VIKAN HANDELSPARK AS.

Where is VIKAN HANDELSPARK AS based?

VIKAN HANDELSPARK AS has its business address in Oslo.

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.