BIZTRAC BETA
Non-scheduled passenger transport by road

LYNGSALPAN BUSS AS

Org. no. 920349749 Limited company (AS) Lyngen Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 707,000
Operating profit NOK 24,000
Equity NOK 52,000
Incorporated 2018
Share capital NOK 30,000

LYNGSALPAN BUSS AS is registered as a limited company in Lyngen, Troms with organisation number 920349749. The business is classified under non-scheduled passenger transport by road (NACE 49.320). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investere i og drive med transport, befraktning og persontransport samt deltakelse i annen forretningsvirksomhet innen samme bransje.”. The most recent filed accounts, for the 2025 financial year, show NOK 707,000 in revenue and NOK 24,000 in operating profit.

Key figures · 2025

Revenue
NOK 707,000
Operating profit
NOK 24,000
Equity
NOK 52,000
Est. value
NOK 104,000

Financial health · 2025

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

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

Who owns LYNGSALPAN BUSS AS?

JØRN-RUNE WIKERØY
LYNGSALPAN BUSS AS
NOK 707,000 rev. · NOK 24,000 profit

LYNGSALPAN BUSS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LYNGSALPAN BUSS AS

Who owns LYNGSALPAN BUSS AS?

JØRN-RUNE WIKERØY is the largest registered owner, with 100.0%.

What is the revenue of LYNGSALPAN BUSS AS?

LYNGSALPAN BUSS AS had revenue of NOK 707,000 in 2025.

Who is the general manager of LYNGSALPAN BUSS AS?

Jørn-Rune Wikerøy is registered as general manager of LYNGSALPAN BUSS AS.

Where is LYNGSALPAN BUSS AS based?

LYNGSALPAN BUSS AS has its business address in Nord-Lenangen.

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.