BIZTRAC BETA
Auditing

REVISJON CONSULT AS

Org. no. 913941330 Limited company (AS) Nittedal Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 2.8m
Operating profit NOK 1.4m
Equity NOK 3.7m
Incorporated 2014
Share capital NOK 100,000

REVISJON CONSULT AS is registered as a limited company in Nittedal, Akershus with organisation number 913941330. The business is classified under auditing (NACE 69.201). The company was incorporated in 2014. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Selskapets formål er revisjon og regnskap, konsulentvirksomhet i den forbindelse. Selskapet kan delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.8m in revenue and NOK 1.4m in operating profit.

Key figures · 2024

Revenue
NOK 2.8m
Operating profit
NOK 1.4m
Equity
NOK 3.7m
Est. value
NOK 6.9m

Financial health · 2024

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

Who owns REVISJON CONSULT AS?

BJØRN PAULSEN
REVISJON CONSULT AS
NOK 2.8m rev. · NOK 1.4m profit

REVISJON CONSULT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does REVISJON CONSULT AS own?

REVISJON CONSULT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about REVISJON CONSULT AS

Who owns REVISJON CONSULT AS?

BJØRN PAULSEN is the largest registered owner, with 100.0%.

What is the revenue of REVISJON CONSULT AS?

REVISJON CONSULT AS had revenue of NOK 2.8m in 2024.

Who is the general manager of REVISJON CONSULT AS?

Bjørn Paulsen is registered as general manager of REVISJON CONSULT AS.

Where is REVISJON CONSULT AS based?

REVISJON CONSULT AS has its business address in Hagan.

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.