biztrac. BETA
COMPANY REGISTER PROFILE
875868632 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Auditing

REVISIONSBUREAUET AS

Org. no. 875868632 Limited company (AS) Oslo Incorporated 1995 Active
Ownership graph ↗
Revenue 2025 NOK 13.2m
Operating profit NOK 1.7m
Equity NOK 3.1m
Incorporated 1995
Employees 7
Share capital NOK 97,000

REVISIONSBUREAUET AS is registered as a limited company in Oslo, Oslo with organisation number 875868632. The business is classified under auditing (NACE 69.201). The company was incorporated in 1995 and has 7 registered employees. Registered share capital is NOK 97,000, divided into 132 shares. The company's stated purpose is: “Å yte tjenester innen revisjon, rådgivning og regnskap, samt det som naturlig faller inn under dette. Selskapet skal også kunne delta i annen virksomhet. ”. The most recent filed accounts, for the 2025 financial year, show NOK 13.2m in revenue and NOK 1.7m in operating profit.

Key figures · 2025

Revenue
NOK 13.2m
▼ −2 %
Operating profit
NOK 1.7m
▼ −40 %
Equity
NOK 3.1m
▼ −23 %
Est. value
NOK 10.3m

Financial health · 2025

Liquidity
2.23
Very good
Current assets ÷ current liabilities
Profitability
21.0%
Very good
Return on total assets
Solidity
40.0%
Good
Equity as a share of total capital

Who owns REVISIONSBUREAUET AS?

REVISIONSBUREAUET AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about REVISIONSBUREAUET AS

Who owns REVISIONSBUREAUET AS?

Finn-Jarle Lund Mathisen is the largest registered owner, with 33.3%.

What is the revenue of REVISIONSBUREAUET AS?

REVISIONSBUREAUET AS had revenue of NOK 13.2m in 2025.

Who is the general manager of REVISIONSBUREAUET AS?

Finn-Jarle Lund Mathisen is registered as general manager of REVISIONSBUREAUET AS.

Where is REVISIONSBUREAUET AS based?

REVISIONSBUREAUET AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.