BIZTRAC BETA
Repair and maintenance of motor vehicles

SVARSTAD BIL AS

Org. no. 997770544 Limited company (AS) Larvik Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 10.9m
Operating profit NOK 1.1m
Equity NOK 4.3m
Incorporated 2011
Employees 7
Share capital NOK 100,000

SVARSTAD BIL AS is registered as a limited company in Larvik, Vestfold with organisation number 997770544. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2011 and has 7 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Reparasjoner av biler og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 10.9m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 10.9m
Operating profit
NOK 1.1m
Equity
NOK 4.3m
Est. value
NOK 7.2m

Financial health · 2025

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

Who owns SVARSTAD BIL AS?

JON ANDREAS HALVORSEN
SVARSTAD BIL AS
NOK 10.9m rev. · NOK 1.1m profit

SVARSTAD BIL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SVARSTAD BIL AS own?

SVARSTAD BIL AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SVARSTAD BIL AS

Who owns SVARSTAD BIL AS?

JON ANDREAS HALVORSEN is the largest registered owner, with 100.0%.

What is the revenue of SVARSTAD BIL AS?

SVARSTAD BIL AS had revenue of NOK 10.9m in 2025.

Who is the general manager of SVARSTAD BIL AS?

Jon Andreas Halvorsen is registered as general manager of SVARSTAD BIL AS.

Where is SVARSTAD BIL AS based?

SVARSTAD BIL AS has its business address in Svarstad.

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.