BIZTRAC BETA
Buying and selling of own real estate

VIKINGBAD HOLDING AS

Org. no. 911656930 Limited company (AS) Grimstad Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 15.8m
Operating profit NOK 12.4m
Equity NOK 36.5m
Incorporated 2013
Share capital NOK 4.8m

VIKINGBAD HOLDING AS is registered as a limited company in Grimstad, Agder with organisation number 911656930. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2013. Registered share capital is NOK 4.8m, divided into 1000 shares. The company's stated purpose is: “Investeringer og deltagelse i andre selskaper og eiendom, samt alt som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 15.8m in revenue and NOK 12.4m in operating profit.

Key figures · 2024

Revenue
NOK 15.8m
Operating profit
NOK 12.4m
Equity
NOK 36.5m
Est. value
NOK 49.8m

Financial health · 2024

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

Who owns VIKINGBAD HOLDING AS?

DK HOLDING AS
VIKINGBAD HOLDING AS
NOK 15.8m rev. · NOK 12.4m profit

VIKINGBAD HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does VIKINGBAD HOLDING AS own?

VIKINGBAD HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Group structure

VIKINGBAD HOLDING AS er morselskap for 5 datterselskaper:

Frequently asked questions about VIKINGBAD HOLDING AS

Who owns VIKINGBAD HOLDING AS?

DK HOLDING AS is the largest registered owner, with 90.0%.

What is the revenue of VIKINGBAD HOLDING AS?

VIKINGBAD HOLDING AS had revenue of NOK 15.8m in 2024.

Where is VIKINGBAD HOLDING AS based?

VIKINGBAD HOLDING AS has its business address in Grimstad.

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.