biztrac. BETA
COMPANY REGISTER PROFILE
970926488 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Freight transport by road

LANGKÅS TRANSPORT AS

Org. no. 970926488 Limited company (AS) Midt-Telemark Incorporated 1994 Active
Ownership graph ↗
Revenue 2025 NOK 11.1m
Operating profit NOK 465,000
Equity NOK 7.7m
Incorporated 1994
Employees 6
Share capital NOK 100,000

LANGKÅS TRANSPORT AS is registered as a limited company in Midt-Telemark, Telemark with organisation number 970926488. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 1994 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Transport av varer og hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 11.1m in revenue and NOK 465,000 in operating profit.

Key figures · 2025

Revenue
NOK 11.1m
▼ −4 %
Operating profit
NOK 465,000
▲ +20 %
Equity
NOK 7.7m
▲ +3 %
Est. value
NOK 5.7m

Financial health · 2025

Liquidity
2.73
Very good
Current assets ÷ current liabilities
Profitability
2.8%
Weak
Return on total assets
Solidity
63.8%
Very good
Equity as a share of total capital

Who owns LANGKÅS TRANSPORT AS?

LANGKÅS TRANSPORT AS
NOK 11.1m rev. · NOK 465,000 profit

LANGKÅS TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LANGKÅS TRANSPORT AS

Who owns LANGKÅS TRANSPORT AS?

Birger Langkås is the largest registered owner, with 100.0%.

What is the revenue of LANGKÅS TRANSPORT AS?

LANGKÅS TRANSPORT AS had revenue of NOK 11.1m in 2025.

Who is the general manager of LANGKÅS TRANSPORT AS?

Birger Langkås is registered as general manager of LANGKÅS TRANSPORT AS.

Where is LANGKÅS TRANSPORT AS based?

LANGKÅS TRANSPORT 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 03.10.2026.

Report a problem

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