BIZTRAC BETA
Freight transport by road

ARVE AASEN TRANSPORT AS

Org. no. 892841802 Limited company (AS) Gloppen Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 1.3m
Operating profit NOK 65,000
Equity NOK −72,000
Incorporated 2008
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−72k kr).

ARVE AASEN TRANSPORT AS is registered as a limited company in Gloppen, Vestland with organisation number 892841802. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Transport av mjøl og gods på vei.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.3m in revenue and NOK 65,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.3m
Operating profit
NOK 65,000
Equity
NOK −72,000
Est. value
NOK 441,000

Financial health · 2024

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

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

Who owns ARVE AASEN TRANSPORT AS?

ARVE JAN AASEN
ARVE AASEN TRANSPORT AS
NOK 1.3m rev. · NOK 65,000 profit

ARVE AASEN TRANSPORT AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about ARVE AASEN TRANSPORT AS

Who owns ARVE AASEN TRANSPORT AS?

ARVE JAN AASEN is the largest registered owner, with 70.0%.

What is the revenue of ARVE AASEN TRANSPORT AS?

ARVE AASEN TRANSPORT AS had revenue of NOK 1.3m in 2024.

Who is the general manager of ARVE AASEN TRANSPORT AS?

Odd Arild Aasen is registered as general manager of ARVE AASEN TRANSPORT AS.

Where is ARVE AASEN TRANSPORT AS based?

ARVE AASEN TRANSPORT AS has its business address in Hyen.

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.