BIZTRAC BETA
Camping grounds and recreational vehicle parks

MORVIGSANDEN CAMPING AS

Org. no. 925195065 Limited company (AS) Grimstad Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 295,000
Equity NOK 1.1m
Incorporated 2020
Share capital NOK 30,000

MORVIGSANDEN CAMPING AS is registered as a limited company in Grimstad, Agder with organisation number 925195065. The business is classified under camping grounds and recreational vehicle parks (NACE 55.300). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drift og utvikling av camping, hytteutleie, eiendomsutvikling, investering i andre selskaper og alt som naturlig hører til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 295,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK 295,000
Equity
NOK 1.1m
Est. value
NOK 1.6m

Financial health · 2025

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

Who owns MORVIGSANDEN CAMPING AS?

JØRN MICHAEL BAKKE
MORVIGSANDEN CAMPING AS
NOK 1.5m rev. · NOK 295,000 profit

MORVIGSANDEN CAMPING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MORVIGSANDEN CAMPING AS

Who owns MORVIGSANDEN CAMPING AS?

JØRN MICHAEL BAKKE is the largest registered owner, with 100.0%.

What is the revenue of MORVIGSANDEN CAMPING AS?

MORVIGSANDEN CAMPING AS had revenue of NOK 1.5m in 2025.

Who is the general manager of MORVIGSANDEN CAMPING AS?

Jørn Michael Bakke is registered as general manager of MORVIGSANDEN CAMPING AS.

Where is MORVIGSANDEN CAMPING AS based?

MORVIGSANDEN CAMPING 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.