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

KEST SAMEIGE

Org. no. 920028438 Condominium flat owner (ESEK) Kvinnherad Incorporated 2010 Active
Ownership graph ↗
Revenue 2023 NOK 900,000
Operating profit NOK 51,000
Equity NOK 457,000
Incorporated 2010

KEST SAMEIGE is registered as a condominium flat owner in Kvinnherad, Vestland with organisation number 920028438. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2010. The company's stated purpose is: “Eierseksjonssameie”. The most recent filed accounts, for the 2023 financial year, show NOK 900,000 in revenue and NOK 51,000 in operating profit.

Key figures · 2023

Revenue
NOK 900,000
Operating profit
NOK 51,000
Equity
NOK 457,000
Est. value
NOK 510,000

Financial health · 2023

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

Who owns KEST SAMEIGE?

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

Frequently asked questions about KEST SAMEIGE

What is the revenue of KEST SAMEIGE?

KEST SAMEIGE had revenue of NOK 900,000 in 2023.

Where is KEST SAMEIGE based?

KEST SAMEIGE has its business address in Husnes.

Property

Business address Stabburshaugen 5, 5460 Husnes
Cadastral unit 4617-143/173/0/0
Building Annen kontorbygning · 19 units

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