BIZTRAC BETA
Accounting and bookkeeping

BJERKREIM REKNESKAPSKONTOR AS

Org. no. 971068450 Limited company (AS) Bjerkreim Incorporated 1994 Active
Ownership graph ↗
Revenue 2025 NOK 7.7m
Operating profit NOK 116,000
Equity NOK 772,000
Incorporated 1994
Employees 10
Share capital NOK 100,000

BJERKREIM REKNESKAPSKONTOR AS is registered as a limited company in Bjerkreim, Rogaland with organisation number 971068450. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 1994 and has 10 registered employees. Registered share capital is NOK 100,000. The company's stated purpose is: “Drift av regnskapskontor, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.7m in revenue and NOK 116,000 in operating profit.

Key figures · 2025

Revenue
NOK 7.7m
Operating profit
NOK 116,000
Equity
NOK 772,000
Est. value
NOK 948,000

Financial health · 2025

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

Who owns BJERKREIM REKNESKAPSKONTOR AS?

JOSTEIN RØYSLAND
BJERKREIM REKNESKAPSKONTOR AS
NOK 7.7m rev. · NOK 116,000 profit

BJERKREIM REKNESKAPSKONTOR AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about BJERKREIM REKNESKAPSKONTOR AS

Who owns BJERKREIM REKNESKAPSKONTOR AS?

JOSTEIN RØYSLAND is the largest registered owner, with 33.0%.

What is the revenue of BJERKREIM REKNESKAPSKONTOR AS?

BJERKREIM REKNESKAPSKONTOR AS had revenue of NOK 7.7m in 2025.

Who is the general manager of BJERKREIM REKNESKAPSKONTOR AS?

Torunn Bjerkreim Moi is registered as general manager of BJERKREIM REKNESKAPSKONTOR AS.

Where is BJERKREIM REKNESKAPSKONTOR AS based?

BJERKREIM REKNESKAPSKONTOR AS has its business address in Vikeså.

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.