BIZTRAC BETA
Construction of residential and non-residential buildings

KN HÅNDVERK AS

Org. no. 918829350 Limited company (AS) Ringerike Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 6.9m
Operating profit NOK 595,000
Equity NOK 504,000
Incorporated 2017
Employees 8
Share capital NOK 30,000

KN HÅNDVERK AS is registered as a limited company in Ringerike, Buskerud with organisation number 918829350. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2017 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Oppføring av bygninger-ny bygg, tilbygg, rehabilitering, oppussing, samt snekker, tømrer, murer, malertjenester, blikkenslager, taktekking.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.9m in revenue and NOK 595,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.9m
Operating profit
NOK 595,000
Equity
NOK 504,000
Est. value
NOK 2.2m

Financial health · 2024

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

Who owns KN HÅNDVERK AS?

RADOSLAW KRZYSZTOF NAWROCKI
KN HÅNDVERK AS
NOK 6.9m rev. · NOK 595,000 profit

KN HÅNDVERK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KN HÅNDVERK AS

Who owns KN HÅNDVERK AS?

RADOSLAW KRZYSZTOF NAWROCKI is the largest registered owner, with 100.0%.

What is the revenue of KN HÅNDVERK AS?

KN HÅNDVERK AS had revenue of NOK 6.9m in 2025.

Who is the general manager of KN HÅNDVERK AS?

Radoslaw Krzysztof Nawrocki is registered as general manager of KN HÅNDVERK AS.

Where is KN HÅNDVERK AS based?

KN HÅNDVERK AS has its business address in Hønefoss.

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.