BIZTRAC BETA
Auditing

EI REVISJON OG RÅDGIVNING AS

Org. no. 933771059 Limited company (AS) Gjesdal Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 11.5m
Operating profit NOK 5.7m
Equity NOK 3.4m
Incorporated 2024
Employees 5
Share capital NOK 100,000

EI REVISJON OG RÅDGIVNING AS is registered as a limited company in Gjesdal, Rogaland with organisation number 933771059. The business is classified under auditing (NACE 69.201). The company was incorporated in 2024 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Revisjon, regnskapsføring og konsulentvirksomhet innenfor regnskap, økonomi og ledelse, samt hva herved står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 11.5m in revenue and NOK 5.7m in operating profit.

Key figures · 2025

Revenue
NOK 11.5m
Operating profit
NOK 5.7m
Equity
NOK 3.4m
Est. value
NOK 19.9m

Financial health · 2025

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

Who owns EI REVISJON OG RÅDGIVNING AS?

3MAST HOLDING AS
EI REVISJON OG RÅDGIVNING AS
NOK 11.5m rev. · NOK 5.7m profit

EI REVISJON OG RÅDGIVNING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EI REVISJON OG RÅDGIVNING AS

Who owns EI REVISJON OG RÅDGIVNING AS?

3MAST HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of EI REVISJON OG RÅDGIVNING AS?

EI REVISJON OG RÅDGIVNING AS had revenue of NOK 11.5m in 2025.

Who is the general manager of EI REVISJON OG RÅDGIVNING AS?

Stein Rhoar Juul is registered as general manager of EI REVISJON OG RÅDGIVNING AS.

Where is EI REVISJON OG RÅDGIVNING AS based?

EI REVISJON OG RÅDGIVNING AS has its business address in Ålgård.

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.