BIZTRAC BETA
Accounting and bookkeeping

REGNSKAPSKONTORET STOKKE AS

Org. no. 997746848 Limited company (AS) Sandefjord Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 13.9m
Operating profit NOK 3.7m
Equity NOK 357,000
Incorporated 2011
Employees 10
Share capital NOK 300,000

REGNSKAPSKONTORET STOKKE AS is registered as a limited company in Sandefjord, Vestfold with organisation number 997746848. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2011 and has 10 registered employees. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Regnskapsføring, bokføring, lønnskjøring med tilhørende konsulent tjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 13.9m in revenue and NOK 3.7m in operating profit.

Key figures · 2024

Revenue
NOK 13.9m
Operating profit
NOK 3.7m
Equity
NOK 357,000
Est. value
NOK 13.3m

Financial health · 2024

Liquidity
1.03
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
5.8%
Weak
Equity as a share of total capital

Who owns REGNSKAPSKONTORET STOKKE AS?

BDL HOLDING AS
REGNSKAPSKONTORET STOKKE AS
NOK 13.9m rev. · NOK 3.7m profit

REGNSKAPSKONTORET STOKKE AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about REGNSKAPSKONTORET STOKKE AS

Who owns REGNSKAPSKONTORET STOKKE AS?

BDL HOLDING AS is the largest registered owner, with 30.0%.

What is the revenue of REGNSKAPSKONTORET STOKKE AS?

REGNSKAPSKONTORET STOKKE AS had revenue of NOK 13.9m in 2024.

Who is the general manager of REGNSKAPSKONTORET STOKKE AS?

Bent Dyrøy Lohne is registered as general manager of REGNSKAPSKONTORET STOKKE AS.

Where is REGNSKAPSKONTORET STOKKE AS based?

REGNSKAPSKONTORET STOKKE AS has its business address in Stokke.

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.