BIZTRAC BETA
Accounting and bookkeeping

REGNSKAPSPIKENE AS

Org. no. 994300431 Limited company (AS) Bærum Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 4.7m
Operating profit NOK 1.0m
Equity NOK 926,000
Incorporated 2009
Share capital NOK 100,000

REGNSKAPSPIKENE AS is registered as a limited company in Bærum, Akershus with organisation number 994300431. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Fremstilling/salg av regnskapsførselstjenester og andre produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.7m in revenue and NOK 1.0m in operating profit.

Key figures · 2024

Revenue
NOK 4.7m
Operating profit
NOK 1.0m
Equity
NOK 926,000
Est. value
NOK 4.6m

Financial health · 2024

Liquidity
1.86
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
49.4%
Very good
Equity as a share of total capital

Who owns REGNSKAPSPIKENE AS?

HELLE BRINCH
REGNSKAPSPIKENE AS
NOK 4.7m rev. · NOK 1.0m profit

REGNSKAPSPIKENE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about REGNSKAPSPIKENE AS

Who owns REGNSKAPSPIKENE AS?

HELLE BRINCH is the largest registered owner, with 50.0%.

What is the revenue of REGNSKAPSPIKENE AS?

REGNSKAPSPIKENE AS had revenue of NOK 4.7m in 2024.

Who is the general manager of REGNSKAPSPIKENE AS?

Rikke Haaland Greibrokk is registered as general manager of REGNSKAPSPIKENE AS.

Where is REGNSKAPSPIKENE AS based?

REGNSKAPSPIKENE AS has its business address in Haslum.

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.