biztrac. BETA
COMPANY REGISTER PROFILE
928620891 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Other tour operator activities

LAPOINT TRAVELS AS

Org. no. 928620891 Limited company (AS) Bærum Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 117.1m
Operating profit NOK 8.0m
Equity NOK 15.9m
Incorporated 2021
Share capital NOK 90,000

LAPOINT TRAVELS AS is registered as a limited company in Bærum, Akershus with organisation number 928620891. The business is classified under other tour operator activities (NACE 79.122). The company was incorporated in 2021. Registered share capital is NOK 90,000, divided into 100 shares. The company's stated purpose is: “Formidle reisevirksomhet, markedsføre og produktutvikle reisetjenester, utføre turoperatørvirksomheter og betjene andre reisebyråer og annen virksomhet som naturlig hører inn under dette, samt investere i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 117.1m in revenue and NOK 8.0m in operating profit.

Former names: (NYE) LAPOINT TRAVELS AS

Key figures · 2025

Revenue
NOK 117.1m
▲ +6 %
Operating profit
NOK 8.0m
▼ −11 %
Equity
NOK 15.9m
▲ +69 %
Est. value
NOK 44.0m

Financial health · 2025

Liquidity
1.59
Good
Current assets ÷ current liabilities
Profitability
29.3%
Very good
Return on total assets
Solidity
37.3%
Good
Equity as a share of total capital

Who owns LAPOINT TRAVELS AS?

LAPOINT TRAVELS AS
NOK 117.1m rev. · NOK 8.0m profit

LAPOINT TRAVELS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LAPOINT TRAVELS AS

Who owns LAPOINT TRAVELS AS?

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

What is the revenue of LAPOINT TRAVELS AS?

LAPOINT TRAVELS AS had revenue of NOK 117.1m in 2025.

Where is LAPOINT TRAVELS AS based?

LAPOINT TRAVELS AS has its business address in Fornebu.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.