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

BOLIGSAMEIET K1

Org. no. 988975516 Condominium flat owner (ESEK) Tromsø Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 2.7m
Operating profit NOK 414,000
Equity NOK 3.0m
Incorporated 2005

BOLIGSAMEIET K1 is registered as a condominium flat owner in Tromsø, Troms with organisation number 988975516. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2005. The company's stated purpose is: “Eierseksjonssameie.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.7m in revenue and NOK 414,000 in operating profit.

Former names: EIERSEKSJONSSAMEIET K1

Key figures · 2025

Revenue
NOK 2.7m
Operating profit
NOK 414,000
Equity
NOK 3.0m
Est. value
NOK 3.4m

Financial health · 2025

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

Who owns BOLIGSAMEIET K1?

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

Frequently asked questions about BOLIGSAMEIET K1

What is the revenue of BOLIGSAMEIET K1?

BOLIGSAMEIET K1 had revenue of NOK 2.7m in 2025.

Where is BOLIGSAMEIET K1 based?

BOLIGSAMEIET K1 has its business address in Tromsø.

Property

Business address v/ Line Fusdahl Sjøgata 16, 9008 Tromsø
Cadastral unit 5501-200/1255/0/0
Building Butikkbygning · 1 unit

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.