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

SOLTUNET BOLIGSAMEIE

Org. no. 993630519 Condominium flat owner (ESEK) Oslo Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 651,000
Operating profit NOK 62,000
Equity NOK 496,000
Incorporated 2008

SOLTUNET BOLIGSAMEIE is registered as a condominium flat owner in Oslo, Oslo with organisation number 993630519. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2008. The most recent filed accounts, for the 2025 financial year, show NOK 651,000 in revenue and NOK 62,000 in operating profit.

Former names: SOLTUNET BOLIGAMEIE

Key figures · 2025

Revenue
NOK 651,000
Operating profit
NOK 62,000
Equity
NOK 496,000
Est. value
NOK 580,000

Financial health · 2025

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

Who owns SOLTUNET BOLIGSAMEIE?

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

Frequently asked questions about SOLTUNET BOLIGSAMEIE

What is the revenue of SOLTUNET BOLIGSAMEIE?

SOLTUNET BOLIGSAMEIE had revenue of NOK 651,000 in 2025.

Where is SOLTUNET BOLIGSAMEIE based?

SOLTUNET BOLIGSAMEIE has its business address in Oslo.

Property

Business address v/ Alle Tall AS Karoline Kristiansens vei 1, 0661 Oslo
Cadastral unit 301-130/2/0/0

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