BIZTRAC BETA
Repair and maintenance of motor vehicles

LANGØRGEN HOLDING AS

Org. no. 912553523 Limited company (AS) Trondheim Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK 142,000
Equity NOK 6.8m
Incorporated 2013
Share capital NOK 100,000

LANGØRGEN HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 912553523. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2013. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive investeringsvirksomhet, herunder investering i aksjer, obligasjoner, selskapsandeler, utlånsvirksomhet eller annen virksomhet, selv eller gjennom hel- eller deleide selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK 142,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK 142,000
Equity
NOK 6.8m
Est. value
NOK 3.9m

Financial health · 2024

Liquidity
0.02
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
31.9%
Good
Equity as a share of total capital

Who owns LANGØRGEN HOLDING AS?

STÅLE LANGØRGEN
LANGØRGEN HOLDING AS
NOK 1.1m rev. · NOK 142,000 profit

LANGØRGEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LANGØRGEN HOLDING AS own?

LANGØRGEN HOLDING AS holds stakes in 8 companies:

See the full ownership structure →

Frequently asked questions about LANGØRGEN HOLDING AS

Who owns LANGØRGEN HOLDING AS?

STÅLE LANGØRGEN is the largest registered owner, with 100.0%.

What is the revenue of LANGØRGEN HOLDING AS?

LANGØRGEN HOLDING AS had revenue of NOK 1.1m in 2024.

Where is LANGØRGEN HOLDING AS based?

LANGØRGEN HOLDING AS has its business address in Heimdal.

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.