BIZTRAC BETA
Accounting and bookkeeping

ARJO REGNSKAP AS

Org. no. 916173741 Limited company (AS) Bergen Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK 32,000
Equity NOK 247,000
Incorporated 2015
Share capital NOK 30,000

ARJO REGNSKAP AS is registered as a limited company in Bergen, Vestland with organisation number 916173741. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Salg av regnskaps- og rådgivningstjenester, samt andre tjenester/produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer og eiendom, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.2m in revenue and NOK 32,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.2m
Operating profit
NOK 32,000
Equity
NOK 247,000
Est. value
NOK 299,000

Financial health · 2024

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

Who owns ARJO REGNSKAP AS?

YELLOWHOUSE AS
ARJO REGNSKAP AS
NOK 1.2m rev. · NOK 32,000 profit

ARJO REGNSKAP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ARJO REGNSKAP AS

Who owns ARJO REGNSKAP AS?

YELLOWHOUSE AS is the largest registered owner, with 100.0%.

What is the revenue of ARJO REGNSKAP AS?

ARJO REGNSKAP AS had revenue of NOK 1.2m in 2024.

Who is the general manager of ARJO REGNSKAP AS?

Arne Johansen is registered as general manager of ARJO REGNSKAP AS.

Where is ARJO REGNSKAP AS based?

ARJO REGNSKAP AS has its business address in Fyllingsdalen.

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.