BIZTRAC BETA
Other investment companies, except captive companies

KGJ PARTNERSHIP VIII AS

Org. no. 928080889 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 37.9m
Operating profit NOK 32.9m
Equity NOK 364.3m
Incorporated 2021
Share capital NOK 30.7m

Signals

1 flags
  • Nylig endring 2026-07-10 Aksjekapital registrert 2026-07-10.

KGJ PARTNERSHIP VIII AS is registered as a limited company in Oslo, Oslo with organisation number 928080889. The business is classified under other investment companies, except captive companies (NACE 64.312). The company was incorporated in 2021. Registered share capital is NOK 30.7m, divided into 3072000 shares. The company's stated purpose is: “Å foreta investeringer, i Norge og utlandet, i forretningsmessig virksomhet av enhver art, herunder eiendommer og finansielle aktiva og deltakelse som medeier i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 37.9m in revenue and NOK 32.9m in operating profit.

Key figures · 2025

Revenue
NOK 37.9m
Operating profit
NOK 32.9m
Equity
NOK 364.3m
Est. value
NOK 299.8m

Financial health · 2025

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

Who owns KGJ PARTNERSHIP VIII AS?

KGJ CAPITAL AS
KGJ PARTNERSHIP VIII AS
NOK 37.9m rev. · NOK 32.9m profit

KGJ PARTNERSHIP VIII AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about KGJ PARTNERSHIP VIII AS

Who owns KGJ PARTNERSHIP VIII AS?

KGJ CAPITAL AS is the largest registered owner, with 31.2%.

What is the revenue of KGJ PARTNERSHIP VIII AS?

KGJ PARTNERSHIP VIII AS had revenue of NOK 37.9m in 2025.

Where is KGJ PARTNERSHIP VIII AS based?

KGJ PARTNERSHIP VIII 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.