BIZTRAC BETA
Repair and maintenance of motor vehicles

K 2000 BILPLEIE BERGEN AS

Org. no. 989191535 Limited company (AS) Bergen Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 3.8m
Operating profit NOK 549,000
Equity NOK 568,000
Incorporated 2005
Share capital NOK 100,000

K 2000 BILPLEIE BERGEN AS is registered as a limited company in Bergen, Vestland with organisation number 989191535. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Vedlikehold, reparasjon, kjøp og salg av motorvogner, båter mv., samt deltagelse i andre selskaper, samt hva som står i forbindelse hermed.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.8m in revenue and NOK 549,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.8m
Operating profit
NOK 549,000
Equity
NOK 568,000
Est. value
NOK 2.3m

Financial health · 2025

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

Who owns K 2000 BILPLEIE BERGEN AS?

K 2000 INVEST AS
K 2000 BILPLEIE BERGEN AS
NOK 3.8m rev. · NOK 549,000 profit

K 2000 BILPLEIE BERGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about K 2000 BILPLEIE BERGEN AS

Who owns K 2000 BILPLEIE BERGEN AS?

K 2000 INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of K 2000 BILPLEIE BERGEN AS?

K 2000 BILPLEIE BERGEN AS had revenue of NOK 3.8m in 2025.

Who is the general manager of K 2000 BILPLEIE BERGEN AS?

Arild Pettersen is registered as general manager of K 2000 BILPLEIE BERGEN AS.

Where is K 2000 BILPLEIE BERGEN AS based?

K 2000 BILPLEIE BERGEN AS has its business address in Bergen.

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.