BIZTRAC BETA
Freight transport by road

AXIS TRANSPORT AS

Org. no. 934039122 Limited company (AS) Melhus Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 512,000
Operating profit NOK 20,000
Equity NOK 44,000
Incorporated 2024
Share capital NOK 30,000

AXIS TRANSPORT AS is registered as a limited company in Melhus, Trøndelag with organisation number 934039122. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen godstransport på vei - 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 512,000 in revenue and NOK 20,000 in operating profit.

Key figures · 2024

Revenue
NOK 512,000
Operating profit
NOK 20,000
Equity
NOK 44,000
Est. value
NOK 86,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns AXIS TRANSPORT AS?

MANCAVE STUDIO AS
AXIS TRANSPORT AS
NOK 512,000 rev. · NOK 20,000 profit

AXIS TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AXIS TRANSPORT AS

Who owns AXIS TRANSPORT AS?

MANCAVE STUDIO AS is the largest registered owner, with 100.0%.

What is the revenue of AXIS TRANSPORT AS?

AXIS TRANSPORT AS had revenue of NOK 512,000 in 2024.

Who is the general manager of AXIS TRANSPORT AS?

Jostein Almåsbro is registered as general manager of AXIS TRANSPORT AS.

Where is AXIS TRANSPORT AS based?

AXIS TRANSPORT AS has its business address in Melhus.

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.