BIZTRAC BETA
Freight transport by road

CHRISTENSEN TRANSPORT VESTBYGD AS

Org. no. 988201936 Limited company (AS) Harstad Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 14.3m
Operating profit NOK 2.4m
Equity NOK 3.2m
Incorporated 2005
Employees 7
Share capital NOK 100,000

CHRISTENSEN TRANSPORT VESTBYGD AS is registered as a limited company in Harstad, Troms with organisation number 988201936. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2005 and has 7 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Transportvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 14.3m in revenue and NOK 2.4m in operating profit.

Key figures · 2024

Revenue
NOK 14.3m
Operating profit
NOK 2.4m
Equity
NOK 3.2m
Est. value
NOK 7.1m

Financial health · 2024

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

Who owns CHRISTENSEN TRANSPORT VESTBYGD AS?

ALEX CHRISTENSEN
CHRISTENSEN TRANSPORT VESTBYGD AS
NOK 14.3m rev. · NOK 2.4m profit

CHRISTENSEN TRANSPORT VESTBYGD AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about CHRISTENSEN TRANSPORT VESTBYGD AS

Who owns CHRISTENSEN TRANSPORT VESTBYGD AS?

ALEX CHRISTENSEN is the largest registered owner, with 50.0%.

What is the revenue of CHRISTENSEN TRANSPORT VESTBYGD AS?

CHRISTENSEN TRANSPORT VESTBYGD AS had revenue of NOK 14.3m in 2024.

Who is the general manager of CHRISTENSEN TRANSPORT VESTBYGD AS?

Alex Christensen is registered as general manager of CHRISTENSEN TRANSPORT VESTBYGD AS.

Where is CHRISTENSEN TRANSPORT VESTBYGD AS based?

CHRISTENSEN TRANSPORT VESTBYGD AS has its business address in Harstad.

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.