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

GEILOBRUA SAMEIE

Org. no. 993151874 Condominium flat owner (ESEK) Hol Incorporated 2008 Active
Ownership graph ↗
Revenue 2018 NOK 465,000
Operating profit NOK 50,000
Equity NOK 256,000
Incorporated 2008

GEILOBRUA SAMEIE is registered as a condominium flat owner in Hol, Buskerud with organisation number 993151874. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2008. The company's stated purpose is: “Eierseksjonssameie.”. The most recent filed accounts, for the 2018 financial year, show NOK 465,000 in revenue and NOK 50,000 in operating profit.

Key figures · 2018

Revenue
NOK 465,000
Operating profit
NOK 50,000
Equity
NOK 256,000
Est. value
NOK 359,000

Financial health · 2018

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

Who owns GEILOBRUA SAMEIE?

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

Frequently asked questions about GEILOBRUA SAMEIE

What is the revenue of GEILOBRUA SAMEIE?

GEILOBRUA SAMEIE had revenue of NOK 465,000 in 2018.

Where is GEILOBRUA SAMEIE based?

GEILOBRUA SAMEIE has its business address in Geilo.

Property

Business address co Sidsel Fjørtoft Skurdalsvegen 26, 3580 Geilo
Cadastral unit 3330-65/160/0/0
Building Kjøpesenter, varehus · 19 units

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