BIZTRAC BETA
Accounting and bookkeeping

ALETT REGNSKAPSHJELP AS

Org. no. 997939999 Limited company (AS) Bergen Incorporated 2012 Active
Ownership graph ↗
Operating profit NOK −1,000
Equity NOK −46,000
Incorporated 2012
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−46k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1k kr).

ALETT REGNSKAPSHJELP AS is registered as a limited company in Bergen, Vestland with organisation number 997939999. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Opplæring, bemanning og bistand innen økonomi, regnskap og ledelse, samt andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”.

Key figures · 2024

Operating profit
NOK −1,000
Equity
NOK −46,000

Financial health · 2024

Liquidity
0.62
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-60.7%
Weak
Equity as a share of total capital

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

Who owns ALETT REGNSKAPSHJELP AS?

FRODE SØVDE
ALETT REGNSKAPSHJELP AS
· NOK −1,000 profit

ALETT REGNSKAPSHJELP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ALETT REGNSKAPSHJELP AS

Who owns ALETT REGNSKAPSHJELP AS?

FRODE SØVDE is the largest registered owner, with 100.0%.

Who is the general manager of ALETT REGNSKAPSHJELP AS?

Frode Søvde is registered as general manager of ALETT REGNSKAPSHJELP AS.

Where is ALETT REGNSKAPSHJELP AS based?

ALETT REGNSKAPSHJELP AS has its business address in Bergen.

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.