biztrac. BETA
COMPANY REGISTER PROFILE
929166507 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Auditing

SENS REVISJON AS

Org. no. 929166507 Limited company (AS) Asker Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 4.7m
Operating profit NOK 1.1m
Equity NOK 64,000
Incorporated 2022
Share capital NOK 30,000

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 2025 financial year, show NOK 4.7m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 4.7m
▲ +148 %
Operating profit
NOK 1.1m
▲ +344 %
Equity
NOK 64,000
▲ +103 %
Est. value
NOK 3.2m

Financial health · 2025

Liquidity
1.01
Satisfactory
Current assets ÷ current liabilities
Profitability
107.8%
Very good
Return on total assets
Solidity
4.8%
Weak
Equity as a share of total capital

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

Who owns SENS REVISJON AS?

SENS REVISJON AS
NOK 4.7m rev. · NOK 1.1m 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 4.7m in 2025.

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 03.10.2026.

Report a problem

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