BIZTRAC BETA
Repair and maintenance of motor vehicles

KONGSBERG BILSKADE AS

Org. no. 984936702 Limited company (AS) Kongsberg Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 54.2m
Operating profit NOK 5.0m
Equity NOK 3.7m
Incorporated 2002
Employees 21
Share capital NOK 1.2m

KONGSBERG BILSKADE AS is registered as a limited company in Kongsberg, Buskerud with organisation number 984936702. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2002 and has 21 registered employees. Registered share capital is NOK 1.2m, divided into 12000 shares. The company's stated purpose is: “Reparasjon og vedlikehold av kjøretøyer og alt som står i forbindelse med dette. Det skal være anledning til å eie aksjer og andeler i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 54.2m in revenue and NOK 5.0m in operating profit.

Key figures · 2024

Revenue
NOK 54.2m
Operating profit
NOK 5.0m
Equity
NOK 3.7m
Est. value
NOK 20.8m

Financial health · 2024

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

Who owns KONGSBERG BILSKADE AS?

MOBILE AS
KONGSBERG BILSKADE AS
NOK 54.2m rev. · NOK 5.0m profit

KONGSBERG BILSKADE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KONGSBERG BILSKADE AS

Who owns KONGSBERG BILSKADE AS?

MOBILE AS is the largest registered owner, with 50.0%.

What is the revenue of KONGSBERG BILSKADE AS?

KONGSBERG BILSKADE AS had revenue of NOK 54.2m in 2024.

Who is the general manager of KONGSBERG BILSKADE AS?

Pål André Fredriksen is registered as general manager of KONGSBERG BILSKADE AS.

Where is KONGSBERG BILSKADE AS based?

KONGSBERG BILSKADE AS has its business address in Kongsberg.

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.