BIZTRAC BETA
Joinery installation

KK BYGGSERVICE AS

Org. no. 921514204 Limited company (AS) Elverum Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 3.5m
Operating profit NOK −333,000
Equity NOK 99,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−333k kr).

KK BYGGSERVICE AS is registered as a limited company in Elverum, Innlandet with organisation number 921514204. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Bygg og anlegg, byggetjenester, rehabilitering, flislegging, gulvlegging, maling, snekring og sparkling. Renhold.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.5m in revenue and NOK −333,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.5m
Operating profit
NOK −333,000
Equity
NOK 99,000
Est. value
NOK 1.3m

Financial health · 2025

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

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

Who owns KK BYGGSERVICE AS?

KRZYSZTOF KWIECIEN
KK BYGGSERVICE AS
NOK 3.5m rev. · NOK −333,000 profit

KK BYGGSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KK BYGGSERVICE AS

Who owns KK BYGGSERVICE AS?

KRZYSZTOF KWIECIEN is the largest registered owner, with 100.0%.

What is the revenue of KK BYGGSERVICE AS?

KK BYGGSERVICE AS had revenue of NOK 3.5m in 2024.

Who is the general manager of KK BYGGSERVICE AS?

Krzysztof Kwiecien is registered as general manager of KK BYGGSERVICE AS.

Where is KK BYGGSERVICE AS based?

KK BYGGSERVICE AS has its business address in Elverum.

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.