BIZTRAC BETA
Accounting and bookkeeping

AVESTO ØKONOMITJENESTER AS

Org. no. 923719008 Limited company (AS) Drammen Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 408,000
Operating profit NOK −3,000
Equity NOK 145,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−3k kr).

AVESTO ØKONOMITJENESTER AS is registered as a limited company in Drammen, Buskerud with organisation number 923719008. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 6 shares. The company's stated purpose is: “Rådgivnings- og regnskapsførervirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 408,000 in revenue and NOK −3,000 in operating profit.

Key figures · 2024

Revenue
NOK 408,000
Operating profit
NOK −3,000
Equity
NOK 145,000
Est. value
NOK 499,000

Financial health · 2024

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

Who owns AVESTO ØKONOMITJENESTER AS?

SHANAZ KANABI
AVESTO ØKONOMITJENESTER AS
NOK 408,000 rev. · NOK −3,000 profit

AVESTO ØKONOMITJENESTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AVESTO ØKONOMITJENESTER AS

Who owns AVESTO ØKONOMITJENESTER AS?

SHANAZ KANABI is the largest registered owner, with 100.0%.

What is the revenue of AVESTO ØKONOMITJENESTER AS?

AVESTO ØKONOMITJENESTER AS had revenue of NOK 408,000 in 2024.

Who is the general manager of AVESTO ØKONOMITJENESTER AS?

Shanaz Kanabi is registered as general manager of AVESTO ØKONOMITJENESTER AS.

Where is AVESTO ØKONOMITJENESTER AS based?

AVESTO ØKONOMITJENESTER AS has its business address in Drammen.

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.