BIZTRAC BETA
Auditing

WIFO REVISJON ØST AS

Org. no. 961029031 Limited company (AS) Moss Incorporated 1991 Active
Ownership graph ↗
Revenue 2025 NOK 1.8m
Operating profit NOK 678,000
Equity NOK 7.3m
Incorporated 1991
Share capital NOK 150,000

WIFO REVISJON ØST AS is registered as a limited company in Moss, Østfold with organisation number 961029031. The business is classified under auditing (NACE 69.201). The company was incorporated in 1991. Registered share capital is NOK 150,000, divided into 750 shares. The company's stated purpose is: “Revisjon og konsulentvirksomhet og alt som står i forbindelse med det, samt investering og deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK 678,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
Operating profit
NOK 678,000
Equity
NOK 7.3m
Est. value
NOK 6.9m

Financial health · 2025

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

Who owns WIFO REVISJON ØST AS?

SVEIN GEVELT FORUM
WIFO REVISJON ØST AS
NOK 1.8m rev. · NOK 678,000 profit

WIFO REVISJON ØST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does WIFO REVISJON ØST AS own?

WIFO REVISJON ØST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about WIFO REVISJON ØST AS

Who owns WIFO REVISJON ØST AS?

SVEIN GEVELT FORUM is the largest registered owner, with 100.0%.

What is the revenue of WIFO REVISJON ØST AS?

WIFO REVISJON ØST AS had revenue of NOK 1.8m in 2025.

Who is the general manager of WIFO REVISJON ØST AS?

Svein Gevelt Forum is registered as general manager of WIFO REVISJON ØST AS.

Where is WIFO REVISJON ØST AS based?

WIFO REVISJON ØST AS has its business address in Moss.

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.