BIZTRAC BETA
Auditing

NORDMØRE REVISJON AS

Org. no. 961225930 Limited company (AS) Kristiansund Incorporated 1991 Active
Ownership graph ↗
Revenue 2025 NOK 106,000
Operating profit NOK 113,000
Equity NOK 1.1m
Incorporated 1991
Share capital NOK 378,000

NORDMØRE REVISJON AS is registered as a limited company in Kristiansund, Møre og Romsdal with organisation number 961225930. The business is classified under auditing (NACE 69.201). The company was incorporated in 1991. Registered share capital is NOK 378,000, divided into 378 shares. The company's stated purpose is: “Eie og forvalte aksjer, andeler og kapital, samt alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 106,000 in revenue and NOK 113,000 in operating profit.

Key figures · 2025

Revenue
NOK 106,000
Operating profit
NOK 113,000
Equity
NOK 1.1m
Est. value
NOK 818,000

Financial health · 2025

Liquidity
0.21
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
28.4%
Good
Equity as a share of total capital

Who owns NORDMØRE REVISJON AS?

NIIS AS
NORDMØRE REVISJON AS
NOK 106,000 rev. · NOK 113,000 profit

NORDMØRE REVISJON AS has 3 registered shareholders:

All shareholders and roles →

Which companies does NORDMØRE REVISJON AS own?

NORDMØRE REVISJON AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NORDMØRE REVISJON AS

Who owns NORDMØRE REVISJON AS?

NIIS AS is the largest registered owner, with 33.3%.

What is the revenue of NORDMØRE REVISJON AS?

NORDMØRE REVISJON AS had revenue of NOK 106,000 in 2025.

Who is the general manager of NORDMØRE REVISJON AS?

Toril Ulfsnes is registered as general manager of NORDMØRE REVISJON AS.

Where is NORDMØRE REVISJON AS based?

NORDMØRE REVISJON AS has its business address in Kristiansund N.

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.