BIZTRAC BETA
COMPANY REGISTER PROFILE
932056674 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 02.09.2026
Freight transport by road

A. LANGKAAS & SØNN AS

Org. no. 932056674 Limited company (AS) Midt-Telemark Incorporated 1981 Active
Ownership graph ↗
Revenue 2025 NOK 10.8m
Operating profit NOK 2.0m
Equity NOK 16.3m
Incorporated 1981
Share capital NOK 100,000

A. LANGKAAS & SØNN AS is registered as a limited company in Midt-Telemark, Telemark with organisation number 932056674. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 1981. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Transport og virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 10.8m in revenue and NOK 2.0m in operating profit.

Former names: HALLVARD LANGKAAS & SØNNER AS

Key figures · 2025

Revenue
NOK 10.8m
▲ +15 %
Operating profit
NOK 2.0m
▲ +87 %
Equity
NOK 16.3m
▲ +12 %
Est. value
NOK 14.4m

Financial health · 2025

Liquidity
8.04
Very good
Current assets ÷ current liabilities
Profitability
13.7%
Good
Return on total assets
Solidity
92.0%
Very good
Equity as a share of total capital

Who owns A. LANGKAAS & SØNN AS?

A. LANGKAAS & SØNN AS
NOK 10.8m rev. · NOK 2.0m profit

A. LANGKAAS & SØNN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about A. LANGKAAS & SØNN AS

Who owns A. LANGKAAS & SØNN AS?

MORTEN LANGKAAS is the largest registered owner, with 100.0%.

What is the revenue of A. LANGKAAS & SØNN AS?

A. LANGKAAS & SØNN AS had revenue of NOK 10.8m in 2025.

Who is the general manager of A. LANGKAAS & SØNN AS?

Morten Langkaas is registered as general manager of A. LANGKAAS & SØNN AS.

Where is A. LANGKAAS & SØNN AS based?

A. LANGKAAS & SØNN AS has its business address in Bø I Telemark.

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

Report a problem

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