BIZTRAC BETA
Camping grounds and recreational vehicle parks

BERGEN CAMPING PARK AS

Org. no. 996259951 Limited company (AS) Bergen Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 8.9m
Operating profit NOK 707,000
Equity NOK 5.4m
Incorporated 2010
Employees 12
Share capital NOK 197,000

BERGEN CAMPING PARK AS is registered as a limited company in Bergen, Vestland with organisation number 996259951. The business is classified under camping grounds and recreational vehicle parks (NACE 55.300). The company was incorporated in 2010 and has 12 registered employees. Registered share capital is NOK 197,000, divided into 197 shares. The company's stated purpose is: “Campingspalss, samt kjøp, utvikling, utleie og salg av fast eiendom og alt som dertil hører til.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.9m in revenue and NOK 707,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.9m
Operating profit
NOK 707,000
Equity
NOK 5.4m
Est. value
NOK 6.3m

Financial health · 2024

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

Who owns BERGEN CAMPING PARK AS?

HERO EIENDOM AS
BERGEN CAMPING PARK AS
NOK 8.9m rev. · NOK 707,000 profit

BERGEN CAMPING PARK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BERGEN CAMPING PARK AS

Who owns BERGEN CAMPING PARK AS?

HERO EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of BERGEN CAMPING PARK AS?

BERGEN CAMPING PARK AS had revenue of NOK 8.9m in 2024.

Who is the general manager of BERGEN CAMPING PARK AS?

Hans Jørgen Tuft is registered as general manager of BERGEN CAMPING PARK AS.

Where is BERGEN CAMPING PARK AS based?

BERGEN CAMPING PARK AS has its business address in Breistein.

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.