biztrac. BETA
COMPANY REGISTER PROFILE
828127322 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Support activities for fishing and aquaculture

YRI HOLDING AS

Org. no. 828127322 Limited company (AS) Bærum Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −12,000
Equity NOK −12,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

YRI HOLDING AS is registered as a limited company in Bærum, Akershus with organisation number 828127322. The business is classified under support activities for fishing and aquaculture (NACE 03.300). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2025

Operating profit
NOK −12,000
Equity
NOK −12,000

Financial health · 2025

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

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

Who owns YRI HOLDING AS?

YRI HOLDING AS
· NOK −12,000 profit

YRI HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does YRI HOLDING AS own?

YRI HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about YRI HOLDING AS

Who owns YRI HOLDING AS?

Eskil Yri is the largest registered owner, with 100.0%.

Where is YRI HOLDING AS based?

YRI HOLDING AS has its business address in Slependen.

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.