BIZTRAC BETA
Repair and maintenance of motor vehicles

NAMDAL BILSKADE AS

Org. no. 989823388 Limited company (AS) Namsos Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 71.1m
Operating profit NOK 4.5m
Equity NOK 9.1m
Incorporated 2006
Employees 56
Share capital NOK 1.0m

NAMDAL BILSKADE AS is registered as a limited company in Namsos, Trøndelag with organisation number 989823388. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2006 and has 56 registered employees. Registered share capital is NOK 1.0m, divided into 3450 shares. The company's stated purpose is: “Verksteddrift, bilutleie, omsetning av kjøretøy, pleie og vedlikehold av biler, båter, mc og caravan og andre produkter/ tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 71.1m in revenue and NOK 4.5m in operating profit.

Key figures · 2024

Revenue
NOK 71.1m
Operating profit
NOK 4.5m
Equity
NOK 9.1m
Est. value
NOK 22.1m

Financial health · 2024

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

Who owns NAMDAL BILSKADE AS?

BILSENTERET INVEST AS
NAMDAL BILSKADE AS
NOK 71.1m rev. · NOK 4.5m profit

NAMDAL BILSKADE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NAMDAL BILSKADE AS

Who owns NAMDAL BILSKADE AS?

BILSENTERET INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of NAMDAL BILSKADE AS?

NAMDAL BILSKADE AS had revenue of NOK 71.1m in 2024.

Who is the general manager of NAMDAL BILSKADE AS?

Thomas Hestmo is registered as general manager of NAMDAL BILSKADE AS.

Where is NAMDAL BILSKADE AS based?

NAMDAL BILSKADE AS has its business address in Namsos.

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.