biztrac. BETA
COMPANY REGISTER PROFILE
971281251 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Activities of housing cooperatives

SAMEIET EKEBERGUTSIKT

Org. no. 971281251 Condominium flat owner (ESEK) Oslo Incorporated 1983 Active
Revenue 2025 NOK 3.4m
Operating profit NOK 1.8m
Equity NOK −1.1m
Incorporated 1983

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,1 mill kr).

SAMEIET EKEBERGUTSIKT is registered as a condominium flat owner in Oslo, Oslo with organisation number 971281251. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 1983. The company's stated purpose is: “Ivareta sameiernes fellesinteresser og administrasjon av eiendommen gnr 233 bnr 125, 126, 129, 131, 132, 134 og 135 i Oslo, med fellesanlegg av enhver art.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.4m in revenue and NOK 1.8m in operating profit.

Former names: SAMEIET EKEBERGBYGG V/ ADV. DÆHLI, SAMEIET EKEBERGBYGG

Key figures · 2025

Revenue
NOK 3.4m
▲ +91 %
Operating profit
NOK 1.8m
▲ +1074 %
Equity
NOK −1.1m
▲ +60 %
Est. value
NOK 4.6m

Financial health · 2025

Liquidity
22.41
Very good
Current assets ÷ current liabilities
Profitability
179.4%
Very good
Return on total assets
Solidity
-60.6%
Weak
Equity as a share of total capital

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

Who owns SAMEIET EKEBERGUTSIKT?

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

Frequently asked questions about SAMEIET EKEBERGUTSIKT

What is the revenue of SAMEIET EKEBERGUTSIKT?

SAMEIET EKEBERGUTSIKT had revenue of NOK 3.4m in 2025.

Where is SAMEIET EKEBERGUTSIKT based?

SAMEIET EKEBERGUTSIKT has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.