BIZTRAC BETA
Auditing

FRAM REVISJON AS

Org. no. 957668933 Limited company (AS) Elverum Incorporated 1990 Active
Ownership graph ↗
Revenue 2024 NOK 35.2m
Operating profit NOK 6.0m
Equity NOK 1.5m
Incorporated 1990
Employees 22
Share capital NOK 96,000

FRAM REVISJON AS is registered as a limited company in Elverum, Innlandet with organisation number 957668933. The business is classified under auditing (NACE 69.201). The company was incorporated in 1990 and has 22 registered employees. Registered share capital is NOK 96,000, divided into 96 shares. The company's stated purpose is: “Revisjonsvirksomhet, forretnignsførsel herunder å føre regnskap for andre selskaper, konsulentbistand og annen virksomhet i forbindelse med dette. Selskapet kan ved aksjetegning eller på andre måter ha eierinteresser i andre selskaper med samme eller lignende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 35.2m in revenue and NOK 6.0m in operating profit.

Key figures · 2024

Revenue
NOK 35.2m
Operating profit
NOK 6.0m
Equity
NOK 1.5m
Est. value
NOK 28.8m

Financial health · 2024

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

Who owns FRAM REVISJON AS?

EØS INVEST AS
FRAM REVISJON AS
NOK 35.2m rev. · NOK 6.0m profit

FRAM REVISJON AS has 11 registered shareholders:

All shareholders and roles →

Frequently asked questions about FRAM REVISJON AS

Who owns FRAM REVISJON AS?

EØS INVEST AS is the largest registered owner, with 31.2%.

What is the revenue of FRAM REVISJON AS?

FRAM REVISJON AS had revenue of NOK 35.2m in 2024.

Who is the general manager of FRAM REVISJON AS?

Erlend Øverby Sund is registered as general manager of FRAM REVISJON AS.

Where is FRAM REVISJON AS based?

FRAM REVISJON AS has its business address in Elverum.

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.