BIZTRAC BETA
Camping grounds and recreational vehicle parks

DAMPSAGA DRIFT AS

Org. no. 991216790 Limited company (AS) Lillehammer Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 13.1m
Operating profit NOK 372,000
Equity NOK 5.0m
Incorporated 2007
Employees 5
Share capital NOK 100,000

DAMPSAGA DRIFT AS is registered as a limited company in Lillehammer, Innlandet with organisation number 991216790. The business is classified under camping grounds and recreational vehicle parks (NACE 55.300). The company was incorporated in 2007 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drift av campingplass samt annen virksomhet i tilknytning til dette, utleie av leiligheter og hybler, handel med motorvogn og campingvogner og selskapet skal kunne eie fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 13.1m in revenue and NOK 372,000 in operating profit.

Key figures · 2024

Revenue
NOK 13.1m
Operating profit
NOK 372,000
Equity
NOK 5.0m
Est. value
NOK 3.8m

Financial health · 2024

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

Who owns DAMPSAGA DRIFT AS?

STIAN LUNN
DAMPSAGA DRIFT AS
NOK 13.1m rev. · NOK 372,000 profit

DAMPSAGA DRIFT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about DAMPSAGA DRIFT AS

Who owns DAMPSAGA DRIFT AS?

STIAN LUNN is the largest registered owner, with 67.0%.

What is the revenue of DAMPSAGA DRIFT AS?

DAMPSAGA DRIFT AS had revenue of NOK 13.1m in 2024.

Who is the general manager of DAMPSAGA DRIFT AS?

Stian Lunn is registered as general manager of DAMPSAGA DRIFT AS.

Where is DAMPSAGA DRIFT AS based?

DAMPSAGA DRIFT AS has its business address in Lillehammer.

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.