BIZTRAC BETA
Accounting and bookkeeping

AARTUN REGNSKAP AS

Org. no. 919367571 Limited company (AS) Sandefjord Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 1.8m
Operating profit NOK 86,000
Equity NOK 121,000
Incorporated 2017
Share capital NOK 50,000

AARTUN REGNSKAP AS is registered as a limited company in Sandefjord, Vestfold with organisation number 919367571. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2017. Registered share capital is NOK 50,000, divided into 100 shares. The company's stated purpose is: “Regnskap og bokføring, samt andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK 86,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
Operating profit
NOK 86,000
Equity
NOK 121,000
Est. value
NOK 469,000

Financial health · 2025

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

Who owns AARTUN REGNSKAP AS?

CHRISTINE AARTUN
AARTUN REGNSKAP AS
NOK 1.8m rev. · NOK 86,000 profit

AARTUN REGNSKAP AS has 1 registered shareholder:

All shareholders and roles →

Which companies does AARTUN REGNSKAP AS own?

AARTUN REGNSKAP AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about AARTUN REGNSKAP AS

Who owns AARTUN REGNSKAP AS?

CHRISTINE AARTUN is the largest registered owner, with 100.0%.

What is the revenue of AARTUN REGNSKAP AS?

AARTUN REGNSKAP AS had revenue of NOK 1.8m in 2025.

Who is the general manager of AARTUN REGNSKAP AS?

Christine Aartun is registered as general manager of AARTUN REGNSKAP AS.

Where is AARTUN REGNSKAP AS based?

AARTUN REGNSKAP AS has its business address in Sandefjord.

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.