BIZTRAC BETA
Auditing

GJERDE HANSEN REVISJON AS

Org. no. 989132903 Limited company (AS) Bærum Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 182,000
Equity NOK 1.0m
Incorporated 2005
Share capital NOK 100,000

GJERDE HANSEN REVISJON AS is registered as a limited company in Bærum, Akershus with organisation number 989132903. The business is classified under auditing (NACE 69.201). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Revisjonsvirksomhet, konsulentbistand, regnskapsførsel, samt hva dermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet. ”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 182,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 182,000
Equity
NOK 1.0m
Est. value
NOK 1.6m

Financial health · 2025

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

Who owns GJERDE HANSEN REVISJON AS?

ARNLAUG GJERDE HANSEN
GJERDE HANSEN REVISJON AS
NOK 1.3m rev. · NOK 182,000 profit

GJERDE HANSEN REVISJON AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GJERDE HANSEN REVISJON AS

Who owns GJERDE HANSEN REVISJON AS?

ARNLAUG GJERDE HANSEN is the largest registered owner, with 100.0%.

What is the revenue of GJERDE HANSEN REVISJON AS?

GJERDE HANSEN REVISJON AS had revenue of NOK 1.3m in 2025.

Who is the general manager of GJERDE HANSEN REVISJON AS?

Arnlaug Gjerde Hansen is registered as general manager of GJERDE HANSEN REVISJON AS.

Where is GJERDE HANSEN REVISJON AS based?

GJERDE HANSEN REVISJON AS has its business address in Rud.

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.