BIZTRAC BETA
Rental and operating of own or leased real estate

BRAGERNES TORG 8 AS

Org. no. 943467749 Limited company (AS) Asker Incorporated 1987 Active
Ownership graph ↗
Revenue 2024 NOK 5.0m
Operating profit NOK 4.3m
Equity NOK 6.0m
Incorporated 1987
Share capital NOK 1.1m

BRAGERNES TORG 8 AS is registered as a limited company in Asker, Akershus with organisation number 943467749. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1987. Registered share capital is NOK 1.1m, divided into 600 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.0m in revenue and NOK 4.3m in operating profit.

Key figures · 2024

Revenue
NOK 5.0m
Operating profit
NOK 4.3m
Equity
NOK 6.0m
Est. value
NOK 12.5m

Financial health · 2024

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

Who owns BRAGERNES TORG 8 AS?

AVA EIENDOMSPARTNER AS
BRAGERNES TORG 8 AS
NOK 5.0m rev. · NOK 4.3m profit

BRAGERNES TORG 8 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

BRAGERNES TORG 8 AS er morselskap for 23 datterselskaper:

Frequently asked questions about BRAGERNES TORG 8 AS

Who owns BRAGERNES TORG 8 AS?

AVA EIENDOMSPARTNER AS is the largest registered owner, with 100.0%.

What is the revenue of BRAGERNES TORG 8 AS?

BRAGERNES TORG 8 AS had revenue of NOK 5.0m in 2024.

Who is the general manager of BRAGERNES TORG 8 AS?

Arne Vannebo is registered as general manager of BRAGERNES TORG 8 AS.

Where is BRAGERNES TORG 8 AS based?

BRAGERNES TORG 8 AS has its business address in Asker.

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.