biztrac. BETA
COMPANY REGISTER PROFILE
918409009 ORG. NO. 2025 ACCOUNTS 12 SECTIONS
Active UPDATED 03.10.2026
Hotels and similar accommodation

HAUGSEN DRIFT AS

Org. no. 918409009 Limited company (AS) Evje Og Hornnes Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 7.7m
Operating profit NOK 260,000
Equity NOK 185,000
Incorporated 2017
Employees 15
Share capital NOK 50,000

HAUGSEN DRIFT AS is registered as a limited company in Evje Og Hornnes, Agder with organisation number 918409009. The business is classified under hotels and similar accommodation (NACE 55.100). The company was incorporated in 2017 and has 15 registered employees. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Drift av hotell- og restaurant, og alt som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.7m in revenue and NOK 260,000 in operating profit.

Key figures · 2025

Revenue
NOK 7.7m
▲ +0 %
Operating profit
NOK 260,000
▼ −38 %
Equity
NOK 185,000
▼ −46 %
Est. value
NOK 996,000

Financial health · 2025

Liquidity
0.87
Weak
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
10.7%
Satisfactory
Equity as a share of total capital

Who owns HAUGSEN DRIFT AS?

HAUGSEN DRIFT AS
NOK 7.7m rev. · NOK 260,000 profit

HAUGSEN DRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HAUGSEN DRIFT AS

Who owns HAUGSEN DRIFT AS?

HAUGSEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of HAUGSEN DRIFT AS?

HAUGSEN DRIFT AS had revenue of NOK 7.7m in 2025.

Who is the general manager of HAUGSEN DRIFT AS?

Else Haugland is registered as general manager of HAUGSEN DRIFT AS.

Where is HAUGSEN DRIFT AS based?

HAUGSEN DRIFT AS has its business address in Evje.

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.