BIZTRAC BETA
Other passenger transport in coastal waters

LISE AS

Org. no. 986336958 Limited company (AS) Trondheim Incorporated 2003 Active
Ownership graph ↗
Revenue 2025 NOK 3.9m
Operating profit NOK 619,000
Equity NOK 494,000
Incorporated 2003
Employees 5
Share capital NOK 100,000

LISE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 986336958. The business is classified under other passenger transport in coastal waters (NACE 50.109). The company was incorporated in 2003 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive person- og godstransport på sjø og land. Samt kjøp, salg og utleie av bil, båt, tilhenger, maskiner og eiendom samt det som naturlig hører til. Selskapet kan også drive med kjøp og salg av pyrotekniske produkter. Selskap kan eie, kjøpe og selge aksjer og verdipapirer i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.9m in revenue and NOK 619,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.9m
Operating profit
NOK 619,000
Equity
NOK 494,000
Est. value
NOK 2.1m

Financial health · 2025

Liquidity
1.59
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
35.2%
Good
Equity as a share of total capital

Who owns LISE AS?

RONO HOLDING AS
LISE AS
NOK 3.9m rev. · NOK 619,000 profit

LISE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LISE AS

Who owns LISE AS?

RONO HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of LISE AS?

LISE AS had revenue of NOK 3.9m in 2025.

Who is the general manager of LISE AS?

Roy Viktor Nordskag is registered as general manager of LISE AS.

Where is LISE AS based?

LISE AS has its business address in Trondheim.

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.