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

BYVY SAMEIE

Org. no. 935303532 Condominium flat owner (ESEK) Trondheim Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 998,000
Operating profit NOK 460,000
Equity NOK 466,000
Incorporated 2024

BYVY SAMEIE is registered as a condominium flat owner in Trondheim, Trøndelag with organisation number 935303532. 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 998,000 in revenue and NOK 460,000 in operating profit.

Key figures · 2025

Revenue
NOK 998,000
Operating profit
NOK 460,000
Equity
NOK 466,000
Est. value
NOK 1.6m

Financial health · 2025

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

Who owns BYVY SAMEIE?

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

Frequently asked questions about BYVY SAMEIE

What is the revenue of BYVY SAMEIE?

BYVY SAMEIE had revenue of NOK 998,000 in 2025.

Where is BYVY SAMEIE based?

BYVY SAMEIE has its business address in Trondheim.

Property

Business address c/o Boligbyggelaget Tobb Krambugata 7, 7011 Trondheim
Cadastral unit 5001-401/322/0/0
Building Annen kontorbygning · 1 unit

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