BIZTRAC BETA
Freight transport by road

STENSLAND TRANSPORT AS

Org. no. 930284459 Limited company (AS) Tromsø Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 6.0m
Operating profit NOK 22,000
Equity NOK 212,000
Incorporated 2022
Share capital NOK 30,000

STENSLAND TRANSPORT AS is registered as a limited company in Tromsø, Troms with organisation number 930284459. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge tjenester og varer innen transport og anlegg, og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.0m in revenue and NOK 22,000 in operating profit.

Key figures · 2024

Revenue
NOK 6.0m
Operating profit
NOK 22,000
Equity
NOK 212,000
Est. value
NOK 180,000

Financial health · 2024

Liquidity
0.63
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
20.1%
Good
Equity as a share of total capital

Who owns STENSLAND TRANSPORT AS?

CASITA INVEST AS
STENSLAND TRANSPORT AS
NOK 6.0m rev. · NOK 22,000 profit

STENSLAND TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STENSLAND TRANSPORT AS

Who owns STENSLAND TRANSPORT AS?

CASITA INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of STENSLAND TRANSPORT AS?

STENSLAND TRANSPORT AS had revenue of NOK 6.0m in 2024.

Who is the general manager of STENSLAND TRANSPORT AS?

Trond-Ivar Ellingsen Stensland is registered as general manager of STENSLAND TRANSPORT AS.

Where is STENSLAND TRANSPORT AS based?

STENSLAND TRANSPORT AS has its business address in Tromsdalen.

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.