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

SAMEIET BJORLIGARD

Org. no. 989273035 Condominium flat owner (ESEK) Lesja Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 306,000
Equity NOK 662,000
Incorporated 2005

SAMEIET BJORLIGARD is registered as a condominium flat owner in Lesja, Innlandet with organisation number 989273035. 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 1.1m in revenue and NOK 306,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK 306,000
Equity
NOK 662,000
Est. value
NOK 1.3m

Financial health · 2025

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

Who owns SAMEIET BJORLIGARD?

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

Frequently asked questions about SAMEIET BJORLIGARD

What is the revenue of SAMEIET BJORLIGARD?

SAMEIET BJORLIGARD had revenue of NOK 1.1m in 2025.

Where is SAMEIET BJORLIGARD based?

SAMEIET BJORLIGARD has its business address in Bjorli.

Property

Business address Bjorligard 63, 2669 Bjorli
Cadastral unit 3432-2/766/0/0
Building Hytter, sommerhus ol fritidsbygning · 13 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.