BIZTRAC BETA
Legal activities

ADVOKAT HANS HENRIK PETTERSEN AS

Org. no. 985567247 Limited company (AS) Halden Incorporated 2003 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 86,000
Equity NOK 1.5m
Incorporated 2003
Share capital NOK 100,000

ADVOKAT HANS HENRIK PETTERSEN AS is registered as a limited company in Halden, Østfold with organisation number 985567247. The business is classified under legal activities (NACE 69.100). The company was incorporated in 2003. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Advokatvirksomhet, samt det som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 86,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK 86,000
Equity
NOK 1.5m
Est. value
NOK 1.4m

Financial health · 2025

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

Who owns ADVOKAT HANS HENRIK PETTERSEN AS?

HANS HENRIK PETTERSEN
ADVOKAT HANS HENRIK PETTERSEN AS
NOK 1.4m rev. · NOK 86,000 profit

ADVOKAT HANS HENRIK PETTERSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ADVOKAT HANS HENRIK PETTERSEN AS

Who owns ADVOKAT HANS HENRIK PETTERSEN AS?

HANS HENRIK PETTERSEN is the largest registered owner, with 100.0%.

What is the revenue of ADVOKAT HANS HENRIK PETTERSEN AS?

ADVOKAT HANS HENRIK PETTERSEN AS had revenue of NOK 1.4m in 2025.

Who is the general manager of ADVOKAT HANS HENRIK PETTERSEN AS?

Hans Henrik Pettersen is registered as general manager of ADVOKAT HANS HENRIK PETTERSEN AS.

Where is ADVOKAT HANS HENRIK PETTERSEN AS based?

ADVOKAT HANS HENRIK PETTERSEN AS has its business address in Halden.

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.