BIZTRAC BETA
Accounting and bookkeeping

Fenstad Regnskapskontor A/S

Org. no. 929983122 Limited company (AS) Nes Incorporated 1976 Active
Ownership graph ↗
Revenue 2025 NOK 14.9m
Operating profit NOK 1.5m
Equity NOK 1.5m
Incorporated 1976
Employees 11
Share capital NOK 50,000

Fenstad Regnskapskontor A/S is registered as a limited company in Nes, Akershus with organisation number 929983122. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 1976 and has 11 registered employees. Registered share capital is NOK 50,000, divided into 500 shares. The company's stated purpose is: “Regnskapsførervirksomhet og annen virksomhet som styret finner relevant for selskapet.”. The most recent filed accounts, for the 2025 financial year, show NOK 14.9m in revenue and NOK 1.5m in operating profit.

Key figures · 2025

Revenue
NOK 14.9m
Operating profit
NOK 1.5m
Equity
NOK 1.5m
Est. value
NOK 8.3m

Financial health · 2025

Liquidity
1.42
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
25.9%
Good
Equity as a share of total capital

Who owns Fenstad Regnskapskontor A/S?

ROLF BRUHOLT
Fenstad Regnskapskontor A/S
NOK 14.9m rev. · NOK 1.5m profit

Fenstad Regnskapskontor A/S has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about Fenstad Regnskapskontor A/S

Who owns Fenstad Regnskapskontor A/S?

ROLF BRUHOLT is the largest registered owner, with 50.0%.

What is the revenue of Fenstad Regnskapskontor A/S?

Fenstad Regnskapskontor A/S had revenue of NOK 14.9m in 2025.

Who is the general manager of Fenstad Regnskapskontor A/S?

Geir Rudolfsen is registered as general manager of Fenstad Regnskapskontor A/S.

Where is Fenstad Regnskapskontor A/S based?

Fenstad Regnskapskontor A/S has its business address in Årnes.

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.