BIZTRAC BETA
Central agencies for goods and transportation procurement

LYNGDAL DROSJESENTRAL AS

Org. no. 932730294 Limited company (AS) Lyngdal Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 15.8m
Operating profit NOK 1.7m
Equity NOK 1.2m
Incorporated 2023
Employees 31
Share capital NOK 30,000

LYNGDAL DROSJESENTRAL AS is registered as a limited company in Lyngdal, Agder with organisation number 932730294. The business is classified under central agencies for goods and transportation procurement (NACE 52.211). The company was incorporated in 2023 and has 31 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drosje transport, Turvogn transport, Drift av Drosjesentral.”. The most recent filed accounts, for the 2024 financial year, show NOK 15.8m in revenue and NOK 1.7m in operating profit.

Key figures · 2024

Revenue
NOK 15.8m
Operating profit
NOK 1.7m
Equity
NOK 1.2m
Est. value
NOK 5.7m

Financial health · 2024

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

Who owns LYNGDAL DROSJESENTRAL AS?

GLENN ARVID HÅLAND
LYNGDAL DROSJESENTRAL AS
NOK 15.8m rev. · NOK 1.7m profit

LYNGDAL DROSJESENTRAL AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LYNGDAL DROSJESENTRAL AS

Who owns LYNGDAL DROSJESENTRAL AS?

GLENN ARVID HÅLAND is the largest registered owner, with 50.0%.

What is the revenue of LYNGDAL DROSJESENTRAL AS?

LYNGDAL DROSJESENTRAL AS had revenue of NOK 15.8m in 2024.

Who is the general manager of LYNGDAL DROSJESENTRAL AS?

Glenn Arvid Håland is registered as general manager of LYNGDAL DROSJESENTRAL AS.

Where is LYNGDAL DROSJESENTRAL AS based?

LYNGDAL DROSJESENTRAL AS has its business address in Lyngdal.

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.