BIZTRAC BETA
Camping grounds and recreational vehicle parks

STIKLESTAD CAMPING AS

Org. no. 974406373 Limited company (AS) Verdal Incorporated 1995 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK 127,000
Equity NOK 216,000
Incorporated 1995
Share capital NOK 150,000

STIKLESTAD CAMPING AS is registered as a limited company in Verdal, Trøndelag with organisation number 974406373. The business is classified under camping grounds and recreational vehicle parks (NACE 55.300). The company was incorporated in 1995. Registered share capital is NOK 150,000. The company's stated purpose is: “Servicevirksomhet i form av utleie av hytter, campingplass, kiosksalg og ellers det som står i naturlig forbindelse med dette, herunder å delta i andre selskaper med liknende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK 127,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK 127,000
Equity
NOK 216,000
Est. value
NOK 467,000

Financial health · 2024

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

Who owns STIKLESTAD CAMPING AS?

STEKKSTAD HOLDING AS
STIKLESTAD CAMPING AS
NOK 1.5m rev. · NOK 127,000 profit

STIKLESTAD CAMPING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STIKLESTAD CAMPING AS

Who owns STIKLESTAD CAMPING AS?

STEKKSTAD HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of STIKLESTAD CAMPING AS?

STIKLESTAD CAMPING AS had revenue of NOK 1.5m in 2024.

Who is the general manager of STIKLESTAD CAMPING AS?

Geir Asbjørn Strøm is registered as general manager of STIKLESTAD CAMPING AS.

Where is STIKLESTAD CAMPING AS based?

STIKLESTAD CAMPING AS has its business address in Verdal.

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.