BIZTRAC BETA
Non-scheduled passenger transport by road

EVENSEN BUSSREISER AS

Org. no. 976912403 Limited company (AS) Kvæfjord Incorporated 1996 Active
Ownership graph ↗
Revenue 2025 NOK 14.2m
Operating profit NOK 1.6m
Equity NOK 16.7m
Incorporated 1996
Employees 12
Share capital NOK 550,000

EVENSEN BUSSREISER AS is registered as a limited company in Kvæfjord, Troms with organisation number 976912403. The business is classified under non-scheduled passenger transport by road (NACE 49.320). The company was incorporated in 1996 and has 12 registered employees. Registered share capital is NOK 550,000, divided into 550 shares. The company's stated purpose is: “Transporttjenester. Samt alt som står i forbindelse derved. Likeledes gjøre seg delaktig i annen forretningsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 14.2m in revenue and NOK 1.6m in operating profit.

Key figures · 2025

Revenue
NOK 14.2m
Operating profit
NOK 1.6m
Equity
NOK 16.7m
Est. value
NOK 14.5m

Financial health · 2025

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

Who owns EVENSEN BUSSREISER AS?

DAG JOHAN EVENSEN
EVENSEN BUSSREISER AS
NOK 14.2m rev. · NOK 1.6m profit

EVENSEN BUSSREISER AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about EVENSEN BUSSREISER AS

Who owns EVENSEN BUSSREISER AS?

DAG JOHAN EVENSEN is the largest registered owner, with 57.3%.

What is the revenue of EVENSEN BUSSREISER AS?

EVENSEN BUSSREISER AS had revenue of NOK 14.2m in 2025.

Who is the general manager of EVENSEN BUSSREISER AS?

Dag Johan Evensen is registered as general manager of EVENSEN BUSSREISER AS.

Where is EVENSEN BUSSREISER AS based?

EVENSEN BUSSREISER AS has its business address in Borkenes.

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.