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

SAMEIET LØVLI TERRASSE

Org. no. 814586812 Condominium flat owner (ESEK) Bergen Incorporated 1984 Active
Ownership graph ↗
Revenue 2025 NOK 12.0m
Operating profit NOK 2.8m
Equity NOK 3.3m
Incorporated 1984

SAMEIET LØVLI TERRASSE is registered as a condominium flat owner in Bergen, Vestland with organisation number 814586812. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 1984. The most recent filed accounts, for the 2025 financial year, show NOK 12.0m in revenue and NOK 2.8m in operating profit.

Key figures · 2025

Revenue
NOK 12.0m
Operating profit
NOK 2.8m
Equity
NOK 3.3m
Est. value
NOK 9.8m

Financial health · 2025

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

Who owns SAMEIET LØVLI TERRASSE?

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

Frequently asked questions about SAMEIET LØVLI TERRASSE

What is the revenue of SAMEIET LØVLI TERRASSE?

SAMEIET LØVLI TERRASSE had revenue of NOK 12.0m in 2025.

Where is SAMEIET LØVLI TERRASSE based?

SAMEIET LØVLI TERRASSE has its business address in Bergen.

Property

Business address c/o Vestbo BBL Strandgaten 196, 5004 Bergen
Cadastral unit 4601-165/68/0/0
Building Annen kontorbygning · 1 unit

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