biztrac. BETA
COMPANY REGISTER PROFILE
920764673 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

RYFYLKEVEGEN 1970 AS

Org. no. 920764673 Limited company (AS) Strand Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 660,000
Equity NOK 1.5m
Incorporated 2018
Share capital NOK 30,000

RYFYLKEVEGEN 1970 AS is registered as a limited company in Strand, Rogaland with organisation number 920764673. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Utleie av fast eiendom og eiendomsutvikling samt hva som herved står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 660,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
▲ +4 %
Operating profit
NOK 660,000
▼ −2 %
Equity
NOK 1.5m
▼ −9 %
Est. value
NOK 2.5m

Financial health · 2025

Liquidity
0.70
Weak
Current assets ÷ current liabilities
Profitability
22.8%
Very good
Return on total assets
Solidity
54.2%
Very good
Equity as a share of total capital

Who owns RYFYLKEVEGEN 1970 AS?

RYFYLKEVEGEN 1970 AS
NOK 1.1m rev. · NOK 660,000 profit

RYFYLKEVEGEN 1970 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RYFYLKEVEGEN 1970 AS

Who owns RYFYLKEVEGEN 1970 AS?

SVABERGE AS is the largest registered owner, with 100.0%.

What is the revenue of RYFYLKEVEGEN 1970 AS?

RYFYLKEVEGEN 1970 AS had revenue of NOK 1.1m in 2025.

Who is the general manager of RYFYLKEVEGEN 1970 AS?

Arild Berge is registered as general manager of RYFYLKEVEGEN 1970 AS.

Where is RYFYLKEVEGEN 1970 AS based?

RYFYLKEVEGEN 1970 AS has its business address in Tau.

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.