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

PARKGATA BORETTSLAG

Org. no. 888539662 Housing cooperative (BRL) Hammerfest Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 4.2m
Operating profit NOK 2.3m
Equity NOK 6.0m
Incorporated 2005

PARKGATA BORETTSLAG is registered as a housing cooperative in Hammerfest, Finnmark with organisation number 888539662. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2005. The company's stated purpose is: “Borettslag.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.2m in revenue and NOK 2.3m in operating profit.

Key figures · 2025

Revenue
NOK 4.2m
Operating profit
NOK 2.3m
Equity
NOK 6.0m
Est. value
NOK 9.4m

Financial health · 2025

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

Who owns PARKGATA BORETTSLAG?

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

Frequently asked questions about PARKGATA BORETTSLAG

What is the revenue of PARKGATA BORETTSLAG?

PARKGATA BORETTSLAG had revenue of NOK 4.2m in 2025.

Where is PARKGATA BORETTSLAG based?

PARKGATA BORETTSLAG has its business address in Hammerfest.

Property

Business address Sjøgata 9, 9600 Hammerfest
Cadastral unit 5603-25/218/0/0
Building Kjøpesenter, varehus · 2 units

78 companies are registered at this address.

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.