BIZTRAC BETA
Accounting and bookkeeping

KAUPANGER REKNESKAPSKONTOR AS

Org. no. 994694448 Limited company (AS) Sogndal Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 3.9m
Operating profit NOK 22,000
Equity NOK 672,000
Incorporated 2009
Employees 6
Share capital NOK 100,000

KAUPANGER REKNESKAPSKONTOR AS is registered as a limited company in Sogndal, Vestland with organisation number 994694448. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2009 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Rekneskapstenester, økonomisk rådgjeving og tilhøyrande tenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.9m in revenue and NOK 22,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.9m
Operating profit
NOK 22,000
Equity
NOK 672,000
Est. value
NOK 481,000

Financial health · 2024

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

Who owns KAUPANGER REKNESKAPSKONTOR AS?

VÅR INVEST AS
KAUPANGER REKNESKAPSKONTOR AS
NOK 3.9m rev. · NOK 22,000 profit

KAUPANGER REKNESKAPSKONTOR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KAUPANGER REKNESKAPSKONTOR AS

Who owns KAUPANGER REKNESKAPSKONTOR AS?

VÅR INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of KAUPANGER REKNESKAPSKONTOR AS?

KAUPANGER REKNESKAPSKONTOR AS had revenue of NOK 3.9m in 2024.

Who is the general manager of KAUPANGER REKNESKAPSKONTOR AS?

Eirik Bøyum is registered as general manager of KAUPANGER REKNESKAPSKONTOR AS.

Where is KAUPANGER REKNESKAPSKONTOR AS based?

KAUPANGER REKNESKAPSKONTOR AS has its business address in Kaupanger.

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.