BIZTRAC BETA
On-demand passenger transport service activities by vehicle with driver

TAXI ØLENSVÅG AS

Org. no. 918652302 Limited company (AS) Vindafjord Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 8.5m
Operating profit NOK 1.8m
Equity NOK 2.7m
Incorporated 2017
Employees 13
Share capital NOK 50,000

TAXI ØLENSVÅG AS is registered as a limited company in Vindafjord, Rogaland with organisation number 918652302. The business is classified under on-demand passenger transport service activities by vehicle with driver (NACE 49.330). The company was incorporated in 2017 and has 13 registered employees. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Drosjekjøring - persontransport.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.5m in revenue and NOK 1.8m in operating profit.

Key figures · 2024

Revenue
NOK 8.5m
Operating profit
NOK 1.8m
Equity
NOK 2.7m
Est. value
NOK 6.7m

Financial health · 2024

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

Who owns TAXI ØLENSVÅG AS?

BJARTE BERGE
TAXI ØLENSVÅG AS
NOK 8.5m rev. · NOK 1.8m profit

TAXI ØLENSVÅG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TAXI ØLENSVÅG AS own?

TAXI ØLENSVÅG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TAXI ØLENSVÅG AS

Who owns TAXI ØLENSVÅG AS?

BJARTE BERGE is the largest registered owner, with 100.0%.

What is the revenue of TAXI ØLENSVÅG AS?

TAXI ØLENSVÅG AS had revenue of NOK 8.5m in 2024.

Who is the general manager of TAXI ØLENSVÅG AS?

Bjarte Berge is registered as general manager of TAXI ØLENSVÅG AS.

Where is TAXI ØLENSVÅG AS based?

TAXI ØLENSVÅG AS has its business address in Ølensvåg.

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.