BIZTRAC BETA
Electrical installation

SETESDAL ELEKTRO AS

Org. no. 987863617 Limited company (AS) Bykle Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 4.3m
Operating profit NOK 93,000
Equity NOK 924,000
Incorporated 2005
Share capital NOK 100,000

SETESDAL ELEKTRO AS is registered as a limited company in Bykle, Agder with organisation number 987863617. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Elektroinstallatør samt det som naturlig faller inn under slik virksomhet, herunder å delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.3m in revenue and NOK 93,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.3m
Operating profit
NOK 93,000
Equity
NOK 924,000
Est. value
NOK 785,000

Financial health · 2025

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

Who owns SETESDAL ELEKTRO AS?

TOR GJERDEN
SETESDAL ELEKTRO AS
NOK 4.3m rev. · NOK 93,000 profit

SETESDAL ELEKTRO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SETESDAL ELEKTRO AS own?

SETESDAL ELEKTRO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SETESDAL ELEKTRO AS

Who owns SETESDAL ELEKTRO AS?

TOR GJERDEN is the largest registered owner, with 100.0%.

What is the revenue of SETESDAL ELEKTRO AS?

SETESDAL ELEKTRO AS had revenue of NOK 4.3m in 2025.

Who is the general manager of SETESDAL ELEKTRO AS?

Tor Gjerden is registered as general manager of SETESDAL ELEKTRO AS.

Where is SETESDAL ELEKTRO AS based?

SETESDAL ELEKTRO AS has its business address in Bykle.

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.