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

HOSLETUNET BOLIGSAMEIE

Org. no. 975608816 Condominium flat owner (ESEK) Bærum Incorporated 1988 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Equity NOK 1.0m
Incorporated 1988

HOSLETUNET BOLIGSAMEIE is registered as a condominium flat owner in Bærum, Akershus with organisation number 975608816. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 1988. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue.

Former names: HOSLETUNET BOLIGSAMEIE V/ADV. LARGE

Key figures · 2025

Revenue
NOK 1.2m
Equity
NOK 1.0m
Est. value
NOK 1.5m

Financial health · 2025

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

Who owns HOSLETUNET BOLIGSAMEIE?

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

Frequently asked questions about HOSLETUNET BOLIGSAMEIE

What is the revenue of HOSLETUNET BOLIGSAMEIE?

HOSLETUNET BOLIGSAMEIE had revenue of NOK 1.2m in 2025.

Where is HOSLETUNET BOLIGSAMEIE based?

HOSLETUNET BOLIGSAMEIE has its business address in Sandvika.

Property

Business address Kinoveien 3, 1337 Sandvika
Cadastral unit 3201-7/39/0/0
Building Kontor- og administrasjonsbygning, rådhus · 14 units

83 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.