BIZTRAC BETA
Business and other management consultancy activities

AVERE AS

Org. no. 928182835 Limited company (AS) Bærum Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −23,000
Equity NOK 393,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

AVERE AS is registered as a limited company in Bærum, Akershus with organisation number 928182835. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Rådgivning, forfattervirksomhet og andre aktiviteter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −23,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −23,000
Equity
NOK 393,000
Est. value
NOK 814,000

Financial health · 2024

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

Who owns AVERE AS?

JAN FOSSE
AVERE AS
NOK 0 rev. · NOK −23,000 profit

AVERE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does AVERE AS own?

AVERE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about AVERE AS

Who owns AVERE AS?

JAN FOSSE is the largest registered owner, with 100.0%.

What is the revenue of AVERE AS?

AVERE AS had revenue of NOK 0 in 2024.

Where is AVERE AS based?

AVERE AS has its business address in Bekkestua.

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.