BIZTRAC BETA
Electrical installation

PERS ELEKTRISKE AS

Org. no. 989290150 Limited company (AS) Nord-Odal Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK −431,000
Equity NOK 1.6m
Incorporated 2005
Share capital NOK 30,000

Signals

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

PERS ELEKTRISKE AS is registered as a limited company in Nord-Odal, Innlandet with organisation number 989290150. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 2005. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Elektrisk installasjonsarbeid, kjøp og salg av elektrovarer og tjenester. Bygg og anlegg: Veggmontasje og andre byggetjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK −431,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK −431,000
Equity
NOK 1.6m
Est. value
NOK 932,000

Financial health · 2025

Liquidity
0.47
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
50.1%
Very good
Equity as a share of total capital

Who owns PERS ELEKTRISKE AS?

PER THOMAS NYHUUS
PERS ELEKTRISKE AS
NOK 1.4m rev. · NOK −431,000 profit

PERS ELEKTRISKE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PERS ELEKTRISKE AS

Who owns PERS ELEKTRISKE AS?

PER THOMAS NYHUUS is the largest registered owner, with 100.0%.

What is the revenue of PERS ELEKTRISKE AS?

PERS ELEKTRISKE AS had revenue of NOK 1.4m in 2025.

Who is the general manager of PERS ELEKTRISKE AS?

Per Thomas Nyhuus is registered as general manager of PERS ELEKTRISKE AS.

Where is PERS ELEKTRISKE AS based?

PERS ELEKTRISKE AS has its business address in Bruvoll.

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.