BIZTRAC BETA
Plumbing installation

LANGESUND RØR AS

Org. no. 933256391 Limited company (AS) Bamble Incorporated 1983 Active
Ownership graph ↗
Revenue 2024 NOK 9.5m
Operating profit NOK 116,000
Equity NOK 1.5m
Incorporated 1983
Employees 7
Share capital NOK 40,000

LANGESUND RØR AS is registered as a limited company in Bamble, Telemark with organisation number 933256391. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 1983 and has 7 registered employees. Registered share capital is NOK 40,000, divided into 75 shares. The company's stated purpose is: “Rørleggervirksomhet og dertil alt som står i forbindelse med sådan virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.5m in revenue and NOK 116,000 in operating profit.

Key figures · 2024

Revenue
NOK 9.5m
Operating profit
NOK 116,000
Equity
NOK 1.5m
Est. value
NOK 951,000

Financial health · 2024

Liquidity
2.57
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
27.2%
Good
Equity as a share of total capital

Who owns LANGESUND RØR AS?

MAGNE RØNNINGSLAND HALVORSEN
LANGESUND RØR AS
NOK 9.5m rev. · NOK 116,000 profit

LANGESUND RØR AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LANGESUND RØR AS own?

LANGESUND RØR AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LANGESUND RØR AS

Who owns LANGESUND RØR AS?

MAGNE RØNNINGSLAND HALVORSEN is the largest registered owner, with 100.0%.

What is the revenue of LANGESUND RØR AS?

LANGESUND RØR AS had revenue of NOK 9.5m in 2024.

Who is the general manager of LANGESUND RØR AS?

Magne Rønningsland Halvorsen is registered as general manager of LANGESUND RØR AS.

Where is LANGESUND RØR AS based?

LANGESUND RØR AS has its business address in Stathelle.

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.