BIZTRAC BETA
Repair and maintenance of motor vehicles

BILPLEIESENTERET LARVIK AS

Org. no. 813519232 Limited company (AS) Larvik Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 13.8m
Operating profit NOK 1.3m
Equity NOK 1.9m
Incorporated 2014
Employees 9
Share capital NOK 30,000

BILPLEIESENTERET LARVIK AS is registered as a limited company in Larvik, Vestfold with organisation number 813519232. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2014 and has 9 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Bilpleie, båtpleie og caravan-relatert service samt vaktmestertjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 13.8m in revenue and NOK 1.3m in operating profit.

Key figures · 2024

Revenue
NOK 13.8m
Operating profit
NOK 1.3m
Equity
NOK 1.9m
Est. value
NOK 5.7m

Financial health · 2024

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

Who owns BILPLEIESENTERET LARVIK AS?

TOM EGIL FJELDHEIM
BILPLEIESENTERET LARVIK AS
NOK 13.8m rev. · NOK 1.3m profit

BILPLEIESENTERET LARVIK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BILPLEIESENTERET LARVIK AS

Who owns BILPLEIESENTERET LARVIK AS?

TOM EGIL FJELDHEIM is the largest registered owner, with 100.0%.

What is the revenue of BILPLEIESENTERET LARVIK AS?

BILPLEIESENTERET LARVIK AS had revenue of NOK 13.8m in 2024.

Who is the general manager of BILPLEIESENTERET LARVIK AS?

Tom Egil Fjeldheim is registered as general manager of BILPLEIESENTERET LARVIK AS.

Where is BILPLEIESENTERET LARVIK AS based?

BILPLEIESENTERET LARVIK AS has its business address in Larvik.

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.