BIZTRAC BETA
Rental and operating of own or leased real estate

AVINUS EIENDOM AS

Org. no. 989155865 Limited company (AS) Ullensaker Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK −58,000
Equity NOK 3.2m
Incorporated 2005
Share capital NOK 100,000

Signals

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

AVINUS EIENDOM AS is registered as a limited company in Ullensaker, Akershus with organisation number 989155865. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 2500000 shares. The company's stated purpose is: “Kjøp, salg og drift av fast eiendom samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK −58,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK −58,000
Equity
NOK 3.2m
Est. value
NOK 3.9m

Financial health · 2024

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

Who owns AVINUS EIENDOM AS?

ANNE LOUISE FURUSETH VOLLEBÆK
AVINUS EIENDOM AS
NOK 1.1m rev. · NOK −58,000 profit

AVINUS EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about AVINUS EIENDOM AS

Who owns AVINUS EIENDOM AS?

ANNE LOUISE FURUSETH VOLLEBÆK is the largest registered owner, with 50.0%.

What is the revenue of AVINUS EIENDOM AS?

AVINUS EIENDOM AS had revenue of NOK 1.1m in 2024.

Who is the general manager of AVINUS EIENDOM AS?

Anne Louise Furuseth Vollebæk is registered as general manager of AVINUS EIENDOM AS.

Where is AVINUS EIENDOM AS based?

AVINUS EIENDOM AS has its business address in Algarheim.

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.