BIZTRAC BETA
Electrical installation

RYFYLKE ELEKTRO AS

Org. no. 987814136 Limited company (AS) Sauda Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 34.1m
Operating profit NOK 3.0m
Equity NOK 4.9m
Incorporated 2005
Employees 21
Share capital NOK 100,000

RYFYLKE ELEKTRO AS is registered as a limited company in Sauda, Rogaland with organisation number 987814136. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 2005 and has 21 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Elektroinstallasjoner og annen virksomhet som kan ha tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 34.1m in revenue and NOK 3.0m in operating profit.

Key figures · 2024

Revenue
NOK 34.1m
Operating profit
NOK 3.0m
Equity
NOK 4.9m
Est. value
NOK 11.8m

Financial health · 2025

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

Who owns RYFYLKE ELEKTRO AS?

BLANKENBORG HOLDING AS
RYFYLKE ELEKTRO AS
NOK 34.1m rev. · NOK 3.0m profit

RYFYLKE ELEKTRO AS has 3 registered shareholders:

All shareholders and roles →

Which companies does RYFYLKE ELEKTRO AS own?

RYFYLKE ELEKTRO AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about RYFYLKE ELEKTRO AS

Who owns RYFYLKE ELEKTRO AS?

BLANKENBORG HOLDING AS is the largest registered owner, with 56.0%.

What is the revenue of RYFYLKE ELEKTRO AS?

RYFYLKE ELEKTRO AS had revenue of NOK 34.1m in 2024.

Who is the general manager of RYFYLKE ELEKTRO AS?

Jon Haugsland Kolstø is registered as general manager of RYFYLKE ELEKTRO AS.

Where is RYFYLKE ELEKTRO AS based?

RYFYLKE ELEKTRO AS has its business address in Sauda.

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.