BIZTRAC BETA
Development of building projects

KALBERG NK3 AS

Org. no. 927817187 Limited company (AS) Klepp Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −29,000
Equity NOK −49,000
Incorporated 2021
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−49k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−29k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KALBERG NK3 AS is registered as a limited company in Klepp, Rogaland with organisation number 927817187. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eiendomsutvikling og utbygging/drift av kraftkrevende industri som feks datasenter, samt alt som står i forbindelse med dette, herunder deltakelse i andre selskaper med lignende og/eller tilhørende virksomhet.”.

Key figures · 2024

Operating profit
NOK −29,000
Equity
NOK −49,000

Financial health · 2024

Liquidity
149.90
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-3.6%
Weak
Equity as a share of total capital

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

Who owns KALBERG NK3 AS?

KALBERG HOLDING AS
KALBERG NK3 AS
· NOK −29,000 profit

KALBERG NK3 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KALBERG NK3 AS

Who owns KALBERG NK3 AS?

KALBERG HOLDING AS is the largest registered owner, with 100.0%.

Who is the general manager of KALBERG NK3 AS?

Frank Skjæveland is registered as general manager of KALBERG NK3 AS.

Where is KALBERG NK3 AS based?

KALBERG NK3 AS has its business address in Klepp Stasjon.

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.