BIZTRAC BETA
Freight transport by road

A STEEN TRANSPORT AS

Org. no. 984670494 Limited company (AS) Høylandet Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 9.6m
Operating profit NOK 787,000
Equity NOK 4.9m
Incorporated 2002
Employees 7
Share capital NOK 100,000

Signals

1 flags
  • Nylig endring 2026-07-26 Adresseendring registrert 2026-07-26.

A STEEN TRANSPORT AS is registered as a limited company in Høylandet, Trøndelag with organisation number 984670494. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2002 and has 7 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Transport og annen virksomhet som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.6m in revenue and NOK 787,000 in operating profit.

Key figures · 2024

Revenue
NOK 9.6m
Operating profit
NOK 787,000
Equity
NOK 4.9m
Est. value
NOK 5.3m

Financial health · 2024

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

Who owns A STEEN TRANSPORT AS?

NILS ARNE STEEN
A STEEN TRANSPORT AS
NOK 9.6m rev. · NOK 787,000 profit

A STEEN TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about A STEEN TRANSPORT AS

Who owns A STEEN TRANSPORT AS?

NILS ARNE STEEN is the largest registered owner, with 100.0%.

What is the revenue of A STEEN TRANSPORT AS?

A STEEN TRANSPORT AS had revenue of NOK 9.6m in 2024.

Who is the general manager of A STEEN TRANSPORT AS?

Nils Arne Steen is registered as general manager of A STEEN TRANSPORT AS.

Where is A STEEN TRANSPORT AS based?

A STEEN TRANSPORT AS has its business address in Høylandet.

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.