BIZTRAC BETA
Development of building projects

RYFYLKE HP AS

Org. no. 915611044 Limited company (AS) Strand Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −4,000
Equity NOK −1.1m
Incorporated 2015
Share capital NOK 1.2m

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,1 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−4k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

RYFYLKE HP AS is registered as a limited company in Strand, Rogaland with organisation number 915611044. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2015. Registered share capital is NOK 1.2m, divided into 12300 shares. The company's stated purpose is: “Utvikling og utbygging av tomteområder og annen eiendom, samt hva hermed står i forbindelse. Å kunne delta i eller kunne gjøre seg interesserte i selskaper som driver med lignende virksomhet.”.

Key figures · 2025

Operating profit
NOK −4,000
Equity
NOK −1.1m

Financial health · 2025

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

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

Who owns RYFYLKE HP AS?

RYFYLKE HANDELSPARK HOLDING AS
RYFYLKE HP AS
· NOK −4,000 profit

RYFYLKE HP AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RYFYLKE HP AS own?

RYFYLKE HP AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about RYFYLKE HP AS

Who owns RYFYLKE HP AS?

RYFYLKE HANDELSPARK HOLDING AS is the largest registered owner, with 100.0%.

Where is RYFYLKE HP AS based?

RYFYLKE HP AS has its business address in Jørpeland.

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.