biztrac. BETA
COMPANY REGISTER PROFILE
929809629 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

ARONS VEI 5 EIENDOM AS

Org. no. 929809629 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 2.6m
Operating profit NOK 1.5m
Equity NOK 12.9m
Incorporated 2022
Share capital NOK 72,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ARONS VEI 5 EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 929809629. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 72,000, divided into 200 shares. The company's stated purpose is: “Utleie av fast eiendom og det som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.6m in revenue and NOK 1.5m in operating profit.

Key figures · 2025

Revenue
NOK 2.6m
▲ +11 %
Operating profit
NOK 1.5m
▲ +7 %
Equity
NOK 12.9m
▼ −0 %
Est. value
NOK 11.8m

Financial health · 2025

Liquidity
0.56
Weak
Current assets ÷ current liabilities
Profitability
6.2%
Satisfactory
Return on total assets
Solidity
56.9%
Very good
Equity as a share of total capital

Who owns ARONS VEI 5 EIENDOM AS?

ARONS VEI 5 EIENDOM AS
NOK 2.6m rev. · NOK 1.5m profit

ARONS VEI 5 EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ARONS VEI 5 EIENDOM AS

Who owns ARONS VEI 5 EIENDOM AS?

CIBUS SALMO AS is the largest registered owner, with 100.0%.

What is the revenue of ARONS VEI 5 EIENDOM AS?

ARONS VEI 5 EIENDOM AS had revenue of NOK 2.6m in 2025.

Where is ARONS VEI 5 EIENDOM AS based?

ARONS VEI 5 EIENDOM 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.