BIZTRAC BETA
Rental and operating of own or leased real estate

BRAGERNES TORG 11 AS

Org. no. 992059052 Limited company (AS) Asker Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 8.5m
Operating profit NOK 2.4m
Equity NOK 88.9m
Incorporated 2007
Share capital NOK 2.0m

Signals

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

BRAGERNES TORG 11 AS is registered as a limited company in Asker, Akershus with organisation number 992059052. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 2.0m, divided into 10000 shares. The company's stated purpose is: “Eiendomshandel og utleie av eiendom, erverve og eie aksjer og andeler i andre selskaper, handel i finansielle instrumenter samt all annen virksomhet som naturlig hører derved.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.5m in revenue and NOK 2.4m in operating profit.

Key figures · 2024

Revenue
NOK 8.5m
Operating profit
NOK 2.4m
Equity
NOK 88.9m
Est. value
NOK 64.9m

Financial health · 2024

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

Who owns BRAGERNES TORG 11 AS?

137 HOLDING AS
BRAGERNES TORG 11 AS
NOK 8.5m rev. · NOK 2.4m profit

BRAGERNES TORG 11 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRAGERNES TORG 11 AS

Who owns BRAGERNES TORG 11 AS?

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

What is the revenue of BRAGERNES TORG 11 AS?

BRAGERNES TORG 11 AS had revenue of NOK 8.5m in 2024.

Where is BRAGERNES TORG 11 AS based?

BRAGERNES TORG 11 AS has its business address in Nesbru.

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.