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

VY SAMEIE

Org. no. 929839838 Condominium flat owner (ESEK) Bergen Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 707,000
Operating profit NOK 158,000
Equity NOK 212,000
Incorporated 2021

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

Key figures · 2025

Revenue
NOK 707,000
Operating profit
NOK 158,000
Equity
NOK 212,000
Est. value
NOK 586,000

Financial health · 2025

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

Who owns VY SAMEIE?

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

Frequently asked questions about VY SAMEIE

What is the revenue of VY SAMEIE?

VY SAMEIE had revenue of NOK 707,000 in 2025.

Where is VY SAMEIE based?

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