BIZTRAC BETA
Repair and maintenance of motor vehicles

FINNMARK BILSKADESENTER AS

Org. no. 918092986 Limited company (AS) Hammerfest Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 12.8m
Operating profit NOK 17,000
Equity NOK 5.8m
Incorporated 2016
Employees 7
Share capital NOK 300,000

FINNMARK BILSKADESENTER AS is registered as a limited company in Hammerfest, Finnmark with organisation number 918092986. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2016 and has 7 registered employees. Registered share capital is NOK 300,000, divided into 600 shares. The company's stated purpose is: “Reparasjon av karosseri og lakkering av personbiler.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.8m in revenue and NOK 17,000 in operating profit.

Key figures · 2024

Revenue
NOK 12.8m
Operating profit
NOK 17,000
Equity
NOK 5.8m
Est. value
NOK 3.8m

Financial health · 2024

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

Who owns FINNMARK BILSKADESENTER AS?

L.H INVEST AS
FINNMARK BILSKADESENTER AS
NOK 12.8m rev. · NOK 17,000 profit

FINNMARK BILSKADESENTER AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about FINNMARK BILSKADESENTER AS

Who owns FINNMARK BILSKADESENTER AS?

L.H INVEST AS is the largest registered owner, with 25.0%.

What is the revenue of FINNMARK BILSKADESENTER AS?

FINNMARK BILSKADESENTER AS had revenue of NOK 12.8m in 2024.

Who is the general manager of FINNMARK BILSKADESENTER AS?

Lars Arne Hauan is registered as general manager of FINNMARK BILSKADESENTER AS.

Where is FINNMARK BILSKADESENTER AS based?

FINNMARK BILSKADESENTER AS has its business address in Hammerfest.

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.