BIZTRAC BETA
COMPANY REGISTER PROFILE
933110672 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Electrical installation

TYSVÆR ELEKTRO AS

Org. no. 933110672 Limited company (AS) Tysvær Incorporated 1982 Active
Ownership graph ↗
Revenue 2025 NOK 11.3m
Operating profit NOK −879,000
Equity NOK 1.4m
Incorporated 1982
Employees 11
Share capital NOK 1.5m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−879k kr).

TYSVÆR ELEKTRO AS is registered as a limited company in Tysvær, Rogaland with organisation number 933110672. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 1982 and has 11 registered employees. Registered share capital is NOK 1.5m, divided into 50 shares. The company's stated purpose is: “Elektrisk installasjonsvirksomhet samt hva dermed står i forbindelse, herunder å delta i andre sel- skaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 11.3m in revenue and NOK −879,000 in operating profit.

Key figures · 2025

Revenue
NOK 11.3m
▲ +17 %
Operating profit
NOK −879,000
▼ −286 %
Equity
NOK 1.4m
▼ −39 %
Est. value
NOK 4.5m

Financial health · 2025

Liquidity
2.34
Very good
Current assets ÷ current liabilities
Profitability
-12.6%
Not satisfactory
Return on total assets
Solidity
21.2%
Good
Equity as a share of total capital

Who owns TYSVÆR ELEKTRO AS?

TYSVÆR ELEKTRO AS
NOK 11.3m rev. · NOK −879,000 profit

TYSVÆR ELEKTRO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TYSVÆR ELEKTRO AS

Who owns TYSVÆR ELEKTRO AS?

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

What is the revenue of TYSVÆR ELEKTRO AS?

TYSVÆR ELEKTRO AS had revenue of NOK 11.3m in 2025.

Where is TYSVÆR ELEKTRO AS based?

TYSVÆR ELEKTRO AS has its business address in Skjoldastraumen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.