BIZTRAC BETA
Repair and maintenance of motor vehicles

VIGELAND BIL AS

Org. no. 979501528 Limited company (AS) Lindesnes Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 22.7m
Operating profit NOK 1.1m
Equity NOK 2.9m
Incorporated 1998
Employees 14
Share capital NOK 100,000

VIGELAND BIL AS is registered as a limited company in Lindesnes, Agder with organisation number 979501528. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 1998 and has 14 registered employees. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Bilverksted, kjøp og salg av biler, erverv og drift av faste eiendommer og alt hva som herved står i forbindelse, herunder gjennom aksjetegning eller på annen måte å delta i andre selskaper eller foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 22.7m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 22.7m
Operating profit
NOK 1.1m
Equity
NOK 2.9m
Est. value
NOK 5.3m

Financial health · 2024

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

Who owns VIGELAND BIL AS?

VIGELAND BIL INVEST AS
VIGELAND BIL AS
NOK 22.7m rev. · NOK 1.1m profit

VIGELAND BIL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VIGELAND BIL AS

Who owns VIGELAND BIL AS?

VIGELAND BIL INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of VIGELAND BIL AS?

VIGELAND BIL AS had revenue of NOK 22.7m in 2024.

Who is the general manager of VIGELAND BIL AS?

Kjell Gunnar Sveinall is registered as general manager of VIGELAND BIL AS.

Where is VIGELAND BIL AS based?

VIGELAND BIL AS has its business address in Lindesnes.

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.