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

SAMEIET SAGALI

Org. no. 818299842 Condominium flat owner (ESEK) Alta Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 475,000
Operating profit NOK 165,000
Equity NOK 789,000
Incorporated 2016

SAMEIET SAGALI is registered as a condominium flat owner in Alta, Finnmark with organisation number 818299842. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2016. The company's stated purpose is: “Eierseksjonssameie.”. The most recent filed accounts, for the 2025 financial year, show NOK 475,000 in revenue and NOK 165,000 in operating profit.

Key figures · 2025

Revenue
NOK 475,000
Operating profit
NOK 165,000
Equity
NOK 789,000
Est. value
NOK 1.0m

Financial health · 2025

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

Who owns SAMEIET SAGALI?

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

Frequently asked questions about SAMEIET SAGALI

What is the revenue of SAMEIET SAGALI?

SAMEIET SAGALI had revenue of NOK 475,000 in 2025.

Where is SAMEIET SAGALI based?

SAMEIET SAGALI has its business address in Alta.

Property

Business address C/O Erling-Christoffer Suhr Sagali 24C, 9517 Alta
Cadastral unit 5601-38/738/0/0
Building Rekkehus · 3 units

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