BIZTRAC BETA
COMPANY REGISTER PROFILE
999316158 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Plumbing installation

KALUPE AS

Org. no. 999316158 Limited company (AS) Horten Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 30,000
Operating profit NOK −109,000
Equity NOK −239,000
Incorporated 2012
Share capital NOK 30,000

Signals

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

KALUPE AS is registered as a limited company in Horten, Vestfold with organisation number 999316158. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Montasje og kjøleteknikk.”. The most recent filed accounts, for the 2024 financial year, show NOK 30,000 in revenue and NOK −109,000 in operating profit.

Key figures · 2024

Revenue
NOK 30,000
Operating profit
NOK −109,000
Equity
NOK −239,000

Financial health · 2024

Liquidity
0.00
Not 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 KALUPE AS?

OLE CHRISTIAN GRØNHOVD
KALUPE AS
NOK 30,000 rev. · NOK −109,000 profit

KALUPE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KALUPE AS

Who owns KALUPE AS?

OLE CHRISTIAN GRØNHOVD is the largest registered owner, with 100.0%.

What is the revenue of KALUPE AS?

KALUPE AS had revenue of NOK 30,000 in 2024.

Who is the general manager of KALUPE AS?

Ole Christian Grønhovd is registered as general manager of KALUPE AS.

Where is KALUPE AS based?

KALUPE AS has its business address in Horten.

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.