BIZTRAC BETA
Other technical consultancy

PERHAR AS

Org. no. 931257382 Limited company (AS) Kongsberg Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 528,000
Operating profit NOK 463,000
Equity NOK 712,000
Incorporated 2023
Share capital NOK 30,000

PERHAR AS is registered as a limited company in Kongsberg, Buskerud with organisation number 931257382. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Rådgivning- og prosjektledelse, samt øvrige tjenester innen beredskap, drift og vedlikehold innen kraftforsyning. Selskapet kan også delta i andre selskap med lignende virksomhet, samt kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak. Selskapet kan også drive med kjøp/drift av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 528,000 in revenue and NOK 463,000 in operating profit.

Key figures · 2025

Revenue
NOK 528,000
Operating profit
NOK 463,000
Equity
NOK 712,000
Est. value
NOK 1.8m

Financial health · 2025

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

Who owns PERHAR AS?

PER BJØRN HARDANGEN
PERHAR AS
NOK 528,000 rev. · NOK 463,000 profit

PERHAR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PERHAR AS

Who owns PERHAR AS?

PER BJØRN HARDANGEN is the largest registered owner, with 100.0%.

What is the revenue of PERHAR AS?

PERHAR AS had revenue of NOK 528,000 in 2025.

Who is the general manager of PERHAR AS?

Per Bjørn Hardangen is registered as general manager of PERHAR AS.

Where is PERHAR AS based?

PERHAR AS has its business address in Kongsberg.

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.