BIZTRAC BETA
Construction of residential and non-residential buildings

GOL KOMMUNALE EIGEDOMAR BOLIGDRIFT AS

Org. no. 922246696 Limited company (AS) Gol Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 3.7m
Operating profit NOK 741,000
Equity NOK 51.8m
Incorporated 2019
Share capital NOK 18.0m

GOL KOMMUNALE EIGEDOMAR BOLIGDRIFT AS is registered as a limited company in Gol, Buskerud with organisation number 922246696. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2019. Registered share capital is NOK 18.0m, divided into 100 shares. The company's stated purpose is: “Å føre opp, eie, drifte og forvalte boliger og andre eiendommer for kommunens behov eller salg.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.7m in revenue and NOK 741,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.7m
Operating profit
NOK 741,000
Equity
NOK 51.8m
Est. value
NOK 24.3m

Financial health · 2024

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

Who owns GOL KOMMUNALE EIGEDOMAR BOLIGDRIFT AS?

GOL KOMMUNALE EIGEDOMAR AS
GOL KOMMUNALE EIGEDOMAR BOLIGDRIFT AS
NOK 3.7m rev. · NOK 741,000 profit

GOL KOMMUNALE EIGEDOMAR BOLIGDRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GOL KOMMUNALE EIGEDOMAR BOLIGDRIFT AS

Who owns GOL KOMMUNALE EIGEDOMAR BOLIGDRIFT AS?

GOL KOMMUNALE EIGEDOMAR AS is the largest registered owner, with 100.0%.

What is the revenue of GOL KOMMUNALE EIGEDOMAR BOLIGDRIFT AS?

GOL KOMMUNALE EIGEDOMAR BOLIGDRIFT AS had revenue of NOK 3.7m in 2024.

Where is GOL KOMMUNALE EIGEDOMAR BOLIGDRIFT AS based?

GOL KOMMUNALE EIGEDOMAR BOLIGDRIFT AS has its business address in Gol.

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

Report a problem

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