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

LUNNER BORETTSLAG

Org. no. 882281272 Housing cooperative (BRL) Gran Incorporated 2000 Active
Ownership graph ↗
Revenue 2025 NOK 838,000
Operating profit NOK 302,000
Equity NOK 4.5m
Incorporated 2000

LUNNER BORETTSLAG is registered as a housing cooperative in Gran, Innlandet with organisation number 882281272. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2000. The company's stated purpose is: “Borettslag.”. The most recent filed accounts, for the 2025 financial year, show NOK 838,000 in revenue and NOK 302,000 in operating profit.

Key figures · 2025

Revenue
NOK 838,000
Operating profit
NOK 302,000
Equity
NOK 4.5m
Est. value
NOK 3.5m

Financial health · 2025

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

Who owns LUNNER BORETTSLAG?

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

Frequently asked questions about LUNNER BORETTSLAG

What is the revenue of LUNNER BORETTSLAG?

LUNNER BORETTSLAG had revenue of NOK 838,000 in 2025.

Where is LUNNER BORETTSLAG based?

LUNNER BORETTSLAG has its business address in Gran.

Property

Business address Smiegata 1, 2750 Gran
Cadastral unit 3446-261/66/0/0
Building Kjøpesenter, varehus · 2 units

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