BIZTRAC BETA
Joinery installation

RYGH HOLDING AS

Org. no. 928468453 Limited company (AS) Engerdal Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −89,000
Equity NOK 2.0m
Incorporated 2021
Share capital NOK 600,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−89k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

RYGH HOLDING AS is registered as a limited company in Engerdal, Innlandet with organisation number 928468453. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2021. Registered share capital is NOK 600,000, divided into 600 shares. The company's stated purpose is: “Forvaltning av kapital, investere i interessante prosjekter av enhver art, herunder fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −89,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −89,000
Equity
NOK 2.0m
Est. value
NOK 7.6m

Financial health · 2024

Liquidity
1.57
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
29.9%
Good
Equity as a share of total capital

Who owns RYGH HOLDING AS?

KRISTOFFER RYGH
RYGH HOLDING AS
NOK 0 rev. · NOK −89,000 profit

RYGH HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RYGH HOLDING AS own?

RYGH HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about RYGH HOLDING AS

Who owns RYGH HOLDING AS?

KRISTOFFER RYGH is the largest registered owner, with 100.0%.

What is the revenue of RYGH HOLDING AS?

RYGH HOLDING AS had revenue of NOK 0 in 2024.

Where is RYGH HOLDING AS based?

RYGH HOLDING AS has its business address in Engerdal.

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.