BIZTRAC BETA
COMPANY REGISTER PROFILE
986611304 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Camping grounds and recreational vehicle parks

TVINDE CAMPING AS

Org. no. 986611304 Limited company (AS) Voss Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 11.4m
Operating profit NOK 3.4m
Equity NOK 13.2m
Incorporated 2004
Employees 6
Share capital NOK 100,000

TVINDE CAMPING AS is registered as a limited company in Voss, Vestland with organisation number 986611304. The business is classified under camping grounds and recreational vehicle parks (NACE 55.300). The company was incorporated in 2004 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drift av campingplass, utleie av hytter og salg av souvenirer og andre kioskvarer.”. The most recent filed accounts, for the 2025 financial year, show NOK 11.4m in revenue and NOK 3.4m in operating profit.

Key figures · 2025

Revenue
NOK 11.4m
▲ +6 %
Operating profit
NOK 3.4m
▲ +8 %
Equity
NOK 13.2m
▲ +25 %
Est. value
NOK 18.3m

Financial health · 2025

Liquidity
5.94
Very good
Current assets ÷ current liabilities
Profitability
26.3%
Very good
Return on total assets
Solidity
89.9%
Very good
Equity as a share of total capital

Who owns TVINDE CAMPING AS?

TVINDE CAMPING AS
NOK 11.4m rev. · NOK 3.4m profit

TVINDE CAMPING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TVINDE CAMPING AS

Who owns TVINDE CAMPING AS?

ARNE TVINDE is the largest registered owner, with 50.0%.

What is the revenue of TVINDE CAMPING AS?

TVINDE CAMPING AS had revenue of NOK 11.4m in 2025.

Who is the general manager of TVINDE CAMPING AS?

Arne Tvinde is registered as general manager of TVINDE CAMPING AS.

Where is TVINDE CAMPING AS based?

TVINDE CAMPING AS has its business address in Skulestadmo.

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

Report a problem

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