BIZTRAC BETA
Accounting and bookkeeping

REKNESKAP FJORDANE AS

Org. no. 997003543 Limited company (AS) Sunnfjord Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 26.5m
Operating profit NOK 4.6m
Equity NOK 104,000
Incorporated 2011
Employees 22
Share capital NOK 100,000

REKNESKAP FJORDANE AS is registered as a limited company in Sunnfjord, Vestland with organisation number 997003543. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2011 and has 22 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utføre rekneskapstenester, økonomisk rådgivning og konsulenttenester for næringsdrivande og bedriftskundar, samt det som høyrer inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 26.5m in revenue and NOK 4.6m in operating profit.

Key figures · 2025

Revenue
NOK 26.5m
Operating profit
NOK 4.6m
Equity
NOK 104,000
Est. value
NOK 21.4m

Financial health · 2025

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

Who owns REKNESKAP FJORDANE AS?

REF INVEST AS
REKNESKAP FJORDANE AS
NOK 26.5m rev. · NOK 4.6m profit

REKNESKAP FJORDANE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about REKNESKAP FJORDANE AS

Who owns REKNESKAP FJORDANE AS?

REF INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of REKNESKAP FJORDANE AS?

REKNESKAP FJORDANE AS had revenue of NOK 26.5m in 2025.

Who is the general manager of REKNESKAP FJORDANE AS?

André Haugsbø is registered as general manager of REKNESKAP FJORDANE AS.

Where is REKNESKAP FJORDANE AS based?

REKNESKAP FJORDANE AS has its business address in Sande I Sunnfjord.

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.