BIZTRAC BETA
COMPANY REGISTER PROFILE
948907321 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Activities of housing cooperatives

GABBROVEGEN BORETTSLAG

Org. no. 948907321 Housing cooperative (BRL) Tromsø Incorporated 1979 Active
Ownership graph ↗
Revenue 2025 NOK 1.7m
Operating profit NOK 419,000
Equity NOK 2.9m
Incorporated 1979

GABBROVEGEN BORETTSLAG is registered as a housing cooperative in Tromsø, Troms with organisation number 948907321. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 1979. The company's stated purpose is: “Borettslag.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK 419,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.7m
Operating profit
NOK 419,000
Equity
NOK 2.9m
Est. value
NOK 2.7m

Financial health · 2025

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

Who owns GABBROVEGEN BORETTSLAG?

No shareholders are registered for GABBROVEGEN BORETTSLAG in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about GABBROVEGEN BORETTSLAG

What is the revenue of GABBROVEGEN BORETTSLAG?

GABBROVEGEN BORETTSLAG had revenue of NOK 1.7m in 2025.

Where is GABBROVEGEN BORETTSLAG based?

GABBROVEGEN BORETTSLAG has its business address in Krokelvdalen.

Property

Business address c/o Magne Rasch Gabbrovegen 24, 9022 Krokelvdalen
Cadastral unit 5501-14/153/0/0
Building Kjede/atriumhus · 6 units

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.