BIZTRAC BETA
Repair and maintenance of motor vehicles

TYSNES BILSENTER AS

Org. no. 983989632 Limited company (AS) Tysnes Incorporated 2001 Active
Ownership graph ↗
Revenue 2024 NOK 11.8m
Operating profit NOK 573,000
Equity NOK 382,000
Incorporated 2001
Share capital NOK 225,000

TYSNES BILSENTER AS is registered as a limited company in Tysnes, Vestland with organisation number 983989632. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2001. Registered share capital is NOK 225,000, divided into 225 shares. The company's stated purpose is: “Drift og utleie av fast eiendom. Bilverksted og lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 11.8m in revenue and NOK 573,000 in operating profit.

Key figures · 2024

Revenue
NOK 11.8m
Operating profit
NOK 573,000
Equity
NOK 382,000
Est. value
NOK 2.0m

Financial health · 2024

Liquidity
1.14
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
9.9%
Weak
Equity as a share of total capital

Who owns TYSNES BILSENTER AS?

ATLE TORNES
TYSNES BILSENTER AS
NOK 11.8m rev. · NOK 573,000 profit

TYSNES BILSENTER AS has 3 registered shareholders:

All shareholders and roles →

Which companies does TYSNES BILSENTER AS own?

TYSNES BILSENTER AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TYSNES BILSENTER AS

Who owns TYSNES BILSENTER AS?

ATLE TORNES is the largest registered owner, with 33.3%.

What is the revenue of TYSNES BILSENTER AS?

TYSNES BILSENTER AS had revenue of NOK 11.8m in 2024.

Who is the general manager of TYSNES BILSENTER AS?

Vidar Lid is registered as general manager of TYSNES BILSENTER AS.

Where is TYSNES BILSENTER AS based?

TYSNES BILSENTER AS has its business address in Uggdal.

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.