BIZTRAC BETA
Freight transport by road

LØKEN TRANSPORT AS

Org. no. 933578534 Limited company (AS) Hustadvika Incorporated 1985 Active
Ownership graph ↗
Revenue 2024 NOK 11.8m
Operating profit NOK −1.8m
Equity NOK 358,000
Incorporated 1985
Employees 11
Share capital NOK 150,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,8 mill kr).

LØKEN TRANSPORT AS is registered as a limited company in Hustadvika, Møre og Romsdal with organisation number 933578534. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 1985 and has 11 registered employees. Registered share capital is NOK 150,000. The company's stated purpose is: “Transportvirksomhet og alt som står i forbindelse med dette, herunder deltagelse i andre selskaper med liknende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 11.8m in revenue and NOK −1.8m in operating profit.

Key figures · 2024

Revenue
NOK 11.8m
Operating profit
NOK −1.8m
Equity
NOK 358,000
Est. value
NOK 5.0m

Financial health · 2024

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

Who owns LØKEN TRANSPORT AS?

PER INGVAR LØKEN
LØKEN TRANSPORT AS
NOK 11.8m rev. · NOK −1.8m profit

LØKEN TRANSPORT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LØKEN TRANSPORT AS

Who owns LØKEN TRANSPORT AS?

PER INGVAR LØKEN is the largest registered owner, with 50.0%.

What is the revenue of LØKEN TRANSPORT AS?

LØKEN TRANSPORT AS had revenue of NOK 11.8m in 2024.

Who is the general manager of LØKEN TRANSPORT AS?

Albert Løken is registered as general manager of LØKEN TRANSPORT AS.

Where is LØKEN TRANSPORT AS based?

LØKEN TRANSPORT AS has its business address in Elnesvågen.

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.