BIZTRAC BETA
Other technical consultancy

NORSK DAMTEKNIKK AS

Org. no. 833924702 Limited company (AS) Tokke Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 576,000
Operating profit NOK 4,000
Equity NOK 48,000
Incorporated 2024
Share capital NOK 30,000

NORSK DAMTEKNIKK AS is registered as a limited company in Tokke, Telemark with organisation number 833924702. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen ingeniørarbeid - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 576,000 in revenue and NOK 4,000 in operating profit.

Key figures · 2025

Revenue
NOK 576,000
Operating profit
NOK 4,000
Equity
NOK 48,000
Est. value
NOK 54,000

Financial health · 2025

Liquidity
1.25
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
19.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns NORSK DAMTEKNIKK AS?

KNUT SKJÆVESLAND
NORSK DAMTEKNIKK AS
NOK 576,000 rev. · NOK 4,000 profit

NORSK DAMTEKNIKK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NORSK DAMTEKNIKK AS

Who owns NORSK DAMTEKNIKK AS?

KNUT SKJÆVESLAND is the largest registered owner, with 50.0%.

What is the revenue of NORSK DAMTEKNIKK AS?

NORSK DAMTEKNIKK AS had revenue of NOK 576,000 in 2025.

Who is the general manager of NORSK DAMTEKNIKK AS?

Bjørn Bergheim is registered as general manager of NORSK DAMTEKNIKK AS.

Where is NORSK DAMTEKNIKK AS based?

NORSK DAMTEKNIKK AS has its business address in Dalen.

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.