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

TRÅLVEIEN BORETTSLAG

Org. no. 990341613 Housing cooperative (BRL) Bodø Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 939,000
Operating profit NOK 499,000
Equity NOK 2.0m
Incorporated 2006

TRÅLVEIEN BORETTSLAG is registered as a housing cooperative in Bodø, Nordland with organisation number 990341613. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2006. The company's stated purpose is: “Borettslag.”. The most recent filed accounts, for the 2025 financial year, show NOK 939,000 in revenue and NOK 499,000 in operating profit.

Key figures · 2025

Revenue
NOK 939,000
Operating profit
NOK 499,000
Equity
NOK 2.0m
Est. value
NOK 2.1m

Financial health · 2025

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

Who owns TRÅLVEIEN BORETTSLAG?

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

Frequently asked questions about TRÅLVEIEN BORETTSLAG

What is the revenue of TRÅLVEIEN BORETTSLAG?

TRÅLVEIEN BORETTSLAG had revenue of NOK 939,000 in 2025.

Where is TRÅLVEIEN BORETTSLAG based?

TRÅLVEIEN BORETTSLAG has its business address in Bodø.

Property

Business address Trålveien 42, 8013 Bodø
Cadastral unit 1804-39/255/0/0
Building Andre småhus med 3 boliger eller flere · 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.