BIZTRAC BETA
Rental and operating of own or leased real estate

KONGSTAD VENTURES AS

Org. no. 923889787 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −5,000
Equity NOK 993,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

KONGSTAD VENTURES AS is registered as a limited company in Oslo, Oslo with organisation number 923889787. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Holdingselskap, men investerer også i aksjer og eiendom, samt selger konsulenttjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −5,000
Equity
NOK 993,000
Est. value
NOK 2.0m

Financial health · 2025

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

Who owns KONGSTAD VENTURES AS?

ANDREAS SCHOU KONGSTAD
KONGSTAD VENTURES AS
NOK 0 rev. · NOK −5,000 profit

KONGSTAD VENTURES AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KONGSTAD VENTURES AS own?

KONGSTAD VENTURES AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KONGSTAD VENTURES AS

Who owns KONGSTAD VENTURES AS?

ANDREAS SCHOU KONGSTAD is the largest registered owner, with 100.0%.

What is the revenue of KONGSTAD VENTURES AS?

KONGSTAD VENTURES AS had revenue of NOK 0 in 2025.

Where is KONGSTAD VENTURES AS based?

KONGSTAD VENTURES AS has its business address in Oslo.

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.