BIZTRAC BETA
Business and other management consultancy activities

Revisjonsselskapet A/S

Org. no. 940144019 Limited company (AS) Vestby Incorporated 1986 Active
Ownership graph ↗
Revenue 2024 NOK 93,000
Operating profit NOK −111,000
Equity NOK 5.7m
Incorporated 1986
Share capital NOK 102,000

Signals

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

Revisjonsselskapet A/S is registered as a limited company in Vestby, Akershus with organisation number 940144019. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 1986. Registered share capital is NOK 102,000, divided into 51 shares. The company's stated purpose is: “Konsulentvirksomhet, samt deltakelse i andre selskap ved aksjetegning og på annen måte.”. The most recent filed accounts, for the 2024 financial year, show NOK 93,000 in revenue and NOK −111,000 in operating profit.

Key figures · 2024

Revenue
NOK 93,000
Operating profit
NOK −111,000
Equity
NOK 5.7m
Est. value
NOK 2.9m

Financial health · 2024

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

Who owns Revisjonsselskapet A/S?

VERPET EIENDOMSDRIFT AS
Revisjonsselskapet A/S
NOK 93,000 rev. · NOK −111,000 profit

Revisjonsselskapet A/S has 2 registered shareholders:

All shareholders and roles →

Group structure

Revisjonsselskapet A/S er morselskap for 1 datterselskap:

Frequently asked questions about Revisjonsselskapet A/S

Who owns Revisjonsselskapet A/S?

VERPET EIENDOMSDRIFT AS is the largest registered owner, with 98.0%.

What is the revenue of Revisjonsselskapet A/S?

Revisjonsselskapet A/S had revenue of NOK 93,000 in 2024.

Where is Revisjonsselskapet A/S based?

Revisjonsselskapet A/S has its business address in Vestby.

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.