BIZTRAC BETA
Rental and operating of own or leased real estate

NINA RYEN HOLDING AS

Org. no. 893464352 Limited company (AS) Fredrikstad Incorporated 2008 Active
Ownership graph ↗
Operating profit NOK −12,000
Equity NOK 29.5m
Incorporated 2008
Share capital NOK 190,000

Signals

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

NINA RYEN HOLDING AS is registered as a limited company in Fredrikstad, Østfold with organisation number 893464352. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2008. Registered share capital is NOK 190,000, divided into 1 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter å forestå investeringsvirksomhet, eiendomsforvaltning, forretningsførsel og annen virksomhet beslektet med denne.”.

Key figures · 2024

Operating profit
NOK −12,000
Equity
NOK 29.5m
Est. value
NOK 43.1m

Financial health · 2024

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

Who owns NINA RYEN HOLDING AS?

NINA ELISABETH RYEN
NINA RYEN HOLDING AS
· NOK −12,000 profit

NINA RYEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NINA RYEN HOLDING AS own?

NINA RYEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NINA RYEN HOLDING AS

Who owns NINA RYEN HOLDING AS?

NINA ELISABETH RYEN is the largest registered owner, with 100.0%.

Who is the general manager of NINA RYEN HOLDING AS?

Nina Elisabeth Ryen is registered as general manager of NINA RYEN HOLDING AS.

Where is NINA RYEN HOLDING AS based?

NINA RYEN HOLDING AS has its business address in Fredrikstad.

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.