biztrac. BETA
COMPANY REGISTER PROFILE
917810346 ORG. NO. 2025 ACCOUNTS 11 SECTIONS
Active UPDATED 03.10.2026
Plumbing installation

K LUND AS

Org. no. 917810346 Limited company (AS) Trondheim Incorporated 1964 Active
Ownership graph ↗
Revenue 2025 NOK 237.9m
Operating profit NOK 6.0m
Equity NOK 87.1m
Incorporated 1964
Employees 138
Share capital NOK 2.0m

K LUND AS is registered as a limited company in Trondheim, Trøndelag with organisation number 917810346. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 1964 and has 138 registered employees. Registered share capital is NOK 2.0m. The company's stated purpose is: “Rørleggervirksomhet, handel, produksjon og deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 237.9m in revenue and NOK 6.0m in operating profit.

Former names: K LUND AS RØRLEGGERFIRMA

Key figures · 2025

Revenue
NOK 237.9m
▼ −1 %
Operating profit
NOK 6.0m
▼ −60 %
Equity
NOK 87.1m
▲ +0 %
Est. value
NOK 77.0m

Financial health · 2025

Liquidity
2.66
Very good
Current assets ÷ current liabilities
Profitability
7.5%
Satisfactory
Return on total assets
Solidity
60.3%
Very good
Equity as a share of total capital

Who owns K LUND AS?

K LUND AS has 3 registered shareholders:

All shareholders and roles →

Which companies does K LUND AS own?

K LUND AS holds stakes in 8 companies:

See the full ownership structure →

Group structure

K LUND AS er morselskap for 1 datterselskap:

Frequently asked questions about K LUND AS

Who owns K LUND AS?

MORTEN KORSNES AS is the largest registered owner, with 59.4%.

What is the revenue of K LUND AS?

K LUND AS had revenue of NOK 237.9m in 2025.

Who is the general manager of K LUND AS?

Torkild Korsnes is registered as general manager of K LUND AS.

Where is K LUND AS based?

K LUND AS has its business address in Trondheim.

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.