BIZTRAC BETA
Joinery installation

KI BYGG AS

Org. no. 936427316 Limited company (AS) Hole Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 548,000
Operating profit NOK −53,000
Equity NOK −23,000
Incorporated 2025
Employees 8
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−23k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−53k kr).
  • Nystiftet selskap Selskapet ble stiftet 2025-10-01.

KI BYGG AS is registered as a limited company in Hole, Buskerud with organisation number 936427316. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2025 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Renovere, ombygge, oppusning. Alt snekker arbeid.”. The most recent filed accounts, for the 2025 financial year, show NOK 548,000 in revenue and NOK −53,000 in operating profit.

Key figures · 2025

Revenue
NOK 548,000
Operating profit
NOK −53,000
Equity
NOK −23,000

Financial health · 2025

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

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

Who owns KI BYGG AS?

Ingus Krumins
KI BYGG AS
NOK 548,000 rev. · NOK −53,000 profit

KI BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KI BYGG AS

Who owns KI BYGG AS?

Ingus Krumins is the largest registered owner, with 100.0%.

What is the revenue of KI BYGG AS?

KI BYGG AS had revenue of NOK 548,000 in 2025.

Who is the general manager of KI BYGG AS?

Ingus Krumins is registered as general manager of KI BYGG AS.

Where is KI BYGG AS based?

KI BYGG AS has its business address in Krokkleiva.

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.