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

SAMEIET HOVDEN APPARTEMENT

Org. no. 879868602 Condominium flat owner (ESEK) Bykle Incorporated 1993 Active
Ownership graph ↗
Revenue 2025 NOK 1.8m
Operating profit NOK 640,000
Equity NOK 1.5m
Incorporated 1993

SAMEIET HOVDEN APPARTEMENT is registered as a condominium flat owner in Bykle, Agder with organisation number 879868602. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 1993. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK 640,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
Operating profit
NOK 640,000
Equity
NOK 1.5m
Est. value
NOK 2.8m

Financial health · 2025

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

Who owns SAMEIET HOVDEN APPARTEMENT?

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

Frequently asked questions about SAMEIET HOVDEN APPARTEMENT

What is the revenue of SAMEIET HOVDEN APPARTEMENT?

SAMEIET HOVDEN APPARTEMENT had revenue of NOK 1.8m in 2025.

Where is SAMEIET HOVDEN APPARTEMENT based?

SAMEIET HOVDEN APPARTEMENT has its business address in Hovden I Setesdal.

Property

Business address Hovden Appartement 18, 4755 Hovden I Setesdal
Cadastral unit 4222-1/113/0/0
Building Appartement · 20 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.