biztrac. BETA
COMPANY REGISTER PROFILE
924345438 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Computer consultancy and computer facilities management activities

YI HOLDING AS

Org. no. 924345438 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 811,000
Operating profit NOK 26,000
Equity NOK 5.1m
Incorporated 2019
Share capital NOK 30,000

YI HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 924345438. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Holdingselskap”. The most recent filed accounts, for the 2025 financial year, show NOK 811,000 in revenue and NOK 26,000 in operating profit.

Key figures · 2025

Revenue
NOK 811,000
▲ +108 %
Operating profit
NOK 26,000
▲ +107 %
Equity
NOK 5.1m
▼ −2 %
Est. value
NOK 9.3m

Financial health · 2025

Liquidity
2.40
Very good
Current assets ÷ current liabilities
Profitability
1.6%
Weak
Return on total assets
Solidity
37.6%
Good
Equity as a share of total capital

Who owns YI HOLDING AS?

YI HOLDING AS
NOK 811,000 rev. · NOK 26,000 profit

YI HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does YI HOLDING AS own?

YI HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about YI HOLDING AS

Who owns YI HOLDING AS?

Yuri Ivanov is the largest registered owner, with 100.0%.

What is the revenue of YI HOLDING AS?

YI HOLDING AS had revenue of NOK 811,000 in 2025.

Who is the general manager of YI HOLDING AS?

Yuri Ivanov is registered as general manager of YI HOLDING AS.

Where is YI HOLDING AS based?

YI HOLDING 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.