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

SAMEIET RISBAKKEN 14

Org. no. 986718834 Condominium flat owner (ESEK) Oslo Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 692,000
Operating profit NOK 115,000
Equity NOK 274,000
Incorporated 2004

SAMEIET RISBAKKEN 14 is registered as a condominium flat owner in Oslo, Oslo with organisation number 986718834. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2004. The most recent filed accounts, for the 2025 financial year, show NOK 692,000 in revenue and NOK 115,000 in operating profit.

Key figures · 2025

Revenue
NOK 692,000
Operating profit
NOK 115,000
Equity
NOK 274,000
Est. value
NOK 570,000

Financial health · 2025

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

Who owns SAMEIET RISBAKKEN 14?

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

Frequently asked questions about SAMEIET RISBAKKEN 14

What is the revenue of SAMEIET RISBAKKEN 14?

SAMEIET RISBAKKEN 14 had revenue of NOK 692,000 in 2025.

Where is SAMEIET RISBAKKEN 14 based?

SAMEIET RISBAKKEN 14 has its business address in Oslo.

Property

Business address Risbakken 14, 0374 Oslo
Cadastral unit 301-41/237/0/0
Building Stort frittliggende boligbygg på 3 og 4 etg · 6 units

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