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

KUBEN SAMEIE

Org. no. 933395278 Condominium flat owner (ESEK) Bergen Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 301,000
Equity NOK 452,000
Incorporated 2024

KUBEN SAMEIE is registered as a condominium flat owner in Bergen, Vestland with organisation number 933395278. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2024. The company's stated purpose is: “Eierseksjonssameie”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 301,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK 301,000
Equity
NOK 452,000
Est. value
NOK 1.2m

Financial health · 2025

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

Who owns KUBEN SAMEIE?

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

Frequently asked questions about KUBEN SAMEIE

What is the revenue of KUBEN SAMEIE?

KUBEN SAMEIE had revenue of NOK 1.4m in 2025.

Where is KUBEN SAMEIE based?

KUBEN SAMEIE has its business address in Bergen.

Property

Business address Nygårdsgaten 13, 5015 Bergen
Cadastral unit 4601-164/800/0/0
Building Kontor- og administrasjonsbygning, rådhus · 19 units

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