BIZTRAC BETA
Activities of agents involved in the wholesale of other particular products

H PAAR CONSULT AS

Org. no. 878629752 Limited company (AS) Fredrikstad Incorporated 1997 Active
Ownership graph ↗
Revenue 2025 NOK 819,000
Operating profit NOK 408,000
Equity NOK 1.6m
Incorporated 1997
Share capital NOK 100,000

H PAAR CONSULT AS is registered as a limited company in Fredrikstad, Østfold with organisation number 878629752. The business is classified under activities of agents involved in the wholesale of other particular products (NACE 46.180). The company was incorporated in 1997. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Markedsføre og selge varer i Norge og Europa. Formidling av salg på provisjonsbasis. Konsulentvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 819,000 in revenue and NOK 408,000 in operating profit.

Key figures · 2025

Revenue
NOK 819,000
Operating profit
NOK 408,000
Equity
NOK 1.6m
Est. value
NOK 2.3m

Financial health · 2025

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

Who owns H PAAR CONSULT AS?

HUGO ERNST JOSEF PAAR
H PAAR CONSULT AS
NOK 819,000 rev. · NOK 408,000 profit

H PAAR CONSULT AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about H PAAR CONSULT AS

Who owns H PAAR CONSULT AS?

HUGO ERNST JOSEF PAAR is the largest registered owner, with 68.0%.

What is the revenue of H PAAR CONSULT AS?

H PAAR CONSULT AS had revenue of NOK 819,000 in 2025.

Who is the general manager of H PAAR CONSULT AS?

Hugo Ernst Josef Paar is registered as general manager of H PAAR CONSULT AS.

Where is H PAAR CONSULT AS based?

H PAAR CONSULT AS has its business address in Engelsviken.

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.