BIZTRAC BETA
Activities of excursion and event organisers

SPURKELAND VIKINGGARD AS

Org. no. 998378656 Limited company (AS) Alver Incorporated 2012 Active
Ownership graph ↗
Operating profit NOK −1,000
Equity NOK 70,000
Incorporated 2012
Share capital NOK 66,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1k kr).

SPURKELAND VIKINGGARD AS is registered as a limited company in Alver, Vestland with organisation number 998378656. The business is classified under activities of excursion and event organisers (NACE 79.121). The company was incorporated in 2012. Registered share capital is NOK 66,000, divided into 1320 shares. The company's stated purpose is: “Driva med formidling av historie, handverk og kultur frå vikingtida, herunder den kristne historien og evangeliets betydning for Noreg. Samt bevertning, overnatting og opplevingar i tilknytning til dette. Samt annan verksemd som naturleg har samanheng med dette.”.

Key figures · 2025

Operating profit
NOK −1,000
Equity
NOK 70,000
Est. value
NOK 101,000

Financial health · 2025

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

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

Who owns SPURKELAND VIKINGGARD AS?

OLE KRISTIAN KJENES
SPURKELAND VIKINGGARD AS
· NOK −1,000 profit

SPURKELAND VIKINGGARD AS has 7 registered shareholders:

All shareholders and roles →

Frequently asked questions about SPURKELAND VIKINGGARD AS

Who owns SPURKELAND VIKINGGARD AS?

OLE KRISTIAN KJENES is the largest registered owner, with 52.3%.

Who is the general manager of SPURKELAND VIKINGGARD AS?

Ole Kristian Kjenes is registered as general manager of SPURKELAND VIKINGGARD AS.

Where is SPURKELAND VIKINGGARD AS based?

SPURKELAND VIKINGGARD AS has its business address in Seim.

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.