biztrac. BETA
COMPANY REGISTER PROFILE
933384543 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Camping grounds and recreational vehicle parks

HALLAND CAMPING AS

Org. no. 933384543 Limited company (AS) Rennebu Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 3.5m
Operating profit NOK 647,000
Equity NOK 1.1m
Incorporated 2024
Employees 15
Share capital NOK 50,000

HALLAND CAMPING AS is registered as a limited company in Rennebu, Trøndelag with organisation number 933384543. The business is classified under camping grounds and recreational vehicle parks (NACE 55.300). The company was incorporated in 2024 and has 15 registered employees. Registered share capital is NOK 50,000, divided into 100 shares. The company's stated purpose is: “Drift av campingplass samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.5m in revenue and NOK 647,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.5m
▲ +21 %
Operating profit
NOK 647,000
▲ +23 %
Equity
NOK 1.1m
▲ +100 %
Est. value
NOK 2.7m

Financial health · 2025

Liquidity
1.73
Good
Current assets ÷ current liabilities
Profitability
33.4%
Very good
Return on total assets
Solidity
46.2%
Very good
Equity as a share of total capital

Who owns HALLAND CAMPING AS?

HALLAND CAMPING AS
NOK 3.5m rev. · NOK 647,000 profit

HALLAND CAMPING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HALLAND CAMPING AS

Who owns HALLAND CAMPING AS?

Tore Halland is the largest registered owner, with 100.0%.

What is the revenue of HALLAND CAMPING AS?

HALLAND CAMPING AS had revenue of NOK 3.5m in 2025.

Who is the general manager of HALLAND CAMPING AS?

Tore Halland is registered as general manager of HALLAND CAMPING AS.

Where is HALLAND CAMPING AS based?

HALLAND CAMPING AS has its business address in Rennebu.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.