BIZTRAC BETA
Plumbing installation

LYNG & LØBERG AS

Org. no. 914057507 Limited company (AS) Skien Incorporated 1984 Active
Ownership graph ↗
Revenue 2025 NOK 15.1m
Operating profit NOK 1.0m
Equity NOK 1.6m
Incorporated 1984
Employees 8
Share capital NOK 50,000

LYNG & LØBERG AS is registered as a limited company in Skien, Telemark with organisation number 914057507. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 1984 and has 8 registered employees. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Drive rørleggerforretning samt virksomhet som står i forbindelse med dette, og å gjøre seg interesert i andre foretagender innen samme bransje.”. The most recent filed accounts, for the 2025 financial year, show NOK 15.1m in revenue and NOK 1.0m in operating profit.

Key figures · 2025

Revenue
NOK 15.1m
Operating profit
NOK 1.0m
Equity
NOK 1.6m
Est. value
NOK 4.3m

Financial health · 2025

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

Who owns LYNG & LØBERG AS?

NOSSEK INVEST AS
LYNG & LØBERG AS
NOK 15.1m rev. · NOK 1.0m profit

LYNG & LØBERG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LYNG & LØBERG AS own?

LYNG & LØBERG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LYNG & LØBERG AS

Who owns LYNG & LØBERG AS?

NOSSEK INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of LYNG & LØBERG AS?

LYNG & LØBERG AS had revenue of NOK 15.1m in 2025.

Who is the general manager of LYNG & LØBERG AS?

Kristian Nossek is registered as general manager of LYNG & LØBERG AS.

Where is LYNG & LØBERG AS based?

LYNG & LØBERG AS has its business address in Skien.

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.