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

ESEBJØRTOPPEN

Org. no. 931244051 Condominium flat owner (ESEK) Stavanger Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 543,000
Operating profit NOK 47,000
Equity NOK 370,000
Incorporated 2023

ESEBJØRTOPPEN is registered as a condominium flat owner in Stavanger, Rogaland with organisation number 931244051. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2023. The company's stated purpose is: “Eierseksjonssameie”. The most recent filed accounts, for the 2025 financial year, show NOK 543,000 in revenue and NOK 47,000 in operating profit.

Key figures · 2025

Revenue
NOK 543,000
Operating profit
NOK 47,000
Equity
NOK 370,000
Est. value
NOK 435,000

Financial health · 2025

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

Who owns ESEBJØRTOPPEN?

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

Frequently asked questions about ESEBJØRTOPPEN

What is the revenue of ESEBJØRTOPPEN?

ESEBJØRTOPPEN had revenue of NOK 543,000 in 2025.

Where is ESEBJØRTOPPEN based?

ESEBJØRTOPPEN has its business address in Stavanger.

Property

Business address Zetlitzveien 2, 4017 Stavanger
Cadastral unit 1103-20/37/0/0
Building Butikkbygning · 1 unit

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