biztrac. BETA
COMPANY REGISTER PROFILE
922025711 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

KANYE INVEST AS

Org. no. 922025711 Limited company (AS) Oslo Incorporated 2018 Active
Revenue 2025 NOK 0
Operating profit NOK −11,000
Equity NOK −18,000
Incorporated 2018
Share capital NOK 52,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−18k kr).

KANYE INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 922025711. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2018. Registered share capital is NOK 52,000, divided into 1729 shares. The company's stated purpose is: “Forvaltning av aksjer og andre finansielle instrumenter, samt alt som naturlig hører til dette”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −11,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
▼ −100 %
Operating profit
NOK −11,000
▼ −108 %
Equity
NOK −18,000
▼ −262 %
Est. value
NOK 169,000

Financial health · 2025

Liquidity
0.05
Not satisfactory
Current assets ÷ current liabilities
Profitability
-9.5%
Not satisfactory
Return on total assets
Solidity
-6.9%
Weak
Equity as a share of total capital

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

Who owns KANYE INVEST AS?

KANYE INVEST AS
NOK 0 rev. · NOK −11,000 profit

KANYE INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KANYE INVEST AS own?

KANYE INVEST AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about KANYE INVEST AS

Who owns KANYE INVEST AS?

Simen Hassel is the largest registered owner, with 100.0%.

What is the revenue of KANYE INVEST AS?

KANYE INVEST AS had revenue of NOK 0 in 2025.

Where is KANYE INVEST AS based?

KANYE INVEST 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.