BIZTRAC BETA
Auditing

FINNMARKSREVISJON AS

Org. no. 934330676 Limited company (AS) Hammerfest Incorporated 1983 Active
Ownership graph ↗
Revenue 2024 NOK 5.1m
Operating profit NOK −8,000
Equity NOK 351,000
Incorporated 1983
Employees 6
Share capital NOK 255,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−8k kr).

FINNMARKSREVISJON AS is registered as a limited company in Hammerfest, Finnmark with organisation number 934330676. The business is classified under auditing (NACE 69.201). The company was incorporated in 1983 and has 6 registered employees. Registered share capital is NOK 255,000, divided into 255 shares. The company's stated purpose is: “Drive revisjon, regnskapsførsel, økonomisk rådgivning, samt det som naturlig hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.1m in revenue and NOK −8,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.1m
Operating profit
NOK −8,000
Equity
NOK 351,000
Est. value
NOK 5.6m

Financial health · 2024

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

Who owns FINNMARKSREVISJON AS?

BIRGIT OPDAHL HANSEN
FINNMARKSREVISJON AS
NOK 5.1m rev. · NOK −8,000 profit

FINNMARKSREVISJON AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about FINNMARKSREVISJON AS

Who owns FINNMARKSREVISJON AS?

BIRGIT OPDAHL HANSEN is the largest registered owner, with 50.6%.

What is the revenue of FINNMARKSREVISJON AS?

FINNMARKSREVISJON AS had revenue of NOK 5.1m in 2024.

Who is the general manager of FINNMARKSREVISJON AS?

Birgit Opdahl Hansen is registered as general manager of FINNMARKSREVISJON AS.

Where is FINNMARKSREVISJON AS based?

FINNMARKSREVISJON AS has its business address in Hammerfest.

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.