BIZTRAC BETA
Other technical consultancy

KJELSBERG AS

Org. no. 989042556 Limited company (AS) Stange Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 227,000
Operating profit NOK −62,000
Equity NOK 10.2m
Incorporated 2005
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−62k kr).

KJELSBERG AS is registered as a limited company in Stange, Innlandet with organisation number 989042556. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Levere ingeniørtjenester, samt investere i aksjer og andre verdipapirer, herunder å delta i andre selskaper med lignende virksomhet. Avvirknig, herunder uttak av tømmer, flis og ved.”. The most recent filed accounts, for the 2025 financial year, show NOK 227,000 in revenue and NOK −62,000 in operating profit.

Key figures · 2025

Revenue
NOK 227,000
Operating profit
NOK −62,000
Equity
NOK 10.2m
Est. value
NOK 10.9m

Financial health · 2025

Liquidity
958.69
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
99.0%
Very good
Equity as a share of total capital

Who owns KJELSBERG AS?

JØRN OTTO KJELSBERG
KJELSBERG AS
NOK 227,000 rev. · NOK −62,000 profit

KJELSBERG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KJELSBERG AS own?

KJELSBERG AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about KJELSBERG AS

Who owns KJELSBERG AS?

JØRN OTTO KJELSBERG is the largest registered owner, with 100.0%.

What is the revenue of KJELSBERG AS?

KJELSBERG AS had revenue of NOK 227,000 in 2025.

Where is KJELSBERG AS based?

KJELSBERG AS has its business address in Åsvang.

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.