BIZTRAC BETA
Repair and maintenance of motor vehicles

HAUGLAND AUTOMOBIL AS

Org. no. 911695170 Limited company (AS) Osterøy Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 38.4m
Operating profit NOK 1.2m
Equity NOK 4.6m
Incorporated 2013
Employees 26
Share capital NOK 100,000

HAUGLAND AUTOMOBIL AS is registered as a limited company in Osterøy, Vestland with organisation number 911695170. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2013 and has 26 registered employees. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Drift av bilverksted, omsetning av biler og rekvisita, samt annen virksomhet som naturleg fell inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 38.4m in revenue and NOK 1.2m in operating profit.

Key figures · 2024

Revenue
NOK 38.4m
Operating profit
NOK 1.2m
Equity
NOK 4.6m
Est. value
NOK 7.0m

Financial health · 2024

Liquidity
1.52
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
43.6%
Very good
Equity as a share of total capital

Who owns HAUGLAND AUTOMOBIL AS?

HAUGLAND AUTO HOLDING AS
HAUGLAND AUTOMOBIL AS
NOK 38.4m rev. · NOK 1.2m profit

HAUGLAND AUTOMOBIL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HAUGLAND AUTOMOBIL AS

Who owns HAUGLAND AUTOMOBIL AS?

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

What is the revenue of HAUGLAND AUTOMOBIL AS?

HAUGLAND AUTOMOBIL AS had revenue of NOK 38.4m in 2024.

Who is the general manager of HAUGLAND AUTOMOBIL AS?

Frode Haugland is registered as general manager of HAUGLAND AUTOMOBIL AS.

Where is HAUGLAND AUTOMOBIL AS based?

HAUGLAND AUTOMOBIL AS has its business address in Valestrandsfossen.

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.