BIZTRAC BETA
COMPANY REGISTER PROFILE
830895752 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Other technical consultancy

NEOHEAT HOLDING AS

Org. no. 830895752 Limited company (AS) Stavanger Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK 97,000
Incorporated 2023
Share capital NOK 30,000

NEOHEAT HOLDING AS is registered as a limited company in Stavanger, Rogaland with organisation number 830895752. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investeringsvirksomhet, herunder å investere i aksjer, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 97,000
Est. value
NOK 69,000

Financial health · 2024

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

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

Who owns NEOHEAT HOLDING AS?

JARLE KJELDSEN
NEOHEAT HOLDING AS
NOK 0 rev. · NOK 0 profit

NEOHEAT HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NEOHEAT HOLDING AS own?

NEOHEAT HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NEOHEAT HOLDING AS

Who owns NEOHEAT HOLDING AS?

JARLE KJELDSEN is the largest registered owner, with 100.0%.

What is the revenue of NEOHEAT HOLDING AS?

NEOHEAT HOLDING AS had revenue of NOK 0 in 2024.

Where is NEOHEAT HOLDING AS based?

NEOHEAT HOLDING AS has its business address in Stavanger.

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.