BIZTRAC BETA
Other real estate activities on a fee or contract basis

KISELDUR INVEST AS

Org. no. 919922346 Limited company (AS) Bergen Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −13,000
Equity NOK −112,000
Incorporated 2017
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−112k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−13k kr).

KISELDUR INVEST AS is registered as a limited company in Bergen, Vestland with organisation number 919922346. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Direkte eller indirekte investeringer i selskaper uavhengig av bransje og alt hva som dermed kan forbindes.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −13,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −13,000
Equity
NOK −112,000

Financial health · 2025

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

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

Who owns KISELDUR INVEST AS?

VALTOR HOLDING AS
KISELDUR INVEST AS
NOK 0 rev. · NOK −13,000 profit

KISELDUR INVEST AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KISELDUR INVEST AS

Who owns KISELDUR INVEST AS?

VALTOR HOLDING AS is the largest registered owner, with 75.0%.

What is the revenue of KISELDUR INVEST AS?

KISELDUR INVEST AS had revenue of NOK 0 in 2025.

Where is KISELDUR INVEST AS based?

KISELDUR INVEST AS has its business address in Bergen.

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.