BIZTRAC BETA
Machining of metals

NORSK VANNSKJÆRING AS

Org. no. 985220514 Limited company (AS) Holmestrand Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 21.2m
Operating profit NOK 4.4m
Equity NOK 2.9m
Incorporated 2002
Employees 7
Share capital NOK 180,000

NORSK VANNSKJÆRING AS is registered as a limited company in Holmestrand, Vestfold with organisation number 985220514. The business is classified under machining of metals (NACE 25.530). The company was incorporated in 2002 and has 7 registered employees. Registered share capital is NOK 180,000, divided into 180000 shares. The company's stated purpose is: “Skjæring og salg av alle platematerialer samt deltakelse i annen tilknyttet virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 21.2m in revenue and NOK 4.4m in operating profit.

Key figures · 2025

Revenue
NOK 21.2m
Operating profit
NOK 4.4m
Equity
NOK 2.9m
Est. value
NOK 14.5m

Financial health · 2025

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

Who owns NORSK VANNSKJÆRING AS?

LSI AS
NORSK VANNSKJÆRING AS
NOK 21.2m rev. · NOK 4.4m profit

NORSK VANNSKJÆRING AS has 3 registered shareholders:

All shareholders and roles →

Group structure

NORSK VANNSKJÆRING AS er morselskap for 2 datterselskaper:

Frequently asked questions about NORSK VANNSKJÆRING AS

Who owns NORSK VANNSKJÆRING AS?

LSI AS is the largest registered owner, with 45.3%.

What is the revenue of NORSK VANNSKJÆRING AS?

NORSK VANNSKJÆRING AS had revenue of NOK 21.2m in 2025.

Who is the general manager of NORSK VANNSKJÆRING AS?

Lars Gulbrand Krogsund is registered as general manager of NORSK VANNSKJÆRING AS.

Where is NORSK VANNSKJÆRING AS based?

NORSK VANNSKJÆRING AS has its business address in Sande I Vestfold.

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.