BIZTRAC BETA
Camping grounds and recreational vehicle parks

UTVIKA AS

Org. no. 917104883 Limited company (AS) Hole Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 7.0m
Operating profit NOK 526,000
Equity NOK −1.2m
Incorporated 2016
Employees 19
Share capital NOK 300,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,2 mill kr).

UTVIKA AS is registered as a limited company in Hole, Buskerud with organisation number 917104883. The business is classified under camping grounds and recreational vehicle parks (NACE 55.300). The company was incorporated in 2016 and has 19 registered employees. Registered share capital is NOK 300,000, divided into 100 shares. The company's stated purpose is: “Overnatting og servering, omsetning av dagligvarer, kjøp og salg av virksomheter og annet som står i naturlig forhold til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.0m in revenue and NOK 526,000 in operating profit.

Key figures · 2025

Revenue
NOK 7.0m
Operating profit
NOK 526,000
Equity
NOK −1.2m
Est. value
NOK 3.2m

Financial health · 2025

Liquidity
1.38
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-6.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns UTVIKA AS?

TORILL JOHBRÅTEN
UTVIKA AS
NOK 7.0m rev. · NOK 526,000 profit

UTVIKA AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about UTVIKA AS

Who owns UTVIKA AS?

TORILL JOHBRÅTEN is the largest registered owner, with 60.0%.

What is the revenue of UTVIKA AS?

UTVIKA AS had revenue of NOK 7.0m in 2025.

Who is the general manager of UTVIKA AS?

Anita Johbraaten is registered as general manager of UTVIKA AS.

Where is UTVIKA AS based?

UTVIKA AS has its business address in Krokkleiva.

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.