BIZTRAC BETA
Hotels and similar accommodation

HAUKELI TURISTHEIM AS

Org. no. 913724054 Limited company (AS) Vinje Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 130,000
Operating profit NOK −63,000
Equity NOK −1.7m
Incorporated 2014
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,7 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−63k kr).

HAUKELI TURISTHEIM AS is registered as a limited company in Vinje, Telemark with organisation number 913724054. The business is classified under hotels and similar accommodation (NACE 55.100). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Formålet til selskapet er drift av servering, overnatting og utleige av bygg til slike formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 130,000 in revenue and NOK −63,000 in operating profit.

Key figures · 2024

Revenue
NOK 130,000
Operating profit
NOK −63,000
Equity
NOK −1.7m

Financial health · 2024

Liquidity
0.05
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-140.4%
Weak
Equity as a share of total capital

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

Who owns HAUKELI TURISTHEIM AS?

HARALD KVAALEN
HAUKELI TURISTHEIM AS
NOK 130,000 rev. · NOK −63,000 profit

HAUKELI TURISTHEIM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HAUKELI TURISTHEIM AS

Who owns HAUKELI TURISTHEIM AS?

HARALD KVAALEN is the largest registered owner, with 50.0%.

What is the revenue of HAUKELI TURISTHEIM AS?

HAUKELI TURISTHEIM AS had revenue of NOK 130,000 in 2024.

Where is HAUKELI TURISTHEIM AS based?

HAUKELI TURISTHEIM AS has its business address in Edland.

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.