BIZTRAC BETA
Freight transport by road

LYSE TRANSPORT AS

Org. no. 981622243 Limited company (AS) Stavanger Incorporated 2000 Active
Ownership graph ↗
Revenue 2025 NOK 13.5m
Operating profit NOK 2.2m
Equity NOK 20.7m
Incorporated 2000
Employees 6
Share capital NOK 1.5m

LYSE TRANSPORT AS is registered as a limited company in Stavanger, Rogaland with organisation number 981622243. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2000 and has 6 registered employees. Registered share capital is NOK 1.5m, divided into 1000 shares. The company's stated purpose is: “Drive med transporttjenester, samt hva som naturlig hører sammen med dette, herunder også deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 13.5m in revenue and NOK 2.2m in operating profit.

Key figures · 2025

Revenue
NOK 13.5m
Operating profit
NOK 2.2m
Equity
NOK 20.7m
Est. value
NOK 17.7m

Financial health · 2025

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

Who owns LYSE TRANSPORT AS?

RUNE LYSE
LYSE TRANSPORT AS
NOK 13.5m rev. · NOK 2.2m profit

LYSE TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LYSE TRANSPORT AS own?

LYSE TRANSPORT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LYSE TRANSPORT AS

Who owns LYSE TRANSPORT AS?

RUNE LYSE is the largest registered owner, with 100.0%.

What is the revenue of LYSE TRANSPORT AS?

LYSE TRANSPORT AS had revenue of NOK 13.5m in 2025.

Who is the general manager of LYSE TRANSPORT AS?

Rune Lyse is registered as general manager of LYSE TRANSPORT AS.

Where is LYSE TRANSPORT AS based?

LYSE TRANSPORT AS has its business address in Stavanger.

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.