BIZTRAC BETA
Retail sale of motor vehicle parts and accessories

BIL & BÅTREKVISITA AS

Org. no. 982335116 Limited company (AS) Holmestrand Incorporated 2000 Active
Ownership graph ↗
Revenue 2024 NOK 9.1m
Operating profit NOK 692,000
Equity NOK 3.7m
Incorporated 2000
Employees 6
Share capital NOK 400,000

BIL & BÅTREKVISITA AS is registered as a limited company in Holmestrand, Vestfold with organisation number 982335116. The business is classified under retail sale of motor vehicle parts and accessories (NACE 47.820). The company was incorporated in 2000 and has 6 registered employees. Registered share capital is NOK 400,000, divided into 1000 shares. The company's stated purpose is: “Handel og hva dermed står i forbindelse, herunder deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.1m in revenue and NOK 692,000 in operating profit.

Key figures · 2024

Revenue
NOK 9.1m
Operating profit
NOK 692,000
Equity
NOK 3.7m
Est. value
NOK 4.8m

Financial health · 2024

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

Who owns BIL & BÅTREKVISITA AS?

STINE VERONICA HUUN - VETTESTAD
BIL & BÅTREKVISITA AS
NOK 9.1m rev. · NOK 692,000 profit

BIL & BÅTREKVISITA AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about BIL & BÅTREKVISITA AS

Who owns BIL & BÅTREKVISITA AS?

STINE VERONICA HUUN - VETTESTAD is the largest registered owner, with 49.0%.

What is the revenue of BIL & BÅTREKVISITA AS?

BIL & BÅTREKVISITA AS had revenue of NOK 9.1m in 2024.

Who is the general manager of BIL & BÅTREKVISITA AS?

Kjell Stensrud is registered as general manager of BIL & BÅTREKVISITA AS.

Where is BIL & BÅTREKVISITA AS based?

BIL & BÅTREKVISITA AS has its business address in Holmestrand.

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.