BIZTRAC BETA
Electrical installation

PR-ELEKTRO AS

Org. no. 942381204 Limited company (AS) Nittedal Incorporated 1986 Active
Ownership graph ↗
Revenue 2025 NOK 626,000
Operating profit NOK −44,000
Equity NOK 52,000
Incorporated 1986
Share capital NOK 100,000

Signals

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

PR-ELEKTRO AS is registered as a limited company in Nittedal, Akershus with organisation number 942381204. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 1986. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Elektrisk installasjon, kjøp og salg av elektriske artikkler, konsulentvirksomhet samt annen virksom- het som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 626,000 in revenue and NOK −44,000 in operating profit.

Key figures · 2025

Revenue
NOK 626,000
Operating profit
NOK −44,000
Equity
NOK 52,000
Est. value
NOK 240,000

Financial health · 2025

Liquidity
1.56
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
44.2%
Weak
Equity as a share of total capital

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

Who owns PR-ELEKTRO AS?

TOM HALVORSEN
PR-ELEKTRO AS
NOK 626,000 rev. · NOK −44,000 profit

PR-ELEKTRO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PR-ELEKTRO AS

Who owns PR-ELEKTRO AS?

TOM HALVORSEN is the largest registered owner, with 100.0%.

What is the revenue of PR-ELEKTRO AS?

PR-ELEKTRO AS had revenue of NOK 626,000 in 2025.

Who is the general manager of PR-ELEKTRO AS?

Tom Halvorsen is registered as general manager of PR-ELEKTRO AS.

Where is PR-ELEKTRO AS based?

PR-ELEKTRO AS has its business address in Nittedal.

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.