BIZTRAC BETA
Uoppgitt

YRJAR HOLDING AS

Org. no. 833226592 Limited company (AS) Ørland Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −5
Equity NOK 30,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

YRJAR HOLDING AS is registered as a limited company in Ørland, Trøndelag with organisation number 833226592. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i, eie, forvalte og selge andeler i andre selskaper, samt å utøve aktiviteter som er komplementære til disse, inkludert, men ikke begrenset til, finansiell rådgivning og forvaltning.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −5 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −5
Equity
NOK 30,000
Est. value
NOK 35,000

Financial health · 2024

Liquidity
1.01
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
1.4%
Weak
Equity as a share of total capital

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

Who owns YRJAR HOLDING AS?

ROGER RØSTAD
YRJAR HOLDING AS
NOK 0 rev. · NOK −5 profit

YRJAR HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does YRJAR HOLDING AS own?

YRJAR HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about YRJAR HOLDING AS

Who owns YRJAR HOLDING AS?

ROGER RØSTAD is the largest registered owner, with 100.0%.

What is the revenue of YRJAR HOLDING AS?

YRJAR HOLDING AS had revenue of NOK 0 in 2024.

Where is YRJAR HOLDING AS based?

YRJAR HOLDING AS has its business address in Bjugn.

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.