biztrac. BETA
COMPANY REGISTER PROFILE
942747454 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Accounting and bookkeeping

AKSESS REGNSKAP AS

Org. no. 942747454 Limited company (AS) Oslo Incorporated 1986 Active
Operating profit NOK −2,000
Equity NOK 36,000
Incorporated 1986
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2k kr).

AKSESS REGNSKAP AS is registered as a limited company in Oslo, Oslo with organisation number 942747454. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 1986. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Tjenester innenfor området regnskap, administrasjon og økonomi, og å organiserer dette slik at kundene har tilgang til egne regnskap. Selskapet skal også kunne drive annen forretningsvirksomhet, samt hva hermed står i forbindelse, herunder å delta og investere i andre selskap.”.

Former names: RØA-SALONGEN AS

Key figures · 2025

Operating profit
NOK −2,000
▲ +68 %
Equity
NOK 36,000
▼ −4 %
Est. value
NOK 58,000

Financial health · 2025

Liquidity
45.12
Very good
Current assets ÷ current liabilities
Profitability
-1.7%
Not satisfactory
Return on total assets
Solidity
38.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns AKSESS REGNSKAP AS?

AKSESS REGNSKAP AS
· NOK −2,000 profit

AKSESS REGNSKAP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AKSESS REGNSKAP AS

Who owns AKSESS REGNSKAP AS?

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

Who is the general manager of AKSESS REGNSKAP AS?

Harald Næss is registered as general manager of AKSESS REGNSKAP AS.

Where is AKSESS REGNSKAP AS based?

AKSESS REGNSKAP AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.