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

JAKTLIA 1 BOLIGSAMEIE

Org. no. 924374659 Condominium flat owner (ESEK) Bærum Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 909,000
Equity NOK 1.2m
Incorporated 2019

JAKTLIA 1 BOLIGSAMEIE is registered as a condominium flat owner in Bærum, Akershus with organisation number 924374659. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2019. The company's stated purpose is: “Eierseksjonssameie”. The most recent filed accounts, for the 2025 financial year, show NOK 909,000 in revenue.

Key figures · 2025

Revenue
NOK 909,000
Equity
NOK 1.2m
Est. value
NOK 1.4m

Financial health · 2025

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

Who owns JAKTLIA 1 BOLIGSAMEIE?

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

Frequently asked questions about JAKTLIA 1 BOLIGSAMEIE

What is the revenue of JAKTLIA 1 BOLIGSAMEIE?

JAKTLIA 1 BOLIGSAMEIE had revenue of NOK 909,000 in 2025.

Where is JAKTLIA 1 BOLIGSAMEIE based?

JAKTLIA 1 BOLIGSAMEIE has its business address in Sandvika.

Property

Business address c/o Asker og Bærum Boligbyggelag 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.