BIZTRAC BETA
Auditing

SENS REVISJON AS

Org. no. 929166507 Limited company (AS) Asker Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 1.9m
Operating profit NOK −438,000
Equity NOK 32,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

SENS REVISJON AS is registered as a limited company in Asker, Akershus with organisation number 929166507. The business is classified under auditing (NACE 69.201). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Salg av revisjonstjenester, regnskapstjenester, herunder føring av regnskap, konsulentbistand, kursvirksomhet samt deltakelse i annen økonomisk virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.9m in revenue and NOK −438,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.9m
Operating profit
NOK −438,000
Equity
NOK 32,000
Est. value
NOK 2.0m

Financial health · 2024

Liquidity
0.75
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
4.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SENS REVISJON AS?

E-REVISOR AS
SENS REVISJON AS
NOK 1.9m rev. · NOK −438,000 profit

SENS REVISJON AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SENS REVISJON AS

Who owns SENS REVISJON AS?

E-REVISOR AS is the largest registered owner, with 50.0%.

What is the revenue of SENS REVISJON AS?

SENS REVISJON AS had revenue of NOK 1.9m in 2024.

Who is the general manager of SENS REVISJON AS?

Eva Alyona Rødaas is registered as general manager of SENS REVISJON AS.

Where is SENS REVISJON AS based?

SENS REVISJON AS has its business address in Nesbru.

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.