BIZTRAC BETA
Refrigeration installation, heat pump installation and installation of fireplaces

KRUG HOLDING AS

Org. no. 923829660 Limited company (AS) Haugesund Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −21,000
Equity NOK −320,000
Incorporated 2019
Share capital NOK 3.8m

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−320k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−21k kr).

KRUG HOLDING AS is registered as a limited company in Haugesund, Rogaland with organisation number 923829660. The business is classified under refrigeration installation, heat pump installation and installation of fireplaces (NACE 43.222). The company was incorporated in 2019. Registered share capital is NOK 3.8m, divided into 100 shares. The company's stated purpose is: “Morselskap. Eie aksjer eller lignende kapitalandeler i andre selskaper, medvirke i andre selskaper, samt alt som hører naturlig til dette. I tillegg skal selskapet drive med salg, service og varmepumper.”.

Key figures · 2024

Operating profit
NOK −21,000
Equity
NOK −320,000

Financial health · 2024

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

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

Who owns KRUG HOLDING AS?

Kenneth Rugtveit
KRUG HOLDING AS
· NOK −21,000 profit

KRUG HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KRUG HOLDING AS own?

KRUG HOLDING AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about KRUG HOLDING AS

Who owns KRUG HOLDING AS?

Kenneth Rugtveit is the largest registered owner, with 100.0%.

Where is KRUG HOLDING AS based?

KRUG HOLDING AS has its business address in Haugesund.

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.