BIZTRAC BETA
Legal activities

ADVOKATFIRMAET JØRSTAD AS

Org. no. 919212586 Limited company (AS) Harstad Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 4.4m
Operating profit NOK 36,000
Equity NOK 401,000
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-03-24 Adresseendring registrert 2026-03-24.

ADVOKATFIRMAET JØRSTAD AS is registered as a limited company in Harstad, Troms with organisation number 919212586. The business is classified under legal activities (NACE 69.100). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Advokatvirksomhet/rettshjelp samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.4m in revenue and NOK 36,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.4m
Operating profit
NOK 36,000
Equity
NOK 401,000
Est. value
NOK 298,000

Financial health · 2025

Liquidity
1.38
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
29.0%
Good
Equity as a share of total capital

Who owns ADVOKATFIRMAET JØRSTAD AS?

FINN HÅKON JØRSTAD
ADVOKATFIRMAET JØRSTAD AS
NOK 4.4m rev. · NOK 36,000 profit

ADVOKATFIRMAET JØRSTAD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ADVOKATFIRMAET JØRSTAD AS

Who owns ADVOKATFIRMAET JØRSTAD AS?

FINN HÅKON JØRSTAD is the largest registered owner, with 100.0%.

What is the revenue of ADVOKATFIRMAET JØRSTAD AS?

ADVOKATFIRMAET JØRSTAD AS had revenue of NOK 4.4m in 2025.

Who is the general manager of ADVOKATFIRMAET JØRSTAD AS?

Finn Håkon Jørstad is registered as general manager of ADVOKATFIRMAET JØRSTAD AS.

Where is ADVOKATFIRMAET JØRSTAD AS based?

ADVOKATFIRMAET JØRSTAD AS has its business address in Harstad.

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.