biztrac. BETA
COMPANY REGISTER PROFILE
946313513 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Activities of housing cooperatives

Granli Borettslag A/L

Org. no. 946313513 Housing cooperative (BRL) Ringerike Incorporated 1966 Active
Revenue 2025 NOK 1.8m
Operating profit NOK 562,000
Equity NOK 2.0m
Incorporated 1966

Granli Borettslag A/L is registered as a housing cooperative in Ringerike, Buskerud with organisation number 946313513. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 1966. The company's stated purpose is: “Skaffe andelseierne bolig ved å erverve eller forestå oppføringen av boligbygg og leie ut boliger i slike bygg til andelseierne. Laget har dessuten til formål å erverve eller forestå opp- føringen av andre bygg enn boligbygg (herunder garasjer) når de skal brukes til felles formål for andelseierne, eller når utleie av lokalene i slike bygg skal skje i sammenheng med lagets øvrige virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK 562,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
▲ +3 %
Operating profit
NOK 562,000
▼ −12 %
Equity
NOK 2.0m
▲ +15 %
Est. value
NOK 2.5m

Financial health · 2025

Liquidity
7.40
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
20.3%
Good
Equity as a share of total capital

Who owns Granli Borettslag A/L?

No shareholders are registered for Granli Borettslag A/L in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about Granli Borettslag A/L

What is the revenue of Granli Borettslag A/L?

Granli Borettslag A/L had revenue of NOK 1.8m in 2025.

Where is Granli Borettslag A/L based?

Granli Borettslag A/L has its business address in Hønefoss.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.