BIZTRAC BETA
Repair and maintenance of motor vehicles

BILSKADESERVICE AS

Org. no. 956606586 Limited company (AS) Kristiansand Incorporated 1990 Active
Ownership graph ↗
Revenue 2025 NOK 6.2m
Operating profit NOK 674,000
Equity NOK 515,000
Incorporated 1990
Employees 5
Share capital NOK 200,000

BILSKADESERVICE AS is registered as a limited company in Kristiansand, Agder with organisation number 956606586. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 1990 and has 5 registered employees. Registered share capital is NOK 200,000, divided into 2000 shares. The company's stated purpose is: “Drive lakkering og oppretting, handel og alt hva hermed står i forbindelse herunder å delta i andre selskap med samme eller lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.2m in revenue and NOK 674,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.2m
Operating profit
NOK 674,000
Equity
NOK 515,000
Est. value
NOK 2.8m

Financial health · 2025

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

Who owns BILSKADESERVICE AS?

MJA BILSERVICE AS
BILSKADESERVICE AS
NOK 6.2m rev. · NOK 674,000 profit

BILSKADESERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BILSKADESERVICE AS

Who owns BILSKADESERVICE AS?

MJA BILSERVICE AS is the largest registered owner, with 50.0%.

What is the revenue of BILSKADESERVICE AS?

BILSKADESERVICE AS had revenue of NOK 6.2m in 2025.

Who is the general manager of BILSKADESERVICE AS?

Geir Greipsland is registered as general manager of BILSKADESERVICE AS.

Where is BILSKADESERVICE AS based?

BILSKADESERVICE AS has its business address in Kristiansand S.

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.