BIZTRAC BETA
Non-scheduled passenger transport by road

LÅGEN TUR AS

Org. no. 897488612 Limited company (AS) Larvik Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 495,000
Operating profit NOK 143,000
Equity NOK 642,000
Incorporated 2011
Share capital NOK 100,000

LÅGEN TUR AS is registered as a limited company in Larvik, Vestfold with organisation number 897488612. The business is classified under non-scheduled passenger transport by road (NACE 49.320). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Turbilvirksomhet, turoperatør, reisebyråvirksomhet, servering og aktiviteter innen reiselivsnæringen. Videre ønsker selskapet å drive med varetransport, drosjevirksomhet, entreprenørvirksomhet, og det som hermed står i forbindelse, samt eie og investere i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 495,000 in revenue and NOK 143,000 in operating profit.

Key figures · 2025

Revenue
NOK 495,000
Operating profit
NOK 143,000
Equity
NOK 642,000
Est. value
NOK 785,000

Financial health · 2025

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

Who owns LÅGEN TUR AS?

OLE JØRGEN NORDRUM
LÅGEN TUR AS
NOK 495,000 rev. · NOK 143,000 profit

LÅGEN TUR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LÅGEN TUR AS

Who owns LÅGEN TUR AS?

OLE JØRGEN NORDRUM is the largest registered owner, with 100.0%.

What is the revenue of LÅGEN TUR AS?

LÅGEN TUR AS had revenue of NOK 495,000 in 2025.

Who is the general manager of LÅGEN TUR AS?

Ole Jørgen Nordrum is registered as general manager of LÅGEN TUR AS.

Where is LÅGEN TUR AS based?

LÅGEN TUR AS has its business address in Kvelde.

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.