BIZTRAC BETA
Scheduled passenger transport by road

LYNGEN BUSS AS

Org. no. 915031765 Limited company (AS) Lyngen Incorporated 1977 Active
Ownership graph ↗
Revenue 2024 NOK 2.9m
Operating profit NOK 205,000
Equity NOK 5.0m
Incorporated 1977
Employees 9
Share capital NOK 550,000

Signals

1 flags
  • Nylig endring 2026-02-08 Adresseendring registrert 2026-02-08.

LYNGEN BUSS AS is registered as a limited company in Lyngen, Troms with organisation number 915031765. The business is classified under scheduled passenger transport by road (NACE 49.310). The company was incorporated in 1977 and has 9 registered employees. Registered share capital is NOK 550,000, divided into 550 shares. The company's stated purpose is: “Handel, transport- og agentur-virksomhet, og det som naturlig faller inn under dette, herunder å delta i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.9m in revenue and NOK 205,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.9m
Operating profit
NOK 205,000
Equity
NOK 5.0m
Est. value
NOK 3.5m

Financial health · 2024

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

Who owns LYNGEN BUSS AS?

HALVARD ELLING OLSEN
LYNGEN BUSS AS
NOK 2.9m rev. · NOK 205,000 profit

LYNGEN BUSS AS has 2 registered shareholders:

All shareholders and roles →

Which companies does LYNGEN BUSS AS own?

LYNGEN BUSS AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about LYNGEN BUSS AS

Who owns LYNGEN BUSS AS?

HALVARD ELLING OLSEN is the largest registered owner, with 54.5%.

What is the revenue of LYNGEN BUSS AS?

LYNGEN BUSS AS had revenue of NOK 2.9m in 2024.

Where is LYNGEN BUSS AS based?

LYNGEN BUSS AS has its business address in Lyngseidet.

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.