BIZTRAC BETA
On-demand passenger transport service activities by vehicle with driver

LAKSELV TAXI AS

Org. no. 996657256 Limited company (AS) Porsanger Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 4.9m
Operating profit NOK 74,000
Equity NOK 515,000
Incorporated 2011
Employees 22
Share capital NOK 171,000

LAKSELV TAXI AS is registered as a limited company in Porsanger, Finnmark with organisation number 996657256. The business is classified under on-demand passenger transport service activities by vehicle with driver (NACE 49.330). The company was incorporated in 2011 and has 22 registered employees. Registered share capital is NOK 171,000, divided into 171 shares. The company's stated purpose is: “Persontransport.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.9m in revenue and NOK 74,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.9m
Operating profit
NOK 74,000
Equity
NOK 515,000
Est. value
NOK 429,000

Financial health · 2024

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

Who owns LAKSELV TAXI AS?

RUNE JOHNSEN
LAKSELV TAXI AS
NOK 4.9m rev. · NOK 74,000 profit

LAKSELV TAXI AS has 3 registered shareholders:

All shareholders and roles →

Which companies does LAKSELV TAXI AS own?

LAKSELV TAXI AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LAKSELV TAXI AS

Who owns LAKSELV TAXI AS?

RUNE JOHNSEN is the largest registered owner, with 33.3%.

What is the revenue of LAKSELV TAXI AS?

LAKSELV TAXI AS had revenue of NOK 4.9m in 2024.

Who is the general manager of LAKSELV TAXI AS?

Rune Johnsen is registered as general manager of LAKSELV TAXI AS.

Where is LAKSELV TAXI AS based?

LAKSELV TAXI AS has its business address in Lakselv.

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.