BIZTRAC BETA
Rental and operating of own or leased real estate

BRATSBERGVEIEN 11-15 AS

Org. no. 912125408 Limited company (AS) Trondheim Incorporated 1952 Active
Ownership graph ↗
Revenue 2024 NOK 10.3m
Operating profit NOK 6.5m
Equity NOK 34.9m
Incorporated 1952
Share capital NOK 3.6m

Signals

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

BRATSBERGVEIEN 11-15 AS is registered as a limited company in Trondheim, Trøndelag with organisation number 912125408. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1952. Registered share capital is NOK 3.6m. The company's stated purpose is: “Handel, kjøp, salg og forvaltning av fast eiendom, samt engasjere seg økonomisk i andre selskaper ved aksjetegning eller på annen måte.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.3m in revenue and NOK 6.5m in operating profit.

Key figures · 2024

Revenue
NOK 10.3m
Operating profit
NOK 6.5m
Equity
NOK 34.9m
Est. value
NOK 40.3m

Financial health · 2024

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

Who owns BRATSBERGVEIEN 11-15 AS?

COOP MIDT-NORGE SA
BRATSBERGVEIEN 11-15 AS
NOK 10.3m rev. · NOK 6.5m profit

BRATSBERGVEIEN 11-15 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRATSBERGVEIEN 11-15 AS

Who owns BRATSBERGVEIEN 11-15 AS?

COOP MIDT-NORGE SA is the largest registered owner, with 100.0%.

What is the revenue of BRATSBERGVEIEN 11-15 AS?

BRATSBERGVEIEN 11-15 AS had revenue of NOK 10.3m in 2024.

Where is BRATSBERGVEIEN 11-15 AS based?

BRATSBERGVEIEN 11-15 AS has its business address in Trondheim.

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.