BIZTRAC BETA
Freight transport by road

NYLØKKEN TRANSPORT AS

Org. no. 911684985 Limited company (AS) Lesja Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 777,000
Operating profit NOK −542,000
Equity NOK 19.8m
Incorporated 2013
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−542k kr).

NYLØKKEN TRANSPORT AS is registered as a limited company in Lesja, Innlandet with organisation number 911684985. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Transport og alle slags tjenester som naturlig hører til dette, og deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 777,000 in revenue and NOK −542,000 in operating profit.

Key figures · 2024

Revenue
NOK 777,000
Operating profit
NOK −542,000
Equity
NOK 19.8m
Est. value
NOK 10.3m

Financial health · 2024

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

Who owns NYLØKKEN TRANSPORT AS?

KJELL JON NYLØKKEN
NYLØKKEN TRANSPORT AS
NOK 777,000 rev. · NOK −542,000 profit

NYLØKKEN TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NYLØKKEN TRANSPORT AS

Who owns NYLØKKEN TRANSPORT AS?

KJELL JON NYLØKKEN is the largest registered owner, with 100.0%.

What is the revenue of NYLØKKEN TRANSPORT AS?

NYLØKKEN TRANSPORT AS had revenue of NOK 777,000 in 2024.

Who is the general manager of NYLØKKEN TRANSPORT AS?

Kjell Jon Nyløkken is registered as general manager of NYLØKKEN TRANSPORT AS.

Where is NYLØKKEN TRANSPORT AS based?

NYLØKKEN TRANSPORT AS has its business address in Lesja.

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.