BIZTRAC BETA
Legal activities

ADVOKATFIRMAET NYHEIM AS

Org. no. 987897643 Limited company (AS) Bodø Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 6,000
Equity NOK 9.1m
Incorporated 2005
Share capital NOK 100,000

ADVOKATFIRMAET NYHEIM AS is registered as a limited company in Bodø, Nordland with organisation number 987897643. The business is classified under legal activities (NACE 69.100). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Advokatvirksomhet, kjøp og salg av aksjer og andre verdipapirer, samt kjøp, utleie og salg av fast eiendom, samt hva hermed står i forbindelse, herunder å delta i andre selskaper med liknende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 6,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 6,000
Equity
NOK 9.1m
Est. value
NOK 4.5m

Financial health · 2025

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

Who owns ADVOKATFIRMAET NYHEIM AS?

SIV NINA NYHEIM
ADVOKATFIRMAET NYHEIM AS
NOK 1.3m rev. · NOK 6,000 profit

ADVOKATFIRMAET NYHEIM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ADVOKATFIRMAET NYHEIM AS own?

ADVOKATFIRMAET NYHEIM AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about ADVOKATFIRMAET NYHEIM AS

Who owns ADVOKATFIRMAET NYHEIM AS?

SIV NINA NYHEIM is the largest registered owner, with 100.0%.

What is the revenue of ADVOKATFIRMAET NYHEIM AS?

ADVOKATFIRMAET NYHEIM AS had revenue of NOK 1.3m in 2025.

Where is ADVOKATFIRMAET NYHEIM AS based?

ADVOKATFIRMAET NYHEIM AS has its business address in Bodø.

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.