BIZTRAC BETA
Repair and maintenance of motor vehicles

BILHUSET FØRDE AS

Org. no. 994271725 Limited company (AS) Sunnfjord Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 200.4m
Operating profit NOK 2.7m
Equity NOK 13.6m
Incorporated 2009
Employees 19
Share capital NOK 1.1m

BILHUSET FØRDE AS is registered as a limited company in Sunnfjord, Vestland with organisation number 994271725. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2009 and has 19 registered employees. Registered share capital is NOK 1.1m, divided into 2200 shares. The company's stated purpose is: “Drive handel med biler og annen virksomhet som har sammenheng med dette. Virksomheten kan utøves av selskapet selv, av datterselskaper, eller gjennom deltakelse i andre selskaper eller i samarbeid med andre.”. The most recent filed accounts, for the 2025 financial year, show NOK 200.4m in revenue and NOK 2.7m in operating profit.

Key figures · 2025

Revenue
NOK 200.4m
Operating profit
NOK 2.7m
Equity
NOK 13.6m
Est. value
NOK 13.7m

Financial health · 2025

Liquidity
1.71
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
25.2%
Good
Equity as a share of total capital

Who owns BILHUSET FØRDE AS?

BILHOLDING AS
BILHUSET FØRDE AS
NOK 200.4m rev. · NOK 2.7m profit

BILHUSET FØRDE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BILHUSET FØRDE AS

Who owns BILHUSET FØRDE AS?

BILHOLDING AS is the largest registered owner, with 60.0%.

What is the revenue of BILHUSET FØRDE AS?

BILHUSET FØRDE AS had revenue of NOK 200.4m in 2025.

Who is the general manager of BILHUSET FØRDE AS?

Kim Ronny Lykkebø is registered as general manager of BILHUSET FØRDE AS.

Where is BILHUSET FØRDE AS based?

BILHUSET FØRDE AS has its business address in Førde.

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.