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

SAMEIGE HANSESKOGEN 20

Org. no. 935991234 Condominium flat owner (ESEK) Lærdal Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 83,000
Operating profit NOK 37,000
Equity NOK 37,000
Incorporated 2025

SAMEIGE HANSESKOGEN 20 is registered as a condominium flat owner in Lærdal, Vestland with organisation number 935991234. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2025. The most recent filed accounts, for the 2025 financial year, show NOK 83,000 in revenue and NOK 37,000 in operating profit.

Key figures · 2025

Revenue
NOK 83,000
Operating profit
NOK 37,000
Equity
NOK 37,000
Est. value
NOK 124,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SAMEIGE HANSESKOGEN 20?

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

Frequently asked questions about SAMEIGE HANSESKOGEN 20

What is the revenue of SAMEIGE HANSESKOGEN 20?

SAMEIGE HANSESKOGEN 20 had revenue of NOK 83,000 in 2025.

Where is SAMEIGE HANSESKOGEN 20 based?

SAMEIGE HANSESKOGEN 20 has its business address in Lærdal.

Property

Business address Hanseskogen 20, 6887 Lærdal
Cadastral unit 4642-31/315/0/0
Building Enebolig · 6 units

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.