BIZTRAC BETA
Rental and operating of own or leased real estate

BRAGERNES TORG 12 AS

Org. no. 924205970 Limited company (AS) Asker Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 8.2m
Operating profit NOK 5.5m
Equity NOK 73.8m
Incorporated 2019
Share capital NOK 927,000

BRAGERNES TORG 12 AS is registered as a limited company in Asker, Akershus with organisation number 924205970. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 927,000, divided into 1500 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 8.2m in revenue and NOK 5.5m in operating profit.

Key figures · 2024

Revenue
NOK 8.2m
Operating profit
NOK 5.5m
Equity
NOK 73.8m
Est. value
NOK 65.9m

Financial health · 2024

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

Who owns BRAGERNES TORG 12 AS?

AVA EIENDOMSPARTNER AS
BRAGERNES TORG 12 AS
NOK 8.2m rev. · NOK 5.5m profit

BRAGERNES TORG 12 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

BRAGERNES TORG 12 AS er morselskap for 23 datterselskaper:

Frequently asked questions about BRAGERNES TORG 12 AS

Who owns BRAGERNES TORG 12 AS?

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

What is the revenue of BRAGERNES TORG 12 AS?

BRAGERNES TORG 12 AS had revenue of NOK 8.2m in 2024.

Who is the general manager of BRAGERNES TORG 12 AS?

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

Where is BRAGERNES TORG 12 AS based?

BRAGERNES TORG 12 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.