BIZTRAC BETA
Rental and operating of own or leased real estate

BELLEVUE 2 AS

Org. no. 913416546 Limited company (AS) Lillesand Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 43,000
Operating profit NOK 19,000
Equity NOK 774,000
Incorporated 2014
Share capital NOK 774,000

Signals

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

BELLEVUE 2 AS is registered as a limited company in Lillesand, Agder with organisation number 913416546. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 774,000, divided into 30 shares. The company's stated purpose is: “Kjøp, utvikling, utleie og salg av eiendommer og alt det som står i forbindelse med dette. ”. The most recent filed accounts, for the 2025 financial year, show NOK 43,000 in revenue and NOK 19,000 in operating profit.

Key figures · 2025

Revenue
NOK 43,000
Operating profit
NOK 19,000
Equity
NOK 774,000
Est. value
NOK 563,000

Financial health · 2025

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

Who owns BELLEVUE 2 AS?

OLE OLSEN HOLDING AS
BELLEVUE 2 AS
NOK 43,000 rev. · NOK 19,000 profit

BELLEVUE 2 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BELLEVUE 2 AS

Who owns BELLEVUE 2 AS?

OLE OLSEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BELLEVUE 2 AS?

BELLEVUE 2 AS had revenue of NOK 43,000 in 2025.

Who is the general manager of BELLEVUE 2 AS?

Ole Haus Olsen is registered as general manager of BELLEVUE 2 AS.

Where is BELLEVUE 2 AS based?

BELLEVUE 2 AS has its business address in Lillesand.

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.